An Azure service that is used to provision Windows and Linux virtual machines.
Thank you for sharing the details. Based on our analysis we have performed the below checks
We inspected Boot Diagnostics and accessed the Serial Console. Both tools confirmed that the operating system was healthy, and the VM booted correctly without underlying OS corruption or disk-related issues.
Upon review, the VM’s provisioning state was "Updating," and an extension was in a "Failed" state. This platform updating or extension failure can temporarily impact VM accessibility until resolved.
We reviewed Performance Insights and CPU metrics, which showed that CPU utilization was consistently high. This confirms that the current VM size was not sufficient for the workload. Due to this sustained utilization, the VM was under resource pressure, which contributed to the access issue.
After redeployed and restarted the VM, access was restored after ~20 minutes. Resizing from Standard_D2as_v5 → Standard_D4as_v5 (4 vCPU, 16 GiB) helped stabilize performance and cx able to access the RDP.
Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm?tabs=portal
Troubleshoot high-CPU issues on Azure Windows virtual machines
Best Practices Before Resizing
To ensure a smooth and safe resize operation, please follow these steps:
- Create a snapshot of the OS disk as a backup: Go to VM → Disks → Select OS Disk → Create snapshot.
- Make sure the VM is in a Deallocated state: Stop the VM → Resize → Start the VM again.
Following these steps helps avoid failures during resizing and ensures you have a recovery option in case anything goes wrong.
Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/expand-disks