How do I install the Azure Quotas skill?

Run npx skillmds@latest add jonathan-vella/azure-quotas in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Azure Quotas safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Azure Quotas?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Azure Quotas free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Azure Quotas?

jonathan-vella (@jonathan-vella) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Azure Quotas by jonathan-vella — Agent Skill

Name: Azure Quotas
Author: jonathan-vella

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).

File contents

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

---name: azure-quotasdescription: **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).license: MIT---# Azure Quotas — Service Limits & Capacity ManagementAzure quotas (service limits) are the maximum number of resources you candeploy in a subscription. **Quotas = available capacity** — if you do nothave quota, you cannot deploy. Always check before planning deploymentsor 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`](references/commands.md) || Azure Portal | [My quotas](https://portal.azure.com/#blade/Microsoft_Azure_Capacity/QuotaMenuBlade/myQuotas) — 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](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits)> — never to REST API or Portal.## Rules1. ✅ Always check quotas before deployment2. ✅ Run `az quota list` first to discover correct quota resource names (ARM resource type ≠ quota resource name — there is **no 1:1 mapping**)3. ✅ Compare regions to find available capacity4. ✅ Request a 20% buffer above immediate needs5. ✅ CLI-first; REST API and Portal are fallback-only6. ✅ Monitor usage; alert at 80% threshold (Portal)## Steps1. Install: `az extension add --name quota`2. Discover quota resource names: `az quota list --scope ...` (match by `localizedValue`)3. Check current usage: `az quota usage show --resource-name <name>`4. Check quota limit: `az quota show --resource-name <name>`5. Validate capacity: `Available = Limit − (Usage + Need)`6. If sufficient → proceed; if insufficient → request increase or change regionFor the 4 detailed workflows (specific check, region compare, increase request,list-all), read [`references/core-workflows.md`](references/core-workflows.md).For ARM-to-quota name mapping examples and discovery workflow, read[`references/resource-name-mapping.md`](references/resource-name-mapping.md).For common errors (`ExtensionNotFound`, `BadRequest`, `QuotaExceeded`,`InvalidScope`) and supported/unsupported providers, read[`references/troubleshooting.md`](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 |

Frequently asked questions