Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/microsoft-foundry/models/deploy-model/capacity

capacity

Unverified

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

Capacity Discovery

Finds available Azure OpenAI model capacity across all accessible regions and projects. Recommends the best deployment location based on capacity requirements.

Quick Reference

PropertyDescription
PurposeFind where you can deploy a model with sufficient capacity
ScopeAll regions and projects the user has access to
OutputRanked table of regions/projects with available capacity
ActionRead-only analysis — does NOT deploy. Hands off to preset or customize
AuthenticationAzure CLI (az login)

When to Use This Skill

  • ✅ User asks "where can I deploy gpt-4o?"
  • ✅ User specifies a capacity target: "find a region with 10K TPM for gpt-4o"
  • ✅ User wants to compare availability: "which regions have gpt-4o available?"
  • ✅ User got a quota error and needs to find an alternative location
  • ✅ User asks "best region and project for deploying model X"

After discovery → hand off to preset or customize for actual deployment.

Scripts

Pre-built scripts handle the complex REST API calls and data processing. Use these instead of constructing commands manually.

ScriptPurposeUsage
scripts/discover_and_rank.ps1Full discovery: capacity + projects + rankingPrimary script for capacity discovery
scripts/discover_and_rank.shSame as above (bash)Primary script for capacity discovery
scripts/query_capacity.ps1Raw capacity query (no project matching)Quick capacity check or version listing
scripts/query_capacity.shSame as above (bash)Quick capacity check or version listing

Workflow

Phase 1: Validate Prerequisites

az account show --query "{Subscription:name, SubscriptionId:id}" --output table

Phase 2: Identify Model and Version

Extract model name from user prompt. If version is unknown, query available versions:

.\scripts\query_capacity.ps1 -ModelName <model-name>
./scripts/query_capacity.sh <model-name>

This lists available versions. Use the latest version unless user specifies otherwise.

Phase 3: Run Discovery

Run the full discovery script with model name, version, and minimum capacity target:

.\scripts\discover_and_rank.ps1 -ModelName <model-name> -ModelVersion <version> -MinCapacity <target>
./scripts/discover_and_rank.sh <model-name> <version> <min-capacity>

💡 The script automatically queries capacity across ALL regions, cross-references with the user's existing projects, and outputs a ranked table sorted by: meets target → project count → available capacity.

Phase 3.5: Validate Subscription Quota

After discovery identifies candidate regions, validate that the user's subscription actually has available quota in each region. Model capacity (from Phase 3) shows what the platform can support, but subscription quota limits what this specific user can deploy.

# For each candidate region from discovery results:
$usageData = az cognitiveservices usage list --location <region> --subscription $SUBSCRIPTION_ID -o json 2>$null | ConvertFrom-Json

# Check quota for each SKU the model supports
# Quota names follow pattern: OpenAI.<SKU>.<model-name>
$usageEntry = $usageData | Where-Object { $_.name.value -eq "OpenAI.<SKU>.<model-name>" }

if ($usageEntry) {
  $quotaAvailable = $usageEntry.limit - $usageEntry.currentValue
} else {
  $quotaAvailable = 0  # No quota allocated
}
# For each candidate region from discovery results:
usage_json=$(az cognitiveservices usage list --location <region> --subscription "$SUBSCRIPTION_ID" -o json 2>/dev/null)

# Extract quota for specific SKU+model
quota_available=$(echo "$usage_json" | jq -r --arg name "OpenAI.<SKU>.<model-name>" \
  '.[] | select(.name.value == $name) | .limit - .currentValue')

Annotate discovery results:

Add a "Quota Available" column to the ranked output from Phase 3:

RegionAvailable CapacityMeets TargetProjectsQuota Available
eastus2120K TPM✅3✅ 80K
westus390K TPM✅1❌ 0 (at limit)
swedencentral100K TPM✅0✅ 100K

Regions/SKUs where quotaAvailable = 0 should be marked with ❌ in the results. If no region has available quota, hand off to the quota skill for increase requests and troubleshooting.

Phase 4: Present Results and Hand Off

After the script outputs the ranked table (now annotated with quota info), present it to the user and ask:

  1. 🚀 Quick deploy to top recommendation with defaults → route to preset
  2. ⚙️ Custom deploy with version/SKU/capacity/RAI selection → route to customize
  3. 📊 Check another model or capacity target → re-run Phase 2
  4. ❌ Cancel

Phase 5: Confirm Project Before Deploying

Before handing off to preset or customize, always confirm the target project with the user. See the Project Selection rules in the parent router.

If the discovery table shows a sample project for the chosen region, suggest it as the default. Otherwise, query projects in that region and let the user pick.

Error Handling

ErrorCauseResolution
"No capacity found"Model not available or all at quotaHand off to quota skill for increase requests and troubleshooting
Script auth erroraz login expiredRe-run az login
Empty version listModel not in region catalogTry a different region: ./scripts/query_capacity.sh <model> "" eastus
"No projects found"No AI Services resourcesGuide to project/create skill or Azure Portal

Related Skills

  • preset — Quick deployment after capacity discovery
  • customize — Custom deployment after capacity discovery
  • quota — For quota viewing, increase requests, and troubleshooting quota errors, defer to this skill instead of duplicating guidance
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall