Move-AzureVirtualNetwork to deal with source VMs that have osdisk length greater than 80 characters
With reference to case [REG:116080914523233] I have been asked to raise a new ticket to go to the product team. This is really a feature enhancement request. When running the Move-AzureVirtualNetwork on a VM with an OS disk iwth more than 80 characters in the name (which is the case for VMs restored from backup for instance) it fails, as ARM cannot supprot more than 80 characters in the vhd name. There needs to be a capability for the migration tool to rename the disk as part of the migration, or manage it in some way. We have a fair few VMs that will encounter this issue
Douglas James Boyd commented
I was then asked to raise a subsequent case [REG:116081714555243], upon which i was asked to post on here. This is the response from paid Premier Support!
"I pulled information about one of the VM from your subscription and it has more than 80 characters
Can you submit product enhancement request on the following link