Home / Azure / Fix Azure VM Not Starting

Azure

Fix Azure VM Not Starting

Resolve Azure VM not starting errors by checking VM size, resource availability, and configuration issues.

Published: Apr 12, 20266 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

Azure Virtual Machines fail to start. VMs stuck in starting state, deployment fails, or VM shows failed status.

Symptoms

VM failed:

```bash az vm show -g MyResourceGroup -n MyVM --query "instanceView.statuses"

[ { "code": "ProvisioningState/failed/InternalOperationError", "displayStatus": "Provisioning failed", "message": "Allocation failed." } ] ```

Allocation failure:

bash

Allocation failed. We do not have sufficient capacity for the requested VM size.

Deployment failed:

bash

Deployment failed. CorrelationId: xxx-xxx-xxx

Common Causes

1.No capacity - Region has no capacity for VM size
2.Quota exceeded - Subscription quota limit reached
3.VM size unavailable - Size not available in region
4.Resource locked - Resource group has lock
5.Image issue - VM image not available
6.Network issue - Subnet or NSG misconfigured
7.Cost limit - Spending limit reached

Step-by-Step Fix

Step 1: Check VM Status

```bash az vm show -g MyResourceGroup -n MyVM --query "instanceView.statuses"

az vm get-instance-view -g MyResourceGroup -n MyVM

az vm list --query "[?name=='MyVM']"

# Check power state: az vm show -g MyResourceGroup -n MyVM --query "powerState" ```

Step 2: Check Allocation Status

```bash az vm deallocate -g MyResourceGroup -n MyVM

az vm start -g MyResourceGroup -n MyVM

# Check activity log: az monitor activity-log list \ --resource-group MyResourceGroup \ --caller $(az account show --query user.name -o tsv) \ --max-events 10 ```

Step 3: Check VM Size Availability

```bash # List available sizes in region: az vm list-sizes --location eastus -o table

# List sizes for specific VM: az vm list-sizes --location eastus --query "[?name=='Standard_D2s_v3']"

# Resize VM: az vm resize -g MyResourceGroup -n MyVM --size Standard_D2s_v3

# Check VM size: az vm show -g MyResourceGroup -n MyVM --query "hardwareProfile.vmSize" ```

Step 4: Check Subscription Quota

```bash # List usage: az vm list-usage --location eastus -o table

# Check specific quota: az vm list-usage --location eastus --query "[?name.value=='standardDSv3Family']"

# Common limits: # - Total Regional vCPUs # - Standard DSv3 Family vCPUs # - Spot vCPUs

# Request quota increase: # Azure Portal -> Subscriptions -> Usage + quotas ```

Step 5: Try Different Region or Zone

```bash # Check available regions: az account list-locations -o table

# Check availability zones: az vm list-skus --location eastus --zone

# Create VM in different zone: az vm create \ --resource-group MyResourceGroup \ --name MyVM \ --image Ubuntu2204 \ --zone 2 ```

Step 6: Check Resource Locks

```bash # List locks: az lock list --resource-group MyResourceGroup

# Delete lock: az lock delete --name MyLock --resource-group MyResourceGroup

# Check for locks: az lock list --query "[?resourceGroup=='MyResourceGroup']" ```

Step 7: Check Disk Issues

```bash # Check disk: az disk show -g MyResourceGroup -n MyDisk

# Check disk state: az disk show -g MyResourceGroup -n MyDisk --query "diskState"

# List VM disks: az vm show -g MyResourceGroup -n MyVM --query "storageProfile"

# Create new disk from snapshot if disk corrupted: az disk create \ --resource-group MyResourceGroup \ --name MyNewDisk \ --source /subscriptions/.../snapshots/MySnapshot ```

Step 8: Check Network Configuration

```bash # Check NIC: az network nic show -g MyResourceGroup -n MyVMNic

# Check NSG: az network nsg show -g MyResourceGroup -n MyNSG

# Check subnet: az network vnet subnet show \ --resource-group MyResourceGroup \ --vnet-name MyVNet \ --name MySubnet

# Check if subnet has address space: az network vnet show -g MyResourceGroup -n MyVNet --query "subnets" ```

Step 9: Check Boot Diagnostics

```bash # Enable boot diagnostics: az vm boot-diagnostics enable \ --resource-group MyResourceGroup \ --name MyVM \ --storage https://mystorage.blob.core.windows.net/

# Get boot diagnostics: az vm boot-diagnostics get-boot-log \ --resource-group MyResourceGroup \ --name MyVM

# Check serial console output: az vm boot-diagnostics get-boot-log-uris \ --resource-group MyResourceGroup \ --name MyVM ```

Step 10: Recreate VM

```bash # Capture VM as image: az vm deallocate -g MyResourceGroup -n MyVM az vm generalize -g MyResourceGroup -n MyVM az image create -g MyResourceGroup -n MyImage --source MyVM

# Create new VM from image: az vm create \ --resource-group MyResourceGroup \ --name MyNewVM \ --image /subscriptions/.../images/MyImage

# Or restore from backup: az backup restore restore-disks \ --resource-group MyResourceGroup \ --vault-name MyVault \ --container-name MyContainer \ --item-name MyVM \ --rp-name MyRecoveryPoint ```

Azure VM Not Starting Checklist

Check	Command	Expected
VM status	az vm show	PowerState/running
Size availability	az vm list-sizes	Size available
Quota	az vm list-usage	Within limits
Locks	az lock list	No blocking locks
Disk state	az disk show	Attached
Boot diagnostics	boot-diagnostics	Check for errors

Verification

```bash az vm show -g MyResourceGroup -n MyVM --query "instanceView.statuses"

az vm list-sizes --location eastus --query "[?name=='Standard_D2s_v3']"

az vm list-usage --location eastus --query "[?name.value=='standardDSv3Family']"

az vm boot-diagnostics get-boot-log -g MyResourceGroup -n MyVM

ssh user@public-ip ```

[Fix Azure VM Connection Failed](/articles/fix-azure-vm-connection-failed)
[Fix AWS EC2 Instance Not Starting](/articles/fix-aws-ec2-instance-not-starting)
[Fix Azure Resource Group Not Found](/articles/fix-azure-resource-group-not-found)

[Technical troubleshooting: Fix Azure Aks Pod Crashloopbackoff Issue in Azure](azure-aks-pod-crashloopbackoff)
[Technical troubleshooting: Fix Azure Api Management Policy Expression Runtime](azure-api-management-policy-expression-runtime-error)
[Technical troubleshooting: Fix Azure App Configuration Feature Flag Not Refre](azure-app-configuration-feature-flag-not-refreshing)
[Technical troubleshooting: Fix Azure App Service 503 Always On Disabled Issue](azure-app-service-503-always-on-disabled)
[Technical troubleshooting: Fix Azure Application Gateway Err SSL Unrecognized](azure-application-gateway-err-ssl-unrecognized-name-alert)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Azure VM Not Starting Azure VM Not Starting Azure Azure VM Not Starting troubleshooting Azure VM Not Starting fix Resolve Azure VM not starting errors by checking VM size, resource availability, and configuration issues Azure Resolve Azure VM not starting errors by checking VM size, resource availability, and configuration issues

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Azure Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this azure-errors troubleshooting guide applies to my situation?

This guide is designed for azure-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these azure-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of azure-errors issue?

Most azure-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this azure-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for azure-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 12, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix Azure VM Not Starting

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check VM Status

Step 2: Check Allocation Status

Step 3: Check VM Size Availability

Step 4: Check Subscription Quota

Step 5: Try Different Region or Zone

Step 6: Check Resource Locks

Step 7: Check Disk Issues

Step 8: Check Network Configuration

Step 9: Check Boot Diagnostics

Step 10: Recreate VM

Azure VM Not Starting Checklist

Verification

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Azure Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix Azure VM Not Starting

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check VM Status

Step 2: Check Allocation Status

Step 3: Check VM Size Availability

Step 4: Check Subscription Quota

Step 5: Try Different Region or Zone

Step 6: Check Resource Locks

Step 7: Check Disk Issues

Step 8: Check Network Configuration

Step 9: Check Boot Diagnostics

Step 10: Recreate VM

Azure VM Not Starting Checklist

Verification

Related Issues

Related Articles

People also search for

Share this guide

More Azure Troubleshooting Guides

Browse Guides from Other Categories

Azure Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading