i cannot connect to my vm

Question

i cannot connect to my vm

Andrew Harrover 0

I cannot connect to my VM. It is running but my RMM shows it offline. The agent status unavailable....

Andrew Harrover 0 Reputation points

2026-02-06T18:11:58.18+00:00

Thank you.
Andrew Harrover 0 Reputation points

2026-02-06T18:42:57.1166667+00:00

any updates?
Manish Deshpande 4,225 Reputation points Microsoft External Staff Moderator

2026-02-09T15:41:07.4066667+00:00

Hello @Andrew Harrover

I have requested for few details to connect with over the teams call to discuss the issue briefly and fix the issue, Pls respond at your earliest.

Thanks,
Manish.
Jilakara Hemalatha 10,200 Reputation points Microsoft External Staff Moderator

2026-02-09T15:46:20.51+00:00
Hello Andrew,

To know more understand about the issue. Could you please provide the below details.

What type of operating system is your VM running (Windows, Linux, etc.)?

Are you trying to connect using RDP, SSH, or another method?

Have there been any recent changes to the VM, such as OS updates, configuration changes, or resizing?

Can you confirm if the VM Agent has always been “Not Ready,” or did it change recently?

Have you tried accessing the VM using the Serial Console?

Has the VM been stopped or deallocated for a long time before this issue occurred?

Did you attempt redeploying the VM or restarting the VM Agent services? If yes, what was the result?

Are there any error messages or logs from boot diagnostics or the VM Agent that you can share?

Please provide please check the boot diagnostic screenshot.

Could you please check the private message and provide the necessary details for further investigation.
Manish Deshpande 4,225 Reputation points Microsoft External Staff Moderator

2026-02-10T23:26:27.6633333+00:00

Hello @Andrew Harrover

I just wanted to kindly follow up to check if you had a chance to review my earlier response. I hope the information shared was helpful. Please feel free to reach out if you have any additional questions or need further clarification.

Thanks,
Manish
Manish Deshpande 4,225 Reputation points Microsoft External Staff Moderator

2026-02-11T19:18:44.2333333+00:00

Hello @Andrew Harrover

I just wanted to kindly follow up to check if you had a chance to review my earlier response. I hope the information shared was helpful. Please feel free to reach out if you have any additional questions or need further clarification.

Thanks,

Manish

3 answers

Your answer

Andrew Harrover 0 Reputation points

2026-02-06T18:11:58.18+00:00

Thank you.
Andrew Harrover 0 Reputation points

2026-02-06T18:42:57.1166667+00:00

any updates?
Manish Deshpande 4,225 Reputation points Microsoft External Staff Moderator

2026-02-09T15:41:07.4066667+00:00

Hello @Andrew Harrover

I have requested for few details to connect with over the teams call to discuss the issue briefly and fix the issue, Pls respond at your earliest.

Thanks,
Manish.
Jilakara Hemalatha 10,200 Reputation points Microsoft External Staff Moderator

2026-02-09T15:46:20.51+00:00

Hello Andrew,

To know more understand about the issue. Could you please provide the below details.

What type of operating system is your VM running (Windows, Linux, etc.)?

Are you trying to connect using RDP, SSH, or another method?

Have there been any recent changes to the VM, such as OS updates, configuration changes, or resizing?

Can you confirm if the VM Agent has always been “Not Ready,” or did it change recently?

Have you tried accessing the VM using the Serial Console?

Has the VM been stopped or deallocated for a long time before this issue occurred?

Did you attempt redeploying the VM or restarting the VM Agent services? If yes, what was the result?

Are there any error messages or logs from boot diagnostics or the VM Agent that you can share?

Please provide please check the boot diagnostic screenshot.

Could you please check the private message and provide the necessary details for further investigation.
Manish Deshpande 4,225 Reputation points Microsoft External Staff Moderator

2026-02-10T23:26:27.6633333+00:00

Hello @Andrew Harrover

I just wanted to kindly follow up to check if you had a chance to review my earlier response. I hope the information shared was helpful. Please feel free to reach out if you have any additional questions or need further clarification.

Thanks,
Manish
Manish Deshpande 4,225 Reputation points Microsoft External Staff Moderator

2026-02-11T19:18:44.2333333+00:00

Hello @Andrew Harrover

I just wanted to kindly follow up to check if you had a chance to review my earlier response. I hope the information shared was helpful. Please feel free to reach out if you have any additional questions or need further clarification.

Thanks,

Manish

Answer 1

Hello @Andrew Harrover ,

In some cases, restarting the VM stop → start can resolve VM agent related issues. You may also try resizing the VM and then verifying that it reaches a running state successfully. If the issue persists, proceed with an offline installation of the VM agent. To do this, create a temporary VM, attach the affected VM’s OS disk as a secondary disk, and then follow the troubleshooting steps provided in the documentation below.

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/install-vm-agent-offline#how-to-install-the-vm-agent-in-offline-mode

Please share the error messages and activity logs in private messages which helps me to troubleshoot the issue more.

Please let us know if you have any further questions. I’m happy to assist. Thank you!

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

Hello Andrew

Thank you for contacting us about the VM issue.

This may be caused due to few reasons

Azure VM Guest Agent stopped responding or became unhealthy

VM was stuck on an underlying host after maintenance
Network or agent-level communication issue (agent heartbeat not reaching Azure)
Guest Agent corruption after updates or restarts

When the Azure VM Agent is unavailable, Azure cannot perform management operations (password reset, Run Command, extensions), and connectivity issues such as RDP failure are common.

Steps to fix the issue

1.Stop (Deallocate) and Start the VM

This forces the VM to be moved to a healthy Azure host and often restores agent communication.

Azure Portal

Go to Virtual Machines
Select the affected VM
Click Stop (wait until status shows Stopped (deallocated))
Click Start
Retry RDP/SSH connection.

2.Redeploy the VM(This is the most recommended solution.)

If Stop/Start does not help, Redeploy has consistently fixed this issue in earlier cases.

What Redeploy Does

Moves the VM to a new Azure host
Preserves OS disk, data disks, IP, and configuration
Does not delete the VM

Azure Portal

VM → Help + troubleshooting
Select Redeploy
Confirm redeploy
Wait for completion
Start the VM (if not auto‑started)
Retry connection.

3.Check Boot Diagnostics

If the VM still cannot be accessed:

VM → Boot diagnostics
Review the screenshot and serial output
Confirm the OS is not stuck on:
- Recovery screen
  - Disk check
    - Startup repair

Boot issues can prevent the VM Agent from starting.

4.Reset RDP Configuration

Once agent communication is restored:

VM → Help
Select Reset password
Choose Reset configuration only
Update and retry RDP

Links :
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/windows-azure-guest-agent
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection

Thanks,
Manish.

Share via

i cannot connect to my vm

3 answers

Your answer