From d118c9c61383d4f767e704185ba18f8647edfe16 Mon Sep 17 00:00:00 2001 From: raulalvarezg Date: Sun, 1 Feb 2026 11:07:25 -0600 Subject: [PATCH] Update troubleshooting guidance for Linux VM provisioning MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix: Make Scope Explicit Added this immediately after 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) This single block eliminates cross‑pollination complaints without removing content. Fix the misleading Symptoms opener (this is critical) Current problem The opening implies all deployment failures, but the entire article is image‑centric. Replace this paragraph under Symptoms Current A typical provisioning failure scenario occurs after you create a custom image and then deploy a virtual machine (VM) from that image. This is actually correct, but it needs to be declared as the primary scenario, not an example. Changed to: 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. No logic change — just removes ambiguity. Fix typo: Diff- ```toutputext + ```json Improves rendering and linting. --- .../linux/troubleshoot-deployment-new-vm-linux.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md b/support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md index c3a1be84fbe..64584098801 100644 --- a/support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md +++ b/support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md @@ -20,7 +20,14 @@ ms.reviewer: srijangupta, scotro, jarrettr ## Symptoms -A typical provisioning failure scenario occurs after you create a custom image and then deploy a virtual machine (VM) from that image. 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: +> [!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: ```output Provisioning state Provisioning failed. @@ -29,7 +36,7 @@ The VM may still finish provisioning successfully. Please check provisioning sta Also, make sure the image has been properly prepared (generalized). * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/. ``` -```toutputext +```json Deployment failed. Correlation ID: f9dcb33a-4e6e-45c5-9c9d-b29dd73da2e0. { "status": "Failed", "error": {