An Azure service that is used to provision Windows and Linux virtual machines.
Hi Aritra,
Thank you for reaching out to Microsoft Q&A.
Just wanted to add few lines to Siddesh Response.
If your Azure Virtual Machine shows up as Healthy and all diagnostics are green, but you still can't connect via RDP, it usually means the problem isn't with the Azure compute host. The health checks just confirm that the platform is running (like power, host status, and basic fabric stuff), but they don’t check the network path or guest OS access. So, even if your VM looks healthy in the portal, you can still run into connectivity issues.
Actions to perform:
1. Verify Network Security Group (NSG) rules
Ensure that the NSG associated with the VM’s NIC or subnet allows inbound traffic on:
- TCP 3389 for Windows (RDP)
Confirm that:
- The Allow rule has a higher priority than any Deny rule
- The source IP range includes your client’s public IP or trusted CIDR
2. Take a look at User‑Defined Routes (UDR) and Effective Routes
If you’ve got a custom route table linked, your traffic might be getting sent to a firewall, NVA, or gateway that can’t handle RDP traffic.
- Hop into Network Watcher → Effective routes on the VM NIC
- Double-check that the next hop for 0.0.0.0/0 or client traffic is set up right
3.Resetting RDP settings from the Azure portal No worries
This method is totally safe, supported by Microsoft, and won’t mess with your credentials.
- Head over to VM → Help → Reset password
- Pick Reset configuration only
Doing this will bring back:
- Your RDP service settings
- Any Windows Firewall rules tied to RDP.
4.Leverage Azure Network Watcher – IP Flow / Connectivity Check for precise diagnostics
Hey, let's run a quick connectivity check to confirm the following:
- NSG rules are functioning as expected
- The route table is configured correctly
- The next-hop is reachable
This approach will allow you to quickly identify exactly where the traffic is being blocked.
5.Use Azure Serial Console to access the VM
If you can’t use RDP at all, the Serial Console is a handy workaround since it skips networking and gives you direct access to the OS. With Serial Console, you can check Windows Firewall rules, restart the RDP service, or fix network and policy settings right at the OS level.
6.Redeploy the VM (Mostly this step fixes the issue)
When you redeploy, your VM gets moved to a different Azure host, but don't worry it keeps the same OS disk, data, IP, and setup.
It's best to try this only after you've checked for any network or OS issues first.
Conclusion:
A healthy VM status confirms that Azure infrastructure is functioning correctly. RDP connectivity issues are most often caused by NSG rules, routing configuration, or OS‑level settings, not the Azure compute layer itself. Following the steps above will help isolate and resolve the issue in a supported manner.
- Troubleshoot RDP connections to Azure VMs
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection - Detailed RDP troubleshooting in Azure
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/detailed-troubleshoot-rdp
I have requested few details to connect with you over a team call pls share the details at the earliest.
- Have you noticed if the crashes happen with certain apps or is it just random across different ones?
- Are there any error messages popping up when things crash?
Thanks,
Manish.