Unable to start VM ,once moved from one subscription to another ,almost 2+ hours it still shows moving resources

Hi @Vinodh247 ,thanks for the reply.

The resources were critical for us, and I initiated the resource migration at 9 AM IST. However, I'm still encountering the same issue. Normally, the migration process only takes 10-20 minutes. I'll wait a few more minutes and update you on the status here.

@Vinodh247 ,it's been beyond the specified time of 4hrs, but the issue persists.

Okay. I just assume you have had all the checks before you started moving the resources. Can you confirm with the below checklist? esp., point 1 & 4.

https://video2.skills-academy.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription#checklist-before-moving-resources

according to azure below is not supported for VM movement, I am placing the link here as well... pls check this too.

Scenarios not supported The following scenarios aren't yet supported:

• Virtual Machine Scale Sets with Standard SKU Load Balancer or Standard SKU Public IP can't be moved.
• Virtual machines in an existing virtual network can be moved to a new subscription only when the virtual network and all of its dependent resources are also moved.
• Virtual machines created from Marketplace resources with plans attached can't be moved across subscriptions. For a potential workaround, see Virtual machines with Marketplace plans.
• Low-priority virtual machines and low-priority virtual machine scale sets can't be moved across resource groups or subscriptions.
• Virtual machines in an availability set can't be moved individually.

https://video2.skills-academy.com/en-us/azure/azure-resource-manager/management/move-limitations/virtual-machines-move-limitations?tabs=azure-cli

@Vinodh247 ,Thank you for the replies. Despite the moving process taking more than 4 hours, it has finally succeeded. I really appreciate your attention to this issue. You're a lifesaver!!