Repo sync for protected branch

[learn-build-service-prod]

Learn Build Service tried pushing to main, but failed due to branch protection rule in this branch. We create this pull request for manual merge. Please merge this pull request to complete this sync.
If you want to make push successfully without creating such pull requests in future, please follow working with branch protection rule to update your branch protection rule.

[learn-build-service-prod]

Learn Build status updates of commit c16ee03:

✅ Validation status: passed

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Added File(s)	This PR contains added files. New files require human review.
Image File	This PR added or updated an image file(s).

[prmerger-automator]

@learn-build-service-prod[bot] : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[ttorble]

@femila @EliotSeattle Can you merge this latest repo sync PR, which appears to be stuck?

[Copilot]

Pull Request Overview

This pull request removes the "(preview)" designation from the Azure Local diagnostic logs collection documentation, indicating the feature has moved from preview to general availability.

• Removed "(preview)" from titles and descriptions
• Updated prerequisites to remove specific extension version requirements
• Added clarification about portal status update delays

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[EliotSeattle]

Please use the Copilot suggestion for line 57 so the grammar is correct.

[learn-build-service-prod]

Learn Build status updates of commit eae9d18:

✅ Validation status: passed

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Added File(s)	This PR contains added files. New files require human review.
Image File	This PR added or updated an image file(s).

[v-dirichards]

@EliotSeattle When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[EliotSeattle]

#sign-off

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @alkohli