Cannot connect to VM

Hello @Anil ,

In addition to the above comments, please review the information below:

Are you still facing the issue? If yes, please follow the steps below:

Firstly, Check CPU Utilization>>Navigate to the VM’s Monitoring section.>>Review the Average CPU Utilization metric.

Check whether the CPU usage is consistently reaching a high threshold. If so, consider resizing the VM and then verify whether you are able to access it.

Verify Firewall Configuration. Ensure that the required firewall ports are enabled. If the firewall is enabled and the issue persists, temporarily disable it for testing purposes and check whether VM access is restored.

Test with a Different Network. Try accessing the VM using a different network connection. In some cases, the ISP/network provider may restrict or impact VM connectivity.

Kindly share the exact error message or screenshots/snippets of the issue via private message for further analysis.

Alternative Recovery Options. You may take a snapshot of the OS disk and create a new VM from that disk to preserve the same data.

Alternatively, you can create a recovery VM, attach the affected OS disk to it, and then swap the OS disk back to the original VM if required.

Please refer to this link: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/cannot-connect-rdp-azure-vm

Please let me know the outcome after performing the above steps, and I will be happy to assist.

The VM shows "Azure Virtual Machine agent status is not ready" and RDP is failing, so both connectivity and the Guest Agent must be checked.

Use this sequence:

1. Verify the VM is running
   1. In the Azure portal, go to Virtual machines and select the VM.
   2. On Overview, confirm the VM is in a Running state, not Stopped or Deallocated.
2. Run basic RDP connectivity troubleshooting After each step, try RDP again.
   1. In the VM blade, under Help, select Reset password.
   2. Set Mode to Reset configuration only and select Update to reset the RDP configuration and firewall rules for port 3389.
   3. Check Network Security Group (NSG) rules on the VM NIC and subnet:
      • Ensure there is an inbound Allow rule for TCP port 3389 from the required source IPs.
      • Make sure no higher‑priority Deny rule is blocking RDP.
   4. Review Boot diagnostics for OS boot errors that might prevent RDP.
   5. If needed, Reset the NIC from the VM blade.
   6. Check Resource health for any platform issues.
3. Address the Guest Agent "Not ready" status
   1. On the VM Properties tab, confirm Agent status is not Ready.
   2. If it is Not ready or blank, Guest Agent is missing or unhealthy. RDP is normally required to repair it, so first restore RDP using the steps above.
   3. Once RDP works, sign in and verify Guest Agent services are running (per the Guest Agent troubleshooting checklist). If needed, reinstall or update the Guest Agent following the guidance in the Guest Agent article.
4. If RDP still fails
   1. Use the Serial console from the VM blade (Support & troubleshooting → Serial console) to get a CMD/PowerShell session.
   2. From Serial console, verify that the TermService (Remote Desktop Services) is running and that port 3389 is listening, or change the RDP port and update firewall rules as described in the RDP internal error article.
   3. If the OS is badly damaged, follow the offline repair approach: detach the OS disk, attach it to a recovery VM, fix configuration, then reattach.

These steps restore RDP connectivity and allow the Guest Agent to report Ready again.

References:

• Troubleshoot Remote Desktop connections to an Azure virtual machine
• Troubleshoot Azure Windows VM Agent issues
• An internal error occurs when you try to connect to an Azure VM through Remote Desktop