azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: \"check quotas\", \"service limits\", \"current usage\", \"request quota increase\", \"quota exceeded\", \"validate capacity\", \"regional availability\", \"provisioning limits\", \"vCPU limit\", \"how many vCPUs available in my subscription\".
Profile →npx skills add microsoft/azure-skills --skill azure-quotas --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Azure Quotas - Service Limits & Capacity Management > **AUTHORITATIVE GUIDANCE** — Follow these instructions exactly for quota management and capacity validation. ## Overview **What are Azure Quotas?** Azure quotas (also called service limits) are the maximum number of resources you can deploy in a subscription. Quotas: - Prevent accidental over-provisioning - Ensure fair resource distribution across Azure - Represent **available capacity** in each region - Can be increased (adjustable quotas) or are fixed (non-adjustable) **Key Concept:** **Quotas = Resource Availability** If you don't have quota, you cannot deploy resources. Always check quotas when planning deployments or selecting regions. ## When to Use This Skill Invoke this skill when: - **Planning a new deployment** - Validate capacity before deployment - **Selecting an Azure region** - Compare quota availability across regions - **Troubleshooting quota exceeded errors** - Check current usage vs limits - **Requesting quota increases** - Submit increase requests via CLI or Portal - **Comparing regional capacity** - Find regions with available quota - **Validating provisioning limits** - Ensure deployment won't exceed quota
- Overview
- When to Use This Skill
- Quick Reference
- Quota Types
- Understanding Resource Name Mapping
- Example Mappings
- Discovery Workflow
- Scripts
- Core Workflows
- Workflow 1: Check Quota for a Specific Resource
- Workflow 2: Compare Quotas Across Regions
- Workflow 3: Request Quota Increase
- Workflow 4: List All Quotas for Planning
- Troubleshooting
az quota list --scope /subscriptions/<id>/providers/<ProviderNamespace>/locations/<region>
az quota show --resource-name ManagedEnvironmentCount --scope ...
az quota usage show --resource-name ManagedEnvironmentCount --scope ...
Define candidate regions
Check quota availability across regions
for region in "${REGIONS[@]}"; do
echo "=== Checking $region ==="
echo "Region: $region | Limit: $LIMIT | Usage: $USAGE | Available: $AVAILABLE"
done
Request increase for VM quotaWhat does the azure-quotas skill do?
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: \"check quotas\", \"service limits\", \"current usage\", \"request quota increase\", \"quota exceeded\", \"validate capacity\", \"regional availability\", \"provisioning limits\", \"vCPU limit\", \"how many vCPUs available in my subscription\".
How do I install it?
Run `npx skills add microsoft/azure-skills --skill azure-quotas --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From microsoft/azure-skills, a repository with 1,353 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.