![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 70%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDH%3C/text%3E%3C/svg%3E)
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
Hello @Dan Hobson
Since this happened immediately after installing updates, the first thing I'd check is whether the Azure VM failed to boot or whether Windows is running, but RDP/network connectivity is no longer responding.
In the Azure portal, please check:
VM > Help > Boot diagnostics
Look at the latest screenshot. Microsoft specifically recommends Boot Diagnostics when an Azure VM becomes unresponsive during or after Windows Update.
If the screenshot shows "Getting Windows ready", "Working on updates", "Reverting changes", or a specific error code, please post that message here. Don't repeatedly power-cycle the VM while Windows is servicing updates, since interrupting the process can potentially leave the OS in a worse state.
If Windows appears to have booted normally, then check:
- Resource Health for the VM.
- Whether the VM responds through Serial Console or Run Command.
- The effective NSG rules and whether TCP 3389 is still reachable.
- Whether you can reset the RDP configuration from VM > Help > Reset password > Reset configuration only.
Microsoft includes these among the standard troubleshooting steps when RDP to a Windows Azure VM stops working.
Since you've identified this server as a domain controller, I would avoid resetting accounts or making major recovery changes until you've confirmed the VM's boot state. If this is one of multiple DCs, also check whether the other DCs are healthy before attempting recovery.
If Boot Diagnostics shows Windows cannot boot after the update, Microsoft provides a separate recovery procedure to repair the OS disk offline using a repair VM. I would treat that as a later recovery step rather than the first action.
Sharing these references with you:
Troubleshoot Windows Update failures on Azure VMs
Troubleshoot RDP connections to a Windows Azure VM
Please share what Boot Diagnostics shows and, if possible, the Windows Server version and which updates were installed. That should tell us which recovery path to take next.
Please "Accept the Answer" if this information helped you. This will help us and others in the community.