Azure Quota Manager
Check Azure limits, compare regional capacity, and request quota increases before deployments fail.
The skill explicitly prefers Azure CLI, identifies Reader/Quota Request Operator permissions, and warns against interpreting “No Limit” as unlimited; however, quota update/create operations cause external changes without an explicit user-confirmation gate, rollback or audit guidance, and sensitive subscription-data handling is unspecified, so points are deducted.
The main workflows, dependency installation, common errors, and unsupported providers are documented, and the shell script uses strict error settings; however, there are no skill-specific tests for key paths, while embedded Python JSON parsing, cross-platform behavior, and abnormal-output handling remain thinly evidenced. Static calibration therefore keeps the score below 10.
Trigger phrases, scenarios, parameters, and CLI/Portal/documentation boundaries are relatively clear; however, non-fit conditions for missing Azure CLI, insufficient permissions, regional/provider variation, Chinese-language use, and mainland-China network reachability are not addressed, so points are deducted.
The documentation is well layered and links the main file to commands.md, advanced-commands.md, and scripts; version, MIT licensing, publisher, repository CI, and security materials are present. It lacks a skill-specific changelog, FAQ, pinned dependency versions, and a clearly documented maintenance/update path, so it is not full marks.
The skill covers quota lookup, regional comparison, capacity calculation, and increase requests, with examples that are potentially directly usable; however, results depend on Azure authentication, permissions, the CLI extension, and provider support, and no committed execution evidence verifies this skill’s key outputs. Static calibration caps the score at 7.
Commands, scripts, and troubleshooting are inspectable, and the repository includes generic CI and test materials; however, those materials do not establish coverage of azure-quotas key paths, and no skill-specific acceptance cases, execution results, or independent corroboration are supplied, so only limited credit is justified.
- quota update/create may modify subscription quota; before execution, explicitly show the target subscription, region, resource name, and new limit and obtain user confirmation.
- The script can install the quota extension and call the active Azure account; verify identity, permissions, and network context to avoid acting on the wrong subscription.
- The provider support list, CLI behavior, and auto-approval statements may change with Azure versions and services; verify current official documentation before acting.
- Reachability of Azure Portal, Microsoft Learn, and Azure APIs from mainland-China networks is not documented; affected users may need an alternative network path.
What it does & when to use it
azure-quotas supports Azure deployment planning and capacity validation by checking quota limits, current usage, and available capacity for resource providers and regions. It makes Azure CLI the primary interface and covers quota discovery, regional comparison, increase requests, and troubleshooting. A central rule is that ARM resource types do not map one-to-one to quota resource names, so the correct name must be discovered first. It is a good fit for teams managing real Azure subscriptions, but it does not replace service-limit documentation or Azure approval processes.
It instructs an agent to install the Azure CLI quota extension and run commands such as az quota list, az quota show, az quota usage list, az quota usage show, and az quota update. Its PowerShell and Bash scripts can return quota limits, current usage, and available capacity, either for all quotas or a named quota. It builds scopes from subscriptions, providers, and regions, discovers the actual quota resource name, and provides multi-region comparison loops. When a provider is unsupported, it redirects the user to Azure service-limit documentation; for increase requests, it also shows how to inspect request status.
- An Azure infrastructure engineer validates capacity for VMs or other resources before deploying to a target region.
- A platform team investigates a QuotaExceeded error by comparing current usage with limits and choosing an increase request or another region.
- A cloud architect compares candidate Azure regions for available quota before selecting a deployment location.
- An operations engineer requests higher VM vCPU, public IP, or storage-account quotas and checks the request status.
- A developer first lists provider quotas when the quota name corresponding to an ARM resource type is unclear.
Pros & cons
- Covers pre-deployment checks, regional comparisons, quota increases, and common failure modes.
- Prioritizes Azure CLI and warns against interpreting REST or Portal No Limit values as unlimited capacity.
- Includes Bash and PowerShell scripts that calculate limits, usage, and available capacity together.
- Provides a concrete discovery workflow for quota names instead of guessing from ARM resource types.
- Requires Azure CLI, the quota extension, Azure authentication, and network access to query subscription data.
- Some providers are unsupported by the quota API, including Microsoft.DocumentDB, requiring Portal or service-limit documentation.
- Increase requests may require manual review, and non-adjustable quotas cannot be changed through ordinary increase requests.
- The source provides no skill-specific test coverage results or cross-client validation matrix.
How to install
Install the repository collection with npx skills add microsoft/skills. Select the needed skills in the wizard; skills are installed into the selected agent directory, such as .github/skills/ for GitHub Copilot. To use only this skill, copy the folder at .github/plugins/azure-skills/skills/azure-quotas/ and its SKILL.md into the target agent's skills directory. The source does not document the exact wizard flow for selecting one skill from this plugin.
How to use
With the skill loaded, use a request such as Check Azure quotas for Microsoft.Compute in eastus and show available vCPUs. or Compare quota availability for standardDSv3Family across eastus and westus2. Ensure Azure authentication is available and have the agent start with az quota; install the extension with az extension add --name quota if needed. Reader permission is required for viewing, while quota management requires Quota Request Operator permission.
Compared to similar skills
Compared with the Azure Portal, this skill makes Azure CLI the primary path and treats the Portal as a fallback. Compared with the Microsoft.Quota REST API, it recommends CLI because REST responses can show misleading No Limit values. It explicitly forbids using the azure-quota MCP server because the source describes it as unreliable.