Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
Seen on:
Azure
Meaning
Capacity and SKU availability vary by region, zone and subscription type (free/student subscriptions are restricted). Quotas cap total and per-family vCPUs per region.
Common causes
- VM size not available in the region/zone
- Subscription restricted from that SKU
- Regional or VM-family vCPU quota reached
- Temporary capacity shortage
⚡ Quick fix
- List available sizes:
az vm list-skus -l <region> --size Standard_D -o table - Choose another size, zone or region
- Request a quota increase (Portal → Quotas)
Detailed fix by platform
Azure
- Check SKUs and usage:bash
az vm list-skus --location centralindia --resource-type virtualMachines --query "[?restrictions==\`[]\`].name" -o tsv | head az vm list-usage --location centralindia -o table
How to diagnose
- SKU — Is the size listed without restrictions?
- Quota — Current vs limit for that family
- Region — Can another region/zone work?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026