azure-quotas

Check and manage Azure subscription quotas and usage for capacity validation and region selection.

Updated May 12, 2026
One-click install
npx skills add https://github.com/sohamda/apex-try-out-demo-repo --skill azure-quotas-sohamda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-quotas
Source: https://github.com/sohamda/apex-try-out-demo-repo/tree/main/.github/skills/azure-quotas
Command: npx skills add https://github.com/sohamda/apex-try-out-demo-repo --skill azure-quotas-sohamda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deployments fail when Azure subscriptions lack sufficient quota, and quota resource names do not map directly to ARM resource types, making capacity validation error-prone. This Skill provides a CLI-first workflow to discover quota names, check limits and usage, compare regional capacity, and request increases before deployment. ## Core Features & Use Cases - Quota Discovery and Validation: Use az quota list, az quota show, and az quota usage show to find correct quota resource names and calculate available capacity (Limit - Usage). - Regional Capacity Comparison: Compare quota availability across multiple regions with bash scripts to select the best deployment target. - Quota Increase Requests: Submit and track quota increase requests via az quota update and az quota request status. - Use Case: Before deploying a VM cluster requiring 100 DSv3 vCPUs, run the quota check workflow to confirm East US has 300 available vCPUs, or request an increase with a 20% buffer if capacity is insufficient. ## Quick Start Ask the agent to check whether your subscription has enough vCPU quota in East US for a planned VM deployment using the azure-quotas skill.

Frequently Asked Questions about azure-quotas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Azure quota limits with Azure CLI?▼

Install the quota extension with `az extension add --name quota`, then run `az quota list` with a scope like `/subscriptions/{id}/providers/Microsoft.Compute/locations/eastus` to discover quota names, and `az quota show` to view specific limits.

How to request an Azure quota increase from the command line?▼

Use `az quota update` with the resource name, scope, and `--limit-object value=N` to submit an increase request. Track approval status with `az quota request status list`; most adjustable quotas are auto-approved within minutes.

Why does the Azure REST API show No Limit for quotas?▼

No Limit in REST API or Portal responses usually means the resource provider does not support the quota API, not that capacity is unlimited. Always use `az quota` CLI commands first, and fall back to Azure service limits documentation if the CLI returns BadRequest.

Which Azure resource providers support the quota CLI?▼

Confirmed supported providers include Microsoft.Compute, Microsoft.Network, Microsoft.App, Microsoft.Storage, Microsoft.MachineLearningServices, and Microsoft.ContainerService. Microsoft.DocumentDB (Cosmos DB) is not supported and returns BadRequest.

Why is there no direct mapping between ARM resource types and quota names?▼

Azure quota resource names differ from ARM resource type names, so you must discover them by running `az quota list` and matching the `localizedValue` field. For example, Container Apps environments map to the quota name ManagedEnvironmentCount.