Enhance restorepoint-search documentation with query examples

[Subham-RKB]

Added artifactQuery properties and examples for filtering restore points based on multiple criteria. Updated the queryExpression in the JSON example to remove unnecessary conditions.

Important

Required for API changes:

• [] Link to API.md file: https://msazure.visualstudio.com/One/_git/AD-AggregatorService-Workloads?path=/Reviews/9992297-22717-Enhanced-Restore-Supporting-Granular-Restore-/API.md&version=GB22717-Enhanced-Restore-Supporting-Granular-Restore-&_a=preview
• [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

---

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 95198ee:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/beta/api/restorepoint-search.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit a3fcfd3:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/beta/api/restorepoint-search.md	✅Succeeded

For more details, please refer to the build report.

[Danipocket]

In my previous comments (on the old PR), I mentioned that you’re using invalid headers.

We have predefined headers—for example, Properties and Examples—and the ones you’re adding aren’t supported. Please create a concept topic instead, or move the content into standard request or response sections without headers.

I’d recommend creating a concept topic, since this is a large amount of content to include in a request or response. Here are the guidelines: (https://eng.ms/docs/products/microsoft-graph-service/microsoft-graph/document-apis/conceptual-content).

[Subham-RKB]

@Danipocket Thanks for the suggestions.
I have added the detail in the already existing concept topic artifactQuery.

Link to that PR: #9789

[Danipocket]

@Subham-RKB, please see my comments.

[learn-build-service-prod]

Learn Build status updates of commit db8551d:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/beta/api/restorepoint-search.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 26aa520:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/beta/api/restorepoint-search.md	✅Succeeded

For more details, please refer to the build report.

[Danipocket]

PR approved.