I am able to create a new virtual machine that's of a larger size than my current one, but I am not able to upgrade or resize an old VM to that larger size even though it's of a pretty similar type. So I'm thinking, since I can't resize the VM in place, can I create a new VM of the larger size and simply restore onto its OS disk the contents of the old, smaller VM's OS disk? I mean, the two VMs seem to be practically the same except the larger type features Premium Disk support.
I've resized other Azure VMs in place before easily, but this particular new scenario is a situation where the old VM I am trying to resize, E32a_v4, supports Standard SSD and the new one, E32as_v4, supports Premium SSD--which is the very reason I'm trying to upgrade! I mean, the two VM types are only off by one letter (s)! However, the resize operation is unfortunately not as straightforward. Azure will not allow the resize to be performed in place, saying, "Failed to resize virtual machine". Here are the details:
"Failed to resize virtual machine 'MyVirtualMachineName' to size 'Standard E32as_v4'. Error: Operation could not be completed as it results in exceeding approved standardEASv4Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 32, Current Usage: 32, Additional Required: 32, (Minimum) New Limit Required: 64. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/?#create/Microsoft.Support/Parameters/bla-bla-bla by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests."
But according to the Azure support technicians I'm interfacing with,
". . . If the customer is trying to resize a VM that operates on standard disk to a VM that operates on Premium disk, they will be unable to as there are significant hardware differences. However, the customer should be able to create a brand new VM as E32asv4 and migrate the data if they would like."
This is unacceptable, as creating a brand new VM for me wouldn't mean that I could simply "migrate the data"--there are a very many software packages configured and far too many other Windows policies and other settings I would have to recreate. It would be a very laborious task and the chances I will miss many important preferences and configurations is too high.
Thus I am thinking, can't I simply take a backup of the old E32a_v4 VM's OS disk and restore it onto the newly created E32as_v4 VM as its new OS disk (wiping out or replacing whatever it already had)?