deploy-model

Route Azure OpenAI model deployment requests to preset, customization, or capacity-discovery workflows.

Updated May 25, 2026
One-click install
npx skills add https://github.com/AcendWay/ai-skills-library --skill deploy-model-acendway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-model
Source: https://github.com/AcendWay/ai-skills-library/tree/main/skill-folders/microsoft-foundry/models/deploy-model
Command: npx skills add https://github.com/AcendWay/ai-skills-library --skill deploy-model-acendway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of deploying Azure OpenAI models by automatically selecting the right deployment mode (preset, customization, or capacity discovery) and guiding safe, quota-aware deployment decisions across regions and projects.

Core Features & Use Cases

  • Intent-based routing (preset, customize, capacity discovery): Interprets what you mean in plain language and routes to the correct workflow for quick deployment, full configuration, or finding available capacity.
  • Capacity-aware, quota-validated options: Checks model support for the selected SKU and validates subscription quota before presenting deployable choices.
  • Safe project selection guardrail: Requires confirming the target project/region/resource group before deploying to prevent accidental mis-deployments.
  • Use case examples: Deploy a model quickly to an optimal region, create a PTU/RAI-controlled deployment when you need precise controls, or answer “where can I deploy this model with X capacity” before you deploy.

Quick Start

Ask the AI: "Deploy gpt-4o to the best region for me."

Frequently Asked Questions about deploy-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Azure OpenAI models to the best available region?

To deploy Azure OpenAI models optimally, this Skill routes your request to a capacity-discovery workflow that checks model support and subscription quota across regions, validating availability before guiding safe deployment. It requires Azure CLI authentication to perform ARM and REST capacity checks.

What is the best way to find Azure OpenAI quota and capacity before deploying a model?

Finding Azure OpenAI quota and capacity involves read-only discovery workflows that check subscription usage and model availability across regions and projects. This Skill validates regional capacity through ARM and REST API checks before presenting deployable SKU choices.

Do I need Azure CLI authentication to check Azure OpenAI deployment capacity?

Yes, Azure CLI authentication is required to validate Azure OpenAI deployment capacity. This Skill uses authenticated ARM and REST API calls to check subscription quotas, verify model SKU support, and ensure safe project and region confirmation before routing to actual deployment.

Can I customize version, SKU, and RAI policies when deploying Azure OpenAI models?

Yes, you can customize version, SKU, capacity, and RAI policies when deploying Azure OpenAI models. This Skill routes interactive requests to a customization workflow that allows precise configuration controls for PTU deployments while validating quota and safe project selection beforehand.

How does intent routing work for Azure OpenAI model deployment requests?

Intent routing for Azure OpenAI deployment interprets plain language requests and directs them to preset, customization, or capacity-discovery workflows based on your constraints. It enables quick deployments, full configuration control, or read-only availability checks before committing to a specific region.

Why does my Azure OpenAI model deployment require project and region confirmation?

Azure OpenAI model deployment requires project and region confirmation as a safe selection guardrail to prevent accidental mis-deployments. This Skill enforces target project, resource group, and region validation before handing off to preset or customize workflows for actual deployment execution.