Resource Mover stopped at Creates or updates a move collection

Hello @LW Thank you for posting your question. Sorry for the inconvenience this must have caused!

Moving a resource is a complex operation that has different phases. It can involve more than just the resource provider of the resource you're trying to move. Because of the dependencies between resource providers, Azure Resource Manager allows 4 hours for the operation to complete. This time period gives resource providers a chance to recover from transient issues. If your move request is within the four-hour period, the operation keeps trying to complete and may still succeed. The source and destination resource groups are locked during this time to avoid consistency issues.

However, in your case, it seems that the move operation got stuck at the "Creates or updates a move collection" phase. This could be due to a number of reasons, such as network connectivity issues, insufficient permissions, or other resource dependencies that are blocking the move.

Since there are no errors in the activity log, it's difficult to determine the exact cause of the issue. However, it's good to know that you were able to move the VHD yourself and rebuild the VM successfully.

To understand why it stopped at Creates or updates a move collection, we need to investigate the issue further to find out the root cause of it. Recommend you reach out to Azure technical support team by creating a support ticket.

Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.