Can not Connect To Azure VM. Error Message: "Agent Status Is Not Ready"

Question

I have a problem with VM Creation, Error Message: "Agent Status Is Not Ready".

 

I have a Windows 10 VM on a subscription that I want to copy it to another subscription.So I did below steps to create the VM:

1. Copy the Original VM OS-Disk To Blob as a .vhd file
2. Copy the Blob From Old Subscription to the new subscription
3. Create a managed os-disk Based on the copied vhd file
4. Create a VM From that disk

 

But after that an Error banner appears in the overview page whit this message "<VM-Name> virtual machine agent status is not ready. Troubleshoot the issue" And I can't connect to the VM via RDP.

I Tried The Troubleshoot. I tried to Stop And Start The VM and to redeploy and reapply and reset configurations but nigher works.

Answer 1

Hi @Mohsen Amirkhani ,
Thanks for contacting Microsoft Q&A.

The "Agent Status Is Not Ready" error typically indicates an issue with the Azure VM Agent on the virtual machine. The Azure VM Agent is responsible for handling various tasks on the VM, such as extensions, diagnostics, and communication with the Azure platform.

You can do below checks to troubleshoot the issue:

Check Azure VM Agent Extension:

Ensure that the Azure VM Agent extension is installed and running on your virtual machine. You can check this in the Azure portal under the VM's Extensions tab. If it's not installed or if there are issues, you may need to reinstall or update the Azure VM Agent extension.

Check Azure VM Agent Logs:

You can access the VM's serial console to view the VM Agent logs. This can provide more details about what might be causing the issue. You can find the serial console in the Azure portal, under the VM's "Support + troubleshooting" section.

Verify Network Connectivity:

Ensure that the VM has proper network connectivity to communicate with the Azure platform. If there are network issues, the VM Agent may not be able to communicate with the Azure control plane.

Check OS Disk Configuration:

Ensure that the OS disk is properly configured and attached to the VM. Verify that the disk has been properly copied, and there are no issues with the disk configuration.

Update Azure VM Agent:

If you find that the VM Agent version is outdated, consider updating it to the latest version. Newer versions may include bug fixes and improvements that could resolve the issue.

Review System and Application Logs:

Inside the VM, check the system and application logs for any errors or warnings that might be related to the Azure VM Agent or general system health.

Check for Disk Corruption:

Verify that the VHD file you copied and used to create the managed OS disk is not corrupted. If there are issues with the VHD file, it can lead to problems with the VM Agent.

Hope this helps you.