Clarify Azure Front Door move support (Classic vs Standard/Premium); add note and links #127781
Conversation
…add note and links This PR clarifies the Azure Front Door entry in the Microsoft.Network table: - Renames `frontdoors` to **frontdoors (Front Door classic)** and retains No/No/No (Classic isn’t movable). - Adds a NOTE under the table explaining that **Front Door Standard/Premium** is surfaced under **Microsoft.Cdn** and **does** support move between resource groups and subscriptions. Recommends migrating Classic → Standard/Premium first, then performing the move. - (Optional) Adds a short reminder under **Microsoft.Cdn** tying those rows to Front Door Standard/Premium. Sources: - Move matrix: `Microsoft.Network/frontdoors = No/No/No`; **Microsoft.Cdn** profiles/endpoints/WAF policies = Yes/Yes/No. - AFD FAQ: Classic cannot move; Standard/Premium & CDN can; migrate first. - AFD migration guidance for Classic → Standard/Premium. No service behavior change—documentation clarity only. Updated `ms.date`.
|
@cyrusirandoust : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 2964a67: 💡 Validation status: suggestions
articles/azure-resource-manager/management/move-support-resources.md
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. |
Fix docs-link-absolute: convert Learn links to site-relative
|
Learn Build status updates of commit 6e4e5ab: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@mumian hi, do I need to do anything else for this update to happen? Thanks in advance for your guidance. |
There was a problem hiding this comment.
Pull Request Overview
This PR clarifies Azure Front Door's move support by distinguishing between Classic and Standard/Premium tiers. The documentation now explicitly states that Front Door Classic cannot be moved, while Standard/Premium (under Microsoft.Cdn) can be moved between resource groups and subscriptions.
Key changes:
- Renamed the
frontdoorsentry to indicate it refers to Front Door Classic - Added a note in the Microsoft.Network section explaining Standard/Premium support and migration path
- Added an important callout in the Microsoft.Cdn section linking those resources to Front Door Standard/Premium
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @mumian |
|
Hi @cyrusirandoust - Thanks for your review. In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM. @mumian Could you take a look? Thanks! |
4 participants
This PR clarifies the Azure Front Door entry in the Microsoft.Network table:
frontdoorsto frontdoors (Front Door classic) and retains No/No/No (Classic isn’t movable).Sources:
Microsoft.Network/frontdoors = No/No/No; Microsoft.Cdn profiles/endpoints/WAF policies = Yes/Yes/No.No service behavior change - documentation clarity only. Updated
ms.date.