An Azure service that is used to provision Windows and Linux virtual machines.
hi Syd Weinstein & thx for sharing urs issue here at Q&A portal,
az vm repair restore is hitting a zone-move path that isn’t supported for that VM/region/subscription.
The LRS disk itself is prob not the real issue. More likely the repair VM was created w/ a different zone setting than the original VM, or the CLI restore flow is trying to enable zone movement while swapping the OS disk back.
don’t use repair restore. Do the restore manually by swapping the repaired OS disk back onto the original VM.
Stop the original VM, detach the repaired OS disk from the repair VM, then use it as the OS disk for the original VM. Make sure the disk is in the same region and compatible zone setup as the original VM. If the original VM is non-zonal, use a non-zonal disk or repair VM. If it’s zonal, keep everything in the same zone.
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/os-disk-swap
create the repair VM in the same region/zone pattern as the source VM. Avoid letting the repair tool pick a zone if the original VM isn’t zonal. That’s prob what triggers the Enabling zone movement error. If manual OS disk swap also fails w/ zone movement, open a VM support case w/ the VM resource ID, disk IDs, region, zone value for both VMs/disks, and the CLI debug output. But yeah, safest path rn is manual disk swap, not retrying the repair restore loop.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal
and at my blog https://ctrlaltdel.blog/