Map Azure deployments to every relevant quota, calculate regional headroom, and control increase requests without confusing assigned limits with capacity.
A deployment can clear its VM-family quota and still fail the regional core limit. A timed-out increase request can be retried before anyone knows whether Azure accepted the first one. Even an approved quota does not reserve the underlying SKU or guarantee physical capacity.
Azure Quota Management turns deployment demand into a reviewable quota decision. It binds tenant, subscription, provider, region, quota name, unit, observation time, and authority. It maps every constraining dimension, calculates post-deployment usage and explicit buffer, compares regions without ignoring residency or architecture, and prepares an exact approval-bound increase request when headroom is short.
The workflow also handles the awkward failure path: a quota mutation times out with no request ID. It preserves the original attempt, checks request history, current limit and usage, activity evidence, and support records, then blocks a duplicate until the result can be reconciled. A canonical JSON contract and read-only checker keep the math, request state, approval, and verdict internally consistent. The checker does not contact Azure, validate permissions, guarantee capacity, authorize a request, or deploy resources.
Version 1.0.0 was reviewed on 2026-07-17 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 96.25 across three cases, compared with 55.42 for the same agent without the skill and 75.42 for the exact free upstream. All cases passed. It led the upstream by 25 points on a multi-quota deployment assessment, tied it on the supplied canonical request packet, and led by 37.5 points on ambiguous-timeout recovery. The evaluation covers those supplied cases. It does not prove that an Azure tenant, subscription, quota, request, permission, regional capacity, or deployment matches supplied evidence.
The reviewed package SHA-256 is e488be1602048c62214758d7d053baf379ee125238fe800bf91c64892e42a45d. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Six Standard_D8s_v5 VMs need 48 vCPUs in eastus. Another approved batch will consume 16. Policy requires 8 unused vCPUs after rollout. Family limit/usage is 80/24; regional total is 120/56.
Output
Two scope-bound quota rows, explicit post-deployment and buffer math, minimum limits of 96 and 128, separate increase targets, an insufficient verdict, and no claim that quota approval guarantees capacity.
Input
Create canonical JSON for an approved increase of standardDSv5Family from 80 to 96 in eastus. The exact scope, demand, buffer, approver, and operation key are supplied; no request has run.
Output
A machine-checkable request-ready record with exact scope, quota name, derived limit, approval binding, not-run execution state, physical-capacity caveat, and an authorized submission next action.
Provide the deployment or incident request, tenant and subscription, candidate regions, Azure resource or SKU, instance count and units, rollout or failover commitments, explicit buffer policy, current quota evidence, authority, and the action you want: assess, plan, request, reconcile, or verify. The skill maps the required quota dimensions, shows the math, and stops before an unapproved or duplicate mutation.
Tenant, subscription, authenticated principal, provider, candidate region, and permission to read quota evidence.
Resource or SKU, instance count, unit conversion, rollout overlap, autoscale or failover demand, concurrent commitments, and explicit buffer policy.
Discovered quota names, exact scopes, units, current limits and usage, observation times, adjustability, and source details.
Exact approval for any increase request plus access to request history, limit and usage read-back, activity evidence, and support records for reconciliation.
SKILL.md; controlled Azure quota assessment, request, reconciliation, and verification workflow; canonical quota-record contract; read-only quota-record checker; Agent Skills interface metadata
No reviews yet.
Input
A request to raise standardDSv5Family from 80 to 120 timed out without an exit status or request ID. Four minutes later the limit is still 80, and request history returns 503. The operator wants to retry now.
Output
An unknown verdict that blocks the duplicate, preserves the original digest and operation key, names every read-only evidence surface, branches on match and conflict states, and requires fresh approval after a proven no-match.
Creator
Wweravo27
