AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-compute

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, capacity reservation (CRG), reserve, guarantee capacity, pre-provision, CRG association, CRG disassociation, machine enrollment (EMM), Essential Machine Management, monitor. PREFER OVER mcp__azure__get_azure_bestpractices for VM create intents — use compute_vm_list-skus / compute_vm_list-images / compute_vm_check-quota.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-compute at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 37

references/vm-quotas.md

VM Quota Validation Guide

Check Azure VM/VMSS quota availability before recommending or deploying. Ensures the subscription and region have sufficient vCPU capacity.

⚠️ NEVER use the azure-quota MCP server as as It is unreliable. Always try az quota CLI commands first.

Quota Structure

VM quotas are tracked at two levels under Microsoft.Compute:

| Quota Level | Resource Name | What It Limits | |---|---|---| | Total Regional | cores | All vCPUs across all families in a region | | Per-Family | e.g., standardDSv3Family | vCPUs for a specific VM family |

⚠️ Both levels must have capacity. A deployment fails if either is exceeded.

Common Quota Resource Names

See vm-families.md for quota resource names per VM family. Use az quota list to discover names not listed there.

⚠️ Do NOT guess quota names from SKU names. Use az quota list to discover correct resource names.

Quota Check Workflow

Option A: az vm list-usage (Recommended for VM quotas)

No extension required. Returns both current usage and limit in a single call for all VM families in a region — equivalent to running az quota usage show and az quota list together for VM vCPU quotas.

# All VM family quotas in a region
az vm list-usage --location <region> -o table

# Filter to a specific family
az vm list-usage --location <region> --query "[?contains(name.value,'<quotaName>')].{Name:name.localizedValue, QuotaName:name.value, Current:currentValue, Limit:limit}" -o table

💡 Tip: az vm list-usage is the simplest way to check VM quotas. Use az quota (Option B) when you need to request quota increases or manage quotas for non-VM resource types.

Option B: az quota CLI (For quota increases or non-VM resources)

Prerequisite: az extension add --name quota

| Step | Command | Purpose | |---|---|---| | 1. Discover names | az quota list --scope /subscriptions/<sub-id>/providers/Microsoft.Compute/locations/<region> -o table | Find quota resource name for the VM family | | 2. Check usage | az quota usage show --resource-name <name> --scope ... | Current vCPU consumption | | 3. Check limit | az quota show --resource-name <name> --scope ... | Maximum allowed vCPUs | | 4. Check regional | Repeat steps 2–3 with --resource-name cores | Total regional vCPU cap |

Calculate Capacity

Available = Limit - Current Usage  (check both family AND regional)
vCPUs Needed = vCPUs per VM × Instance Count

✅ Deploy if: vCPUs Needed ≤ min(Family Available, Regional Available)
❌ Blocked if: either is exceeded

Example: 3× Standard_D4s_v5 (4 vCPUs each) = 12 needed. Family: 100−40 = 60 ✅. Regional: 350−280 = 70 ✅.

Handling Insufficient Quota

| Option | Action | |---|---| | Request increase | az quota update --resource-name <name> --scope ... --limit-object value=<new-limit> --resource-type dedicated. Most increases auto-approve within minutes. | | Try different region | Run the quota check workflow against alternative regions to find available capacity | | Switch VM family | Recommend an alternative family with quota (e.g., D-series full → Dads v5 AMD variant) |

VMSS Considerations

For scale sets, validate against autoscale maximum: vCPUs per VM × Max Instance Count.

| Autoscale Setting | vCPUs to Validate | |---|---| | Fixed count (5 instances) | vCPUs × 5 | | Autoscale min=2, max=10 | vCPUs × 10 |

Error Reference

| Error | Cause | Action | |---|---|---| | QuotaExceeded | Family vCPU limit reached | Request increase or change family/region | | OperationNotAllowed | Subscription lacks capacity | Request quota increase | | cores limit hit | Regional vCPUs exhausted | Request regional increase | | CLI commands fail entirely | Auth/extension issue | Use MCP fallback (see below) |

Related Resources