customize
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
npx skills add microsoft/azure-skills --skill customize --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Customize Model Deployment Interactive guided workflow for deploying Azure OpenAI models with full customization control over version, SKU, capacity, content filtering, and advanced options. ## Quick Reference | Property | Description | |----------|-------------| | **Flow** | Interactive step-by-step guided deployment | | **Customization** | Version, SKU, Capacity, RAI Policy, Advanced Options | | **SKU Support** | GlobalStandard, Standard, ProvisionedManaged, DataZoneStandard | | **Best For** | Precise control over deployment configuration | | **Authentication** | Azure CLI (`az login`) | | **Tools** | Azure CLI, MCP tools (optional) | ## When to Use This Skill Use this skill when you need **precise control** over deployment configuration: - ✅ **Choose specific model version** (not just latest) - ✅ **Select deployment SKU** (GlobalStandard vs Standard vs PTU) - ✅ **Set exact capacity** within available range - ✅ **Configure content filtering** (RAI policy selection) - ✅ **Enable advanced features** (dynamic quota, priority processing, spillover) - ✅ **PTU deployments** (Provisioned Throughput Units) **Alternative:** Use `preset` for quick deployment to the best available region
- Quick Reference
- When to Use This Skill
- Comparison: customize vs preset
- Prerequisites
- Workflow Overview
- Complete Flow (14 Phases)
- Fast Path (Defaults)
- Phase Summaries
- Error Handling
- Common Issues and Resolutions
- Troubleshooting Commands
- Selection Guides & Advanced Topics
- Related Skills
- Notes
Check deployment status az cognitiveservices account deployment show --name <account> --resource-group <rg> --deployment-name <name> List all deployments az cognitiveservices account deployment list --name <account> --resource-group <rg> -o table Check quota usage az cognitiveservices usage list --name <account> --resource-group <rg> Delete failed deployment az cognitiveservices account deployment delete --name <account> --resource-group <rg> --deployment-name <name>
What does the customize skill do?
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
How do I install it?
Run `npx skills add microsoft/azure-skills --skill customize --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From microsoft/azure-skills, a repository with 1,353 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.