Azure OpenAI Optimal Region Deployment
Automatically checks Azure capacity and deploys an Azure OpenAI model in a suitable available region.
The document requires Azure authentication, a project resource ID, and region selection, and explicitly asks the user to choose the Anthropic industry field. However, resource creation, model deployment, and potentially billable external changes lack a final pre-deployment confirmation, cost warning, detailed least-privilege guidance, and rollback procedure; deletion is only shown as an advanced command, and tenant-data flow disclosure is limited, so points are deducted.
The main flow, error table, and deployment polling are reasonably detailed, with actionable failure guidance. However, the two workflow references disagree on model-format handling, capacity calculation, and quota paths; jq, awk, openssl, and scripts not verified in the supplied material are required, and several edge cases are thinly handled, so the score remains below the static ceiling.
Trigger terms and excluded scenarios are relatively clear in the front matter, covering local capacity, alternative regions, and project creation. Inputs, output guarantees, and region-selection policy still depend on interaction, non-Azure boundaries are not defined, Chinese-language support is absent, and Azure CLI/management-API reachability is not discussed, so points are deducted.
The skill includes MIT licensing, author and version metadata, phased information architecture, prerequisites, examples, error handling, and related-skill links. It lacks a changelog, explicit maintenance owner and update path, and complete installation guidance for referenced scripts and tools; inconsistencies between references also reduce maintainability.
It supplies directly reusable Azure CLI, REST, and polling commands covering deployment, alternate regions, project creation, and quota failure guidance, so the core value is clear. Yet example outcomes and timings are not statically verifiable, script availability is unproven, and conflicting capacity logic creates implementation risk; therefore the score stays within the static limit and is reduced.
Specific commands, API versions, error paths, and repository-level CI/test material provide some auditability. The supplied CI tests do not demonstrate this target skill's key paths, and the successful example results and timing claims lack third-party execution evidence, so only limited credit is warranted.
- Deployment and resource creation are external, potentially billable changes; add explicit final confirmation, cost/quota warnings, and a documented recovery plan before execution.
- The two workflow references conflict on OpenAI versus non-OpenAI handling, capacity calculation, and quota relative paths; reconcile and validate them first.
- The availability and behavior of generate_deployment_name, generate_deployment_url, jq, awk, and openssl are not fully evidenced in the supplied target materials.
- The Anthropic flow reads tenant countryCode and displayName; document purpose, permission scope, and sensitive-data handling.
What does this skill do, and when should you use it?
This skill is a focused model-deployment workflow from the Azure AI Foundry portion of Microsoft’s Agent Skills repository. It verifies Azure authentication and project scope, checks the current region, and searches other regions when local capacity is unavailable. It can filter or create a project, deploy with the GlobalStandard SKU, and monitor progress. It is a good fit for fast, standard deployments, but not for custom SKUs, versions, capacity settings, or PTU deployments.
Checks Azure CLI authentication and subscription context; parses and verifies an Azure AI Foundry project resource ID; lists available models for selection; queries GlobalStandard capacity through the Azure REST API; queries alternative regions when the current region lacks capacity; filters or creates a project in the selected region; generates a unique deployment name, calculates deployment capacity, creates the deployment, and monitors its progress.
- An Azure AI Foundry developer wants to deploy quickly when the current project region has capacity.
- A platform engineer needs to compare Azure regions after the current region reports no capacity.
- A team wants to deploy a model through Azure CLI into an existing or newly created Foundry project.
- A prototype needs a standard GlobalStandard deployment and can accept automatic region selection.
What are this skill's strengths and limitations?
- Checks the current project region first and searches alternatives when capacity is unavailable.
- Covers authentication, project verification, capacity discovery, project selection, deployment, and progress monitoring.
- Can create a new project in the selected region when needed.
- The collection supports installation with `npx skills add microsoft/skills` and multi-agent setups.
- Supports GlobalStandard only; custom SKU, version, capacity, and PTU deployments should use the customize skill.
- Requires Azure CLI, an active subscription, a project resource ID, and appropriate Cognitive Services permissions.
- Deployment depends on live regional capacity and model availability, so the workflow cannot guarantee success.
- The supplied material provides no skill-specific test results; the repository is still under active development.
How do you install this skill?
Install the collection with npx skills add microsoft/skills, then select the needed skill in the wizard. Alternatively, clone the repository and copy .github/plugins/azure-skills/skills/microsoft-foundry/models/deploy-model/preset/ into the selected agent’s skills directory. The README does not document a separate installation command for this individual skill.
How do you use this skill?
Install and configure Azure CLI, use an Azure subscription with Cognitive Services read/create permissions, and provide PROJECT_RESOURCE_ID or enter the project resource ID interactively. Trigger the skill with an intent such as “deploy this model quickly,” “find the best region,” or “check capacity across regions.” The workflow then guides model selection and, when necessary, region and project selection.
How does this skill compare with similar options?
Compared with the related customize skill, preset automatically selects a region and uses GlobalStandard for fast standard deployments; customize is intended for specified SKUs, versions, capacities, or PTU. For quota shortages, the source directs users to the related quota skill for quota requests and troubleshooting.