Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update app-service-move-limitations.md #122229

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

azarboon
Copy link
Contributor

@azarboon azarboon commented May 4, 2024

The following fact hasn't been mentioned any where in the doc so I've clarified it:

'When you move a Web App to a different subscription, location of the Web App remains the same but its policy will be changed. For example, if your Web App is in Subscription1 located in Central US and has Policy1. And Subscription2 is in the UK South and has Policy2. If you move the Web App to Subscription2, the location of the Web App remains the same (Central US) however it will be under the new policy which is policy2.'

The following fact hasn't been mentioned any where in the doc so I've clarified it:

'When you move a Web App to a different subscription, location of the Web App remains the same but its policy will be changed. For example, if your Web App is in Subscription1 located in Central US and has Policy1. And Subscription2 is in the UK South and has Policy2. If you move the Web App to Subscription2, the location of the Web App remains the same (Central US) however it will be under the new policy which is policy2.'
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 483711d:

✅ Validation status: passed

File Status Preview URL Details
articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented May 6, 2024

@mumian

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants