Dynamic Rules Graph Doc Changes

[manikantsinghms]

Important

Required for API changes:

• Link to API.md file: ADD LINK HERE
• Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): https://msazure.visualstudio.com/One/_git/AD-AggregatorService-Workloads/pullrequest/11332217
  https://msazure.visualstudio.com/One/_git/AD-AggregatorService-Workloads/pullrequest/11009551

---

Add other supporting information, such as a description of the PR changes:

ADD INFORMATION HERE

---

Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.

• do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
• Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
• If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
• After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
• Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

[learn-build-service-prod]

Learn Build status updates of commit 11f77fb:

✅ Validation status: passed

File	Status	Preview URL	Details
changelog/Microsoft.EnhancedRestore.json	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Danielabom]

@manikantsinghms, the repo that you would want to use is https://github.com/microsoftgraph/microsoft-graph-docs.

[learn-build-service-prod]

Learn Build status updates of commit 6b233d4:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
api-reference/beta/api/driveprotectionrule-deleteandunprotect.md	❌Error		Details

api-reference/beta/api/driveprotectionrule-deleteandunprotect.md

• Line 28, Column 1: [Error: include-not-found - See documentation] Invalid include link: '../includes/permissions/driveprotectionrule-deleteandunprotect-permissions.md'.
• Line 7, Column 16: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.subservice': '**TODO: Add MS subservice. See [topic-level metadata reference](https://aka.ms/msgo?pagePath=Document-APIs/Guidelines/Metadata)**' is not valid with 'ms.service' value 'microsoft-graph'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Danielabom]

@manikantsinghms, the repo that you need to use is (https://github.com/microsoftgraph/microsoft-graph-docs). Please follow this wiki (https://dev.azure.com/msazure/One/_wiki/wikis/Microsoft%20Graph%20Partners/707657/Get-started).

[github-actions]

This pull request has conflicting changes, the author must resolve the conflicts before this pull request can be merged.