Skip to content

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

preset

Verified

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

Deploy Model to Optimal Region

Automates intelligent Azure OpenAI model deployment by checking capacity across regions and deploying to the best available option.

What This Skill Does

  1. Verifies Azure authentication and project scope
  2. Checks capacity in current project's region
  3. If no capacity: analyzes all regions and shows available alternatives
  4. Filters projects by selected region
  5. Supports creating new projects if needed
  6. Deploys model with GlobalStandard SKU
  7. Monitors deployment progress

Prerequisites

  • Azure CLI installed and configured
  • Active Azure subscription with Cognitive Services read/create permissions
  • Azure AI Foundry project resource ID (PROJECT_RESOURCE_ID env var or provided interactively)
    • Format: /subscriptions/{sub-id}/resourceGroups/{rg}/providers/Microsoft.CognitiveServices/accounts/{account}/projects/{project}
    • Found in: Azure AI Foundry portal → Project → Overview → Resource ID

Quick Workflow

Fast Path (Current Region Has Capacity)

1. Check authentication → 2. Get project → 3. Check current region capacity
→ 4. Deploy immediately

Alternative Region Path (No Capacity)

1. Check authentication → 2. Get project → 3. Check current region (no capacity)
→ 4. Query all regions → 5. Show alternatives → 6. Select region + project
→ 7. Deploy

Deployment Phases

PhaseActionKey Commands
1. Verify AuthCheck Azure CLI login and subscriptionaz account show, az login
2. Get ProjectParse PROJECT_RESOURCE_ID ARM ID, verify existsaz cognitiveservices account show
3. Get ModelList available models, user selects model + versionaz cognitiveservices account list-models
4. Check Current RegionQuery capacity using GlobalStandard SKUaz rest --method GET .../modelCapacities
5. Multi-Region QueryIf no local capacity, query all regionsSame capacity API without location filter
6. Select Region + ProjectUser picks region; find or create projectaz cognitiveservices account list, az cognitiveservices account create
7. DeployGenerate unique name, calculate capacity (50% available, min 50 TPM), create deploymentaz cognitiveservices account deployment create

For detailed step-by-step instructions, see workflow reference.


Error Handling

ErrorSymptomResolution
Auth failureaz account show returns errorRun az login then az account set --subscription <id>
No quotaAll regions show 0 capacityDefer to the quota skill for increase requests and troubleshooting; check existing deployments; try alternative models
Model not foundEmpty capacity listVerify model name with az cognitiveservices account list-models; check case sensitivity
Name conflict"deployment already exists"Append suffix to deployment name (handled automatically by generate_deployment_name script)
Region unavailableRegion doesn't support modelSelect a different region from the available list
Permission denied"Forbidden" or "Unauthorized"Verify Cognitive Services Contributor role: az role assignment list --assignee <user>

Advanced Usage

# Custom capacity
az cognitiveservices account deployment create ... --sku-capacity <value>

# Check deployment status
az cognitiveservices account deployment show --name <acct> --resource-group <rg> --deployment-name <name> --query "{Status:properties.provisioningState}"

# Delete deployment
az cognitiveservices account deployment delete --name <acct> --resource-group <rg> --deployment-name <name>

Notes

  • SKU: GlobalStandard only — API Version: 2024-10-01 (GA stable)

Related Skills

  • microsoft-foundry - Parent skill for Azure AI Foundry operations
  • quota — For quota viewing, increase requests, and troubleshooting quota errors, defer to this skill
  • azure-quick-review - Review Azure resources for compliance
  • azure-cost-estimation - Estimate costs for Azure deployments
  • azure-validate - Validate Azure infrastructure before deployment
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 CodeCodexVerifiedInstall