Azure VM is not accessible, says VM agent is not ready. I have tried all the troubleshoot options however, it's not working

Sivakumaran R 0 Reputation points
2026-02-02T13:20:47.17+00:00

Hi There,

I’d appreciate your support in resolving the Azure VM access issue. The VM was working fine earlier, but RDP access suddenly stopped working. In the Azure portal, the Virtual Machine Agent status shows as Not Ready. As recommended by Microsoft troubleshooting guidelines, I’ve already tried the suggested recovery steps, but none of them resolved the issue.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-02-02T13:20:58.3633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To resolve the issue of your Azure VM showing the Agent status as Not Ready, you can follow these troubleshooting steps:

    1. Check if the VM is started: Ensure that your VM is running. You can do this by navigating to the Azure portal, selecting your Virtual Machine, and checking the Overview page.
    2. Verify Guest Agent status: On the VM Overview page, check the Properties tab to see if the Agent status is Ready. If it is not, the Guest Agent may not be installed or functioning correctly.
    3. Check Guest Agent services: Use Remote Desktop Protocol (RDP) to connect to your VM and ensure that the Guest Agent services are running. If they are not, you may need to restart them.
    4. Review connectivity to WireServer IP: The VM must be able to connect to the WireServer IP address (168.63.129.16). Check if there are any firewalls or proxies blocking this connection. You can test connectivity to this IP from within the VM.
    5. Check for common error scenarios: Look for specific error messages in the WaAppAgent.log file located at C:\WindowsAzure\Logs\WaAppAgent.log. Common issues include problems with DHCP settings, firewalls blocking necessary ports, or the Guest Agent being stuck in a stopping process.

    If these steps do not resolve the issue, consider reinstalling the Azure VM Agent or checking for any updates that may need to be applied.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.