Clarify Azure Front Door move support (Classic vs Standard/Premium); add note and links

[cyrusirandoust]

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.
• 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.

[prmerger-automator[bot]]

@cyrusirandoust : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 2964a67:

:bulb: Validation status: suggestions

File	Status	Preview URL	Details
articles/azure-resource-manager/management/move-support-resources.md	:bulb:Suggestion		Details

articles/azure-resource-manager/management/move-support-resources.md

• Line 1402, Column 8: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/frontdoor/front-door-faq#can-i-move-front-door-and-cdn-profiles-between-resource-groups-or-subscriptions-without-any-downtime-' will be broken in isolated environments. Replace with a relative link.
• Line 1402, Column 206: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/frontdoor/migrate-tier' 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.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 6e4e5ab:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/azure-resource-manager/management/move-support-resources.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

[cyrusirandoust]

@mumian hi, do I need to do anything else for this update to happen? Thanks in advance for your guidance.

[ttorble]

@mumian

Can you review the proposed changes?

IMPORTANT: 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

[cyrusirandoust]

Please can anyone merge this? @mumian @ttorble What do I need to do more?

[cyrusirandoust]

#sign-off

[prmerger-automator[bot]]

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

[v-dirichards]

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!

[cyrusirandoust]

@v-dirichards @ttorble can you please ask @mumian to work on this one, or please assign someone else?

[v-dirichards]

@v-dirichards @ttorble can you please ask @mumian to work on this one, or please assign someone else?

In the public repo, PRs must be signed off by the author, which is @mumian. We're waiting for their approval.

[v-dirichards]

@mumian

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[learn-build-service-prod[bot]]

Learn Build status updates of commit 8b5ccb5:

:bulb: Validation status: suggestions

File	Status	Preview URL	Details
articles/azure-resource-manager/management/move-support-resources.md	:bulb:Suggestion		Details

articles/azure-resource-manager/management/move-support-resources.md

• Line 4, Column 11: [Suggestion: value-deprecated-replace - See documentation] The 'ms.topic: conceptual' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.topic: article'.

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.

[cyrusirandoust]

@v-dirichards I see this new message: "The 'ms.topic: conceptual' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.topic: article'." Do I need to resolve this or will this be done by @mumian