Sync upcoming breaking changes docs from Azure/azure-powershell repo

[azure-powershell-bot]

Description

Sync latest upcoming breaking changes doc from Azure/azure-powershell repo.

[learn-build-service-prod]

Learn Build status updates of commit 7a9ec2c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-conceptual/azps-10.2.0/upcoming-breaking-changes.md	⚠️Warning	View (azps-10.2.0)	Details

docs-conceptual/azps-10.2.0/upcoming-breaking-changes.md

• Line 26, Column 232: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/virtual-machines/trusted-launch' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 34, Column 163: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 26, Column 232: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-machines/trusted-launch' will be broken in isolated environments. Replace with a relative link.
• Line 34, Column 163: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch' will be broken in isolated environments. Replace with a relative link.

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

[github-actions]

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

• It is not a draft PR.
• It does not have a WIP prefix in the title.
• It passes validation and build steps.
• It does not have any merge conflicts.
• You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

[mikefrobbins]

Replaced with PR #2665