When an Azure virtual machine will not start normally, boot diagnostics provides a view of its startup state. It collects screenshots and serial log information that can help you choose the next troubleshooting step.
This guide covers individual Windows and Linux Azure Resource Manager VMs. You need access to the VM and permission to view its diagnostics; changing the configuration also requires appropriate write access.
Open boot diagnostics
- Sign into the Azure portal and open Virtual machines.
- Select the affected VM. Check its subscription and resource group so you are inspecting the correct instance.
- In the VM menu, find Boot diagnostics. Microsoft documentation places it under Help; portal navigation may also group troubleshooting tools together.
- Inspect the screenshot and available serial log information.
Look for a displayed boot error, recovery prompt, or other startup message. Record the exact wording rather than relying on a description such as “it will not boot.”
If boot diagnostics is disabled
- On the VM’s Boot diagnostics page, select Settings.
- Choose the option to enable boot diagnostics with a managed storage account.
- Select Save, then return to the diagnostics view.
Microsoft recommends managed storage for the standard experience. Boot diagnostics is enabled by default for VMs created through the portal, but check the actual configuration of existing VMs.
Allow time for evidence to appear
Microsoft notes that screenshots and output can take up to 10 minutes to appear. A screenshot can also be stale because of the guest operating system’s virtual display timeout. An old image alone is not enough to establish the VM’s current state.
With custom diagnostic storage, check permissions and storage firewall access. The custom storage account must be in the same region and subscription as the VM.
Use the evidence
Create a short incident note containing the VM name, observation time, visible error, recent change, and the next check you plan to perform. For example: “After today’s update, the screenshot shows a recovery screen; investigate the displayed error before making disk changes.”
Boot diagnostics gathers evidence; it does not repair the underlying problem. Choose a Microsoft troubleshooting procedure that matches what you actually observe.

