Source: microsoft/azure-skills · Maintainer: Microsoft · License: MIT · Checked: 27 October 2026
What is the Azure quotas skill?
The Azure quotas skill teaches a coding agent to check how much of each Azure quota you have used, how much is left, and where you have room to deploy. It runs the az quota CLI extension, ships two scripts that print limit, usage and available capacity in one table, and can file an increase request.
Its description reads: "Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection." Trigger phrases include "quota exceeded", "request quota increase", "vCPU limit" and "how many vCPUs available in my subscription".
The skill ships in microsoft/azure-skills, the Azure Skills Plugin. The README lists it under "Troubleshoot, monitor, and govern". The SKILL.md frontmatter lists version 1.2.2 and author Microsoft.
As of 27 October 2026, its skills.sh page listed about 471,700 installs (snapshot, 27 October 2026).
What does it do?
The SKILL.md is about 12 KB and opens with a firm instruction: "Follow these instructions exactly for quota management and capacity validation."
CLI first, always. The quick reference names az quota as the primary tool, "USE THIS FIRST, ALWAYS". The portal is a fallback. The REST API is marked "Unreliable, do NOT use first", and the azure-quota MCP server gets "NEVER use this". The reason it gives: the portal and REST API can show "No Limit", which "does not mean unlimited capacity" but that the quota API doesn't support that resource type.
Find the real quota name. The skill warns there is "NO 1:1 mapping" between ARM resource types and quota names. Its examples:
| ARM resource type | Quota resource names |
|---|---|
Microsoft.App/managedEnvironments |
ManagedEnvironmentCount |
Microsoft.Compute/virtualMachines |
standardDSv3Family, cores, virtualMachines |
Microsoft.Network/publicIPAddresses |
PublicIPAddresses, IPv4StandardSkuPublicIpAddresses |
So the agent runs az quota list for the provider and region first, matches on the readable localizedValue, and uses the name field in later commands.
Run the scripts. scripts/check-quota.sh and scripts/check-quota.ps1 take a provider, a region and an optional quota name. They install the quota extension if it's missing, read your current subscription, and print a table of limit, usage and available capacity. Per the az quota reference on Microsoft Learn, the extension also installs itself the first time you run an az quota command.
./scripts/check-quota.sh Microsoft.Compute eastus standardDSv3Family
Compare regions. A Bash loop checks one quota across several regions and prints limit, usage and available for each, so the agent can suggest where to deploy.
Request an increase. The skill uses az quota update with --limit-object value=500 and --resource-type dedicated for a VM family, then az quota request status list to follow the request. It says most adjustable quotas are approved in minutes, some need manual review, and non-adjustable ones need a support ticket.
Troubleshoot. A table maps errors to fixes: ExtensionNotFound, BadRequest (provider not supported), MissingRegistration (register Microsoft.Quota), QuotaExceeded and InvalidScope. It lists Cosmos DB (Microsoft.DocumentDB) as unsupported, and Compute, Network, Container Apps, Storage and Machine Learning as confirmed working.
How do you install the Azure quotas skill?
The repo README documents several routes.
Claude Code: the Azure Skills Plugin. Run inside Claude Code:
/plugin install azure@claude-plugins-official
Or run /plugin and search for "azure". Update later with /plugin update azure@claude-plugins-official. See Claude Code plugins and Claude Code MCP.
GitHub Copilot CLI:
/plugin marketplace add microsoft/azure-skills
/plugin install azure@azure-skills
Codex, Cursor and Gemini CLI. For Codex, the README says to run codex plugin marketplace add microsoft/azure-skills, then install azure from /plugins. For Cursor, use the Cursor Marketplace or Settings, then Plugins. For Gemini CLI, run gemini extensions install https://github.com/microsoft/azure-skills. See Codex skills and Cursor skills.
Skill only. The command on skills.sh copies just this folder, scripts included:
npx skills add https://github.com/microsoft/azure-skills --skill azure-quotas
Prerequisites: the README asks for an Azure subscription, Node.js 18 or later and the Azure CLI signed in with az login. The skill adds Reader access to view quotas or Quota Request Operator to manage them. The Bash script also calls python3 in all-quotas mode.
How do you use it?
Say what you plan to deploy and where. The skill is model-invoked, so the agent loads it when your request matches its triggers.
Example prompts (suggestions; the last one is a trigger phrase from the skill):
Check my Microsoft.Compute quotas in eastus and show what's left.I need 64 vCPUs of DSv3 for a cluster. Which of eastus, eastus2 and westus2 has room?Our deployment failed with QuotaExceeded on public IPs in westeurope. What's the limit and what's used?Request an increase of standardDSv3Family in eastus to 200 vCPUs and tell me how to track it.How many vCPUs available in my subscription?
Expect a table of limit, usage and available capacity, then a suggestion: deploy, switch region, or request more.
Tips and limits
From the repo, Microsoft Learn and skills.sh, not from testing:
- Quota is not reserved capacity. The skill says quotas "Represent available capacity in each region". Microsoft's quotas overview says "An assigned Quota does not reserve or guarantee capacity for Customer use, and capacity may not be available at the time of request." A region can still be short on capacity when you have quota.
- Approval isn't automatic. Microsoft Learn says approval "is subject to Microsoft's review, including consideration of current usage, service availability, and capacity constraints". Treat the skill's "usually auto-approved" as a typical case.
- Requests are free. Both agree. The skill says requesting increases is free, and Microsoft Learn says "There's no cost associated with requesting a quota increase."
- Provider support varies. Microsoft's overview table lists Compute and Machine Learning under the Quota APIs, while the skill lists more providers as working. If a provider returns
BadRequest, the skill points to the Azure subscription and service limits page. - It can change limits.
az quota updatesubmits a real request against your subscription. Read the scope and value before you approve it. - Audits. On skills.sh, Gen Agent Trust Hub and Snyk rated the skill Pass on 14 October 2026. Socket rated it Warn (medium) the same day, describing check-quota.sh as "a legitimate Azure quota-reporting script with no clear malicious intent" but flagging that its all-quotas mode embedded Azure JSON and the region argument directly into generated Python. A repo sync on 14 October 2026 changed that code to read the JSON from stdin and the region as an argument. It isn't clear from skills.sh which version was scanned.
The MIT License lets you copy and change the skill as long as you keep Microsoft's copyright and license notices.
Save it in your Kipt library
An edited copy helps if your team has fixed regions, a standard VM family or a rule like "never file increases without a ticket number". In Kipt, open Skills and paste the skill's GitHub folder link into the import box, or drop the folder or a .zip; the scripts come with it. Skills in your private GitHub repo install into Claude Code or Codex with one command:
npx skills add https://github.com/<you>/<repo>.git --all -g
Kipt is not affiliated with Microsoft.
Similar skills
- Azure prepare skill: plans the deployment that a quota check should come before.
- Azure deploy skill: runs the deployment once you know there's room.
- Azure resource lookup skill: lists what you already have running in a subscription.
- Azure validate skill: checks a project is ready to deploy.
- Azure compute skill: picks and prices VM sizes and checks their quota before creating VMs.
- Azure diagnostics skill: troubleshooting after a deployment fails for other reasons.