(ClassicIaaSMigration) Help Needed! - Stuck in abort

Question

We are trying to migrate ASM VMs to ARM.

We used Move-AzureVirtualNetwork -prepare -virtualnetwork <name>

then we decided to abort (we didn't commit) using:

Move-AzureVirtualNetwork -abort -virtualnetwork <name>

Unfortunately the abort failed due to internal error. We had tried:

Abort again – failed due to exclusive lock

Prepare again – failed due to abort in progress

Manually delete resource – failed due to exclusive lock

Manually delete resource group – same failure as abort again

Thanks,

Answer 1

Hello Louis,

• Are you migrating to different region within the same subscription or to a different subscription?

To my knowledge, Azure billing team can help you in migrating the VMs between subscriptions, but there could be some constraints; your answers to the above questions would also influence if the migration is supported by the billing team or technical team.

Billing and Subscription team would be the best to provide more insight and guidance on this regard (I presume you have already contacted the Billing team and not the technical team).

https://azure.microsoft.com/en-us/support/options/  

If you wish you may migrate the VMs, the following documentations will guide you on the procedure.

Migrating Azure Virtual Machines from ASM (Classic) to ARM https://blogs.technet.microsoft.com/diegoviso/2015/12/10/migrating-azure-virtual-machines-from-asm-to-arm/  

Migrate Azure Virtual Machines between Storage Accounts

https://azure.microsoft.com/en-us/blog/migrate-azure-virtual-machines-between-storage-accounts/   

Azure-data-center-migration-just-got-easier

https://azure.microsoft.com/en-us/blog/azure-data-center-migration-just-got-easier/

Regards,

Sumanth BM

Answer 2

Sumanth - This question is not in the scope of subscription migration but the newly released feature that is talked about here - https://azure.microsoft.com/en-us/blog/iaas-migration-classic-resource-manager/ 

Regarding this particular issue, we are directly working with Louis and his customer to unblock them. To give a brief note on what happened, we detected a bug in the migration service where the service runs into a migration error when migrating certain older VMs (Created before 2013). We are rolling out a fix for this as we speak and should be resolved in 2-3 weeks for all customers.