Why can't I login to a VM with local admin account after moving regions via Azure Resource Mover?

Question

I have used the Azure resource mover to successfully move a VM from one region to another. I did have a couple of resources that had dependencies regarding Zones. I did change the destination resource to Not Applicable which resolved that. (mentioning this, but don't believe it's the cause.)

I do see my resource group and all resources in the destination region. After copying the RDP file and attempting to login, it is asking for my M365 credentials. I cannot use the local Admin user and password that were used on the source VM to connect.

I'm certain I read that all this information gets moved with the VM to the new region.

Answer 1

Hi @Marcus,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

It looks that you've successfully moved a VM to a new region using Azure Resource Mover, however you're facing login issues because it's asking for Microsoft 365 credentials instead of the local admin credentials.

If you are unable to log in with the local admin credentials, you can reset the local admin password through the Azure portal>>Virtual Machine>>In the left plane-Help>>Reset Password>>Set New password>>Update.

Ensure that the VM is running and not in a stopped or deallocated state and the NSG rules associated with the VM allow RDP port numbers.

Try manually RDP with public IP of the VM and enter local admin username and password.

Review the Azure Activity Log and the VM's event logs for any errors or warnings that could offer additional insights into the login issues.

If you have any further queries, do let us know.

If the answer has been helpful, we appreciate hearing from you and would love to help others who may have the same question. Accepting answers helps increase visibility of this question for other members of the Microsoft Q&A community.

Answer 2

When moving a VM using Azure Resource Mover, it's important to note that while the VM and its associated resources are transferred, certain configurations and settings may not carry over as expected. In your case, the inability to log in with the local admin account after the move could be due to several factors:

1. Managed Identity: The managed identity used during the move may not have the necessary permissions, which can affect access to the VM. Ensure that the managed identity has the appropriate roles assigned.
2. Local Admin Credentials: Sometimes, the local admin credentials may not be retained or may require reconfiguration after the move. It's advisable to check if the local admin account was properly set up in the new region.
3. Backup and Recovery Services: If the VM was backed up using Azure Backup, the backup data does not move with the VM. You may need to reconfigure backup settings in the new region.
4. Network Configuration: Ensure that the network settings, such as NSGs and public IP addresses, are correctly configured in the new region, as these can affect access to the VM.

If you continue to face issues, consider resetting the local admin password through the Azure portal or using the Azure Serial Console for troubleshooting.

---

References:

• Frequently asked questions - Move Azure single instance virtual machines from regional to zonal target availability zones
• Move Azure VMs to an availability zone in another region with Azure Resource Mover