Update move-virtual-machines-regional-zonal-portal.md#480
Conversation
Correcting the region given in Azure CLI command where move collection is being created.
|
@Kavya-KU : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@Kavya-KU : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit d40a9fd: ✅ Validation status: passed
For more details, please refer to the build report. |
|
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
…-portal.md Co-authored-by: Regan Downer <v-rdowner@microsoft.com>
|
Learn Build status updates of commit cae28e8: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Azure CLI example in the “regional to zonal” VM move article to ensure the move collection’s --move-region matches the resource location used to create the move collection, aligning the sample with the stated requirement that the move collection is created in the source region.
Changes:
- Corrected the
az resource-mover move-collection createexample to use--move-region eastus2instead ofeastus. - Added a clarifying sentence ahead of the CLI snippet about keeping the resource location and source region aligned.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 1d15267: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@cynthn @iamwilliew Could you please review the proposed changes? |
Correcting the region given in Azure CLI command where move collection is being created, as the resource location and move collection's source region should be same.