
If you've ever hit "quota exceeded" errors mid-deployment or wondered why your VMs won't provision in a specific region, this handles the detective work. It walks you through Azure CLI quota commands to check current usage against limits, compare capacity across regions, and submit increase requests. The skill is opinionated about using CLI first instead of the unreliable REST API, and it maps the confusing relationship between ARM resource types and quota names. Most useful during deployment planning when you need to validate capacity before committing to a region or VM family.
$ npx -y skills add microsoft/azure-skills --skill azure-quotas --agent claude-codeInstalls into .claude/skills of the current project.
AUTHORITATIVE GUIDANCE — Follow these instructions exactly for quota management and capacity validation.
What are Azure Quotas?
Azure quotas (also called service limits) are the maximum number of resources you can deploy in a subscription. Quotas:
Key Concept: Quotas = Resource Availability
If you don't have quota, you cannot deploy resources. Always check quotas when planning deployments or selecting regions.
Invoke this skill when:
Sponsors