MicrosoftDocs
Running VMs in AVSET within an AVZone is no longer supported.
Hey all,
In step 5 under "Add a Target Availability Zone", it mentions you are able to run a VM in an AVSET within an AVZONE: "In Availability set, select an availability set if you want the target VM to run within an availability set in the availability zone."
Was doing some testing and it seems this is no longer the case. You have to choose between one of the two:
Error message Virtual machine has an unsupported target configuration. Possible Causes: The virtual machine /subscriptions/xxxxxxxxxxxxxxxxx/resourceGroups/testmove_group/providers/Microsoft.Compute/virtualMachines/testmove is configured to use both availability set /subscriptions/xxxxxxxxxxxxxx/resourceGroups/testmove_group/providers/Microsoft.Compute/availabilitySets/NEWAVSET and availability zone 1 redundancy which is not supported. Recommended Action: Select one of the 2 redundancy options and retry the operation.
Just a heads up. Looks like we need to update this documentation.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 63aafb7a-9c0a-8bcb-89da-31887dd4cc75
- Version Independent ID: 374b743f-0621-42e3-a100-a89a3ba725af
- Content: Move Azure VMs to availability zones in another region with Azure Resource Mover
- Content Source: articles/resource-mover/move-region-availability-zone.md
- Service: resource-move
- GitHub Login: @rayne-wiselman
- Microsoft Alias: raynew
@phyoungmsft Thanks for your feedback! We will investigate and update as appropriate.
@phyoungmsft, thank you for reporting it. I am assigning it to the content author for further review and update, as required.
@rayne-wiselman, could you please review this and share your thoughts. Thanks
Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close