azure-quotas

**UTILITY SKILL** — Check and manage Azure quotas and usage across providers for deployment planning, capacity validation, and region selection. WHEN: "check quotas", "service limits", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "vCPU limit". DO NOT USE FOR: deployment execution (azure-deploy), cost analysis (azure-cost-optimization).

Quality

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Azure Quotas — Service Limits & Capacity Management

Azure quotas (service limits) are the maximum number of resources you can deploy in a subscription. Quotas = available capacity — if you do not have quota, you cannot deploy. Always check before planning deployments or selecting regions.

Prerequisites

Azure CLI ≥ 2.50 authenticated (az login)
CLI extension: az extension add --name quota (install once)
RBAC: Reader to view quotas; Quota Request Operator to submit increases

Quick Reference

Property	Details
Primary tool	Azure CLI (`az quota`) — always use first
Extension	`az extension add --name quota` (install once)
Key commands	`az quota list`, `az quota show`, `az quota usage list`, `az quota usage show`
Full CLI reference	`references/commands.md`
Azure Portal	My quotas — fallback only
REST API	Microsoft.Quota provider — unreliable, do NOT use first
Required permission	Reader (view) or Quota Request Operator (manage)

CLI-first is mandatory. REST API and Portal report "No Limit" / "Unlimited" when the API does not cover a resource type — not when capacity is unlimited. Service-specific hard limits still apply. If CLI returns BadRequest, fall back to Azure service limits docs — never to REST API or Portal.

Rules

✅ Always check quotas before deployment
✅ Run az quota list first to discover correct quota resource names (ARM resource type ≠ quota resource name — there is no 1:1 mapping)
✅ Compare regions to find available capacity
✅ Request a 20% buffer above immediate needs
✅ CLI-first; REST API and Portal are fallback-only
✅ Monitor usage; alert at 80% threshold (Portal)

Steps

Install: az extension add --name quota
Discover quota resource names: az quota list --scope ... (match by localizedValue)
Check current usage: az quota usage show --resource-name <name>
Check quota limit: az quota show --resource-name <name>
Validate capacity: Available = Limit − (Usage + Need)
If sufficient → proceed; if insufficient → request increase or change region

For the 4 detailed workflows (specific check, region compare, increase request, list-all), read references/core-workflows.md.

For ARM-to-quota name mapping examples and discovery workflow, read references/resource-name-mapping.md.

For common errors (ExtensionNotFound, BadRequest, QuotaExceeded, InvalidScope) and supported/unsupported providers, read references/troubleshooting.md.

Reference Index

Reference	When to Load
`references/commands.md`	Full `az quota` CLI command reference
`references/advanced-commands.md`	Less-common quota CLI patterns
`references/core-workflows.md`	Detailed check, compare, increase, and list workflows
`references/troubleshooting.md`	Common errors and unsupported providers
`references/resource-name-mapping.md`	ARM-to-quota resource name mapping and discovery

Repository: jonathan-vella/azure-agentic-infraops
Commit: 05d7617

Last updated: 5 days ago
Created: 5 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.