Skip to content

Update troubleshooting guidance for Linux VM provisioning #2008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
raulalvarezg wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update troubleshooting guidance for Linux VM provisioning #2008

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d118c9c
Update troubleshooting guidance for Linux VM provisioning
raulalvarezg Feb 1, 2026
8f75974
Merge branch 'main' into patch-1
raulalvarezg Jun 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,14 @@ Before troubleshooting, determine where the deployment failed:

## Symptoms

> [!IMPORTANT]
> This article focuses on **Linux VM provisioning failures**, most commonly seen when deploying from **custom images**.
>
> If the deployment fails due to **capacity, SKU availability, or regional allocation**, see:
> - [Troubleshoot Azure VM allocation failures](https://learn.microsoft.com/troubleshoot/azure/virtual-machines/allocation-failure)
> - [Troubleshoot issues when creating virtual machines in Azure](https://learn.microsoft.com/troubleshoot/azure/virtual-machines/troubleshoot-deployment-overview)

Most Linux VM provisioning failures described in this article occur when you deploy a virtual machine (VM) from a **custom image** that wasn't prepared or generalized correctly. When this failure occurs, the VM status is shown as `creating` for up to 40 minutes, and you receive one of the following error messages:
### Provisioning failure

A common provisioning failure occurs when you deploy a virtual machine from a custom Linux image. In this scenario:
Expand All @@ -49,6 +57,8 @@ A common provisioning failure occurs when you deploy a virtual machine from a cu
- Provisioning eventually fails.
- Azure reports an OS provisioning error.

```json
Deployment failed. Correlation ID: f9dcb33a-4e6e-45c5-9c9d-b29dd73da2e0. {
The following example shows this kind of error message:

> [!NOTE]
Expand Down