[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699T1H2DTYFYN6GWWHP8F3H":3,"skill-same:01M699T1H2DTYFYN6GWWHP8F3H":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M699T1H2DTYFYN6GWWHP8F3H","azure-resource-visualizer",null,"Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.","microsoft\u002Fazure-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699HXPKQFT1BH5KD1PG0CB4",1636,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,9],"azure resource visualizer","azure","generate","when","my","resources","map","show","mermaid diagram","diagrams","analyze","topology","visualization","visualize","create","architecture diagram","infrastructure","mermaid","diagram","architecture","2026-11-10 10:12:30",false,"---\nname: azure-resource-visualizer\ndescription: \"Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.2.3\"\n---\n\n# Azure Resource Visualizer - Architecture Diagram Generator\n\nA user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.\n\n## Core Responsibilities\n\n1. **Resource Group Discovery**: List available resource groups when not specified\n2. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies\n3. **Relationship Mapping**: Identify and document all connections between resources\n4. **Diagram Generation**: Create detailed, accurate Mermaid diagrams\n5. **Documentation Creation**: Produce clear markdown files with embedded diagrams\n\n## Workflow Process\n\n### Step 1: Resource Group Selection\n\nIf the user hasn't specified a resource group:\n\n1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.\n2. Present a numbered list of resource groups with their locations\n3. Ask the user to select one by number or name\n4. Wait for user response before proceeding\n\nIf a resource group is specified, validate it exists and proceed.\n\n### Step 2: Resource Discovery & Analysis\n\nFor bulk resource discovery across subscriptions, use Azure Resource Graph queries. See [Azure Resource Graph Queries](references\u002Fazure-resource-graph.md) for cross-subscription inventory and relationship discovery patterns.\n\nOnce you have the resource group:\n\n1. **Query all resources** in the resource group using Azure MCP tools or `az`.\n2. **Analyze each resource** type and capture:\n   - Resource name and type\n   - SKU\u002Ftier information\n   - Location\u002Fregion\n   - Key configuration properties\n   - Network settings (VNets, subnets, private endpoints)\n   - Identity and access (Managed Identity, RBAC)\n   - Dependencies and connections\n\n3. **Map relationships** by identifying:\n   - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints\n   - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends\n   - **Identity**: Managed identities connecting to resources\n   - **Configuration**: App Settings pointing to Key Vaults, connection strings\n   - **Dependencies**: Parent-child relationships, required resources\n\n> **Important**: You must only use placeholder names to represent secret values, such as keys, connection strings, Key Vault secrets, etc. Use meaningful placeholder names to represent each secret in the diagram. Never put secret values in the resource diagram.\n\n### Step 3: Diagram Construction\n\nCreate a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format.\n\nSee [example-diagram.md](.\u002Fassets\u002Fexample-diagram.md) for a complete sample architecture diagram.\n\n**Key Diagram Requirements:**\n\n- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring\n- **Include details**: SKUs, tiers, important settings in node labels (use `\u003Cbr\u002F>` for line breaks)\n- **Label all connections**: Describe what flows between resources (data, identity, network)\n- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)\n- **Visual hierarchy**: Subgraphs for logical grouping\n- **Connection types**:\n  - `-->` for data flow or dependencies\n  - `-.->` for optional\u002Fconditional connections\n  - `==>` for critical\u002Fprimary paths\n\n**Resource Type Examples:**\n- App Service: Include plan tier (B1, S1, P1v2)\n- Functions: Include runtime (.NET, Python, Node)\n- Databases: Include tier (Basic, Standard, Premium)\n- Storage: Include redundancy (LRS, GRS, ZRS)\n- VNets: Include address space\n- Subnets: Include address range\n\n### Step 4: File Creation\n\nUse [template-architecture.md](.\u002Fassets\u002Ftemplate-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:\n\n1. **Header**: Resource group name, subscription, region\n2. **Summary**: Brief overview of the architecture (2-3 paragraphs)\n3. **Resource Inventory**: Table listing all resources with types and key properties\n4. **Architecture Diagram**: The complete Mermaid diagram\n5. **Relationship Details**: Explanation of key connections and data flows\n6. **Notes**: Any important observations, potential issues, or recommendations\n\n## Operating Guidelines\n\n### Quality Standards\n\n- **Accuracy**: Verify all resource details before including in diagram\n- **Completeness**: Don't omit resources; include everything in the resource group\n- **Clarity**: Use clear, descriptive labels and logical grouping\n- **Detail Level**: Include configuration details that matter for architecture understanding\n- **Relationships**: Show ALL significant connections, not just obvious ones\n\n### Tool Usage Patterns\n\n1. **Azure MCP Search**: \n   - Use `intent=\"list resource groups\"` to discover resource groups\n   - Use `intent=\"list resources in group\"` with group name to get all resources\n   - Use `intent=\"get resource details\"` for individual resource analysis\n   - Use `command` parameter when you need specific Azure operations\n\n2. **File Creation**:\n   - Always create in workspace root or a `docs\u002F` folder if it exists\n   - Use clear, descriptive filenames: `[rg-name]-architecture.md`\n   - Ensure Mermaid syntax is valid (test syntax mentally before output)\n\n3. **Terminal (when needed)**:\n   - Use Azure CLI for complex queries not available via MCP\n   - Example: `az resource list --resource-group \u003Cname> --output json`\n   - Example: `az network vnet show --resource-group \u003Cname> --name \u003Cvnet-name>`\n\n### Constraints & Boundaries\n\n**Always Do:**\n- ✅ List resource groups if not specified\n- ✅ Wait for user selection before proceeding\n- ✅ Analyze ALL resources in the group\n- ✅ Create detailed, accurate diagrams\n- ✅ Include configuration details in node labels\n- ✅ Group resources logically with subgraphs\n- ✅ Label all connections descriptively\n- ✅ Create a complete markdown file with diagram\n\n**Never Do:**\n- ❌ Skip resources because they seem unimportant\n- ❌ Make assumptions about resource relationships without verification\n- ❌ Create incomplete or placeholder diagrams\n- ❌ Omit configuration details that affect architecture\n- ❌ Proceed without confirming resource group selection\n- ❌ Generate invalid Mermaid syntax\n- ❌ Modify or delete Azure resources (read-only analysis)\n\n### Edge Cases & Error Handling\n\n- **No resources found**: Inform user and verify resource group name\n- **Permission issues**: Explain what's missing and suggest checking RBAC\n- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer\n- **Cross-resource-group dependencies**: Note external dependencies in diagram notes\n- **Resources without clear relationships**: Group in \"Other Resources\" section\n\n## Output Format Specifications\n\n### Mermaid Diagram Syntax\n- Use `graph TB` (top-to-bottom) for vertical layouts\n- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)\n- Subgraph syntax: `subgraph \"Descriptive Name\"`\n- Node syntax: `ID[\"Display Name\u003Cbr\u002F>Details\"]`\n- Connection syntax: `SOURCE -->|\"Label\"| TARGET`\n\n### Markdown Structure\n- Use H1 for main title\n- Use H2 for major sections\n- Use H3 for subsections\n- Use tables for resource inventories\n- Use bullet lists for notes and recommendations\n- Use code blocks with `mermaid` language tag for diagrams\n\n## Success Criteria\n\nA successful analysis includes:\n- ✅ Valid resource group identified\n- ✅ All resources discovered and analyzed\n- ✅ All significant relationships mapped\n- ✅ Detailed Mermaid diagram with proper grouping\n- ✅ Complete markdown file created\n- ✅ Clear, actionable documentation\n- ✅ Valid Mermaid syntax that renders correctly\n- ✅ Professional, architect-level output\n\nYour goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.\n","# Azure Resource Visualizer - Architecture Diagram Generator\n\nA user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.\n\n## Core Responsibilities\n\n1. **Resource Group Discovery**: List available resource groups when not specified\n2. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies\n3. **Relationship Mapping**: Identify and document all connections between resources\n4. **Diagram Generation**: Create detailed, accurate Mermaid diagrams\n5. **Documentation Creation**: Produce clear markdown files with embedded diagrams\n\n## Workflow Process\n\n### Step 1: Resource Group Selection\n\nIf the user hasn't specified a resource group:\n\n1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.\n2. Present a numbered list of resource groups with their locations\n3. Ask the user to select one by number or name\n4. Wait for user response before proceeding\n\nIf a resource group is specified, validate it exists and proceed.\n\n### Step 2: Resource Discovery & Analysis\n\nFor bulk resource discovery across subscriptions, use Azure Resource Graph queries. See [Azure Resource Graph Queries](references\u002Fazure-resource-graph.md) for cross-subscription inventory and relationship discovery patterns.\n\nOnce you have the resource group:\n\n1. **Query all resources** in the resource group using Azure MCP tools or `az`.\n2. **Analyze each resource** type and capture:\n   - Resource name and type\n   - SKU\u002Ftier information\n   - Location\u002Fregion\n   - Key configuration properties\n   - Network settings (VNets, subnets, private endpoints)\n   - Identity and access (Managed Identity, RBAC)\n   - Dependencies and connections\n\n3. **Map relationships** by identifying:\n   - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints\n   - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends\n   - **Identity**: Managed identities connecting to resources\n   - **Configuration**: App Settings pointing to Key Vaults, connection strings\n   - **Dependencies**: Parent-child relationships, required resources\n\n> **Important**: You must only use placeholder names to represent secret values, such as keys, connection strings, Key Vault secrets, etc. Use meaningful placeholder names to represent each secret in the diagram. Never put secret values in the resource diagram.\n\n### Step 3: Diagram Construction\n\nCreate a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format.\n\nSee [example-diagram.md](.\u002Fassets\u002Fexample-diagram.md) for a complete sample architecture diagram.\n\n**Key Diagram Requirements:**\n\n- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring\n- **Include details**: SKUs, tiers, important settings in node labels (use `\u003Cbr\u002F>` for line breaks)\n- **Label all connections**: Describe what flows between resources (data, identity, network)\n- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)\n- **Visual hierarchy**: Subgraphs for logical grouping\n- **Connection types**:\n  - `-->` for data flow or dependencies\n  - `-.->` for optional\u002Fconditional connections\n  - `==>` for critical\u002Fprimary paths\n\n**Resource Type Examples:**\n- App Service: Include plan tier (B1, S1, P1v2)\n- Functions: Include runtime (.NET, Python, Node)\n- Databases: Include tier (Basic, Standard, Premium)\n- Storage: Include redundancy (LRS, GRS, ZRS)\n- VNets: Include address space\n- Subnets: Include address range\n\n### Step 4: File Creation\n\nUse [template-architecture.md](.\u002Fassets\u002Ftemplate-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:\n\n1. **Header**: Resource group name, subscription, region\n2. **Summary**: Brief overview of the architecture (2-3 paragraphs)\n3. **Resource Inventory**: Table listing all resources with types and key properties\n4. **Architecture Diagram**: The complete Mermaid diagram\n5. **Relationship Details**: Explanation of key connections and data flows\n6. **Notes**: Any important observations, potential issues, or recommendations\n\n## Operating Guidelines\n\n### Quality Standards\n\n- **Accuracy**: Verify all resource details before including in diagram\n- **Completeness**: Don't omit resources; include everything in the resource group\n- **Clarity**: Use clear, descriptive labels and logical grouping\n- **Detail Level**: Include configuration details that matter for architecture understanding\n- **Relationships**: Show ALL significant connections, not just obvious ones\n\n### Tool Usage Patterns\n\n1. **Azure MCP Search**: \n   - Use `intent=\"list resource groups\"` to discover resource groups\n   - Use `intent=\"list resources in group\"` with group name to get all resources\n   - Use `intent=\"get resource details\"` for individual resource analysis\n   - Use `command` parameter when you need specific Azure operations\n\n2. **File Creation**:\n   - Always create in workspace root or a `docs\u002F` folder if it exists\n   - Use clear, descriptive filenames: `[rg-name]-architecture.md`\n   - Ensure Mermaid syntax is valid (test syntax mentally before output)\n\n3. **Terminal (when needed)**:\n   - Use Azure CLI for complex queries not available via MCP\n   - Example: `az resource list --resource-group \u003Cname> --output json`\n   - Example: `az network vnet show --resource-group \u003Cname> --name \u003Cvnet-name>`\n\n### Constraints & Boundaries\n\n**Always Do:**\n- ✅ List resource groups if not specified\n- ✅ Wait for user selection before proceeding\n- ✅ Analyze ALL resources in the group\n- ✅ Create detailed, accurate diagrams\n- ✅ Include configuration details in node labels\n- ✅ Group resources logically with subgraphs\n- ✅ Label all connections descriptively\n- ✅ Create a complete markdown file with diagram\n\n**Never Do:**\n- ❌ Skip resources because they seem unimportant\n- ❌ Make assumptions about resource relationships without verification\n- ❌ Create incomplete or placeholder diagrams\n- ❌ Omit configuration details that affect architecture\n- ❌ Proceed without confirming resource group selection\n- ❌ Generate invalid Mermaid syntax\n- ❌ Modify or delete Azure resources (read-only analysis)\n\n### Edge Cases & Error Handling\n\n- **No resources found**: Inform user and verify resource group name\n- **Permission issues**: Explain what's missing and suggest checking RBAC\n- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer\n- **Cross-resource-group dependencies**: Note external dependencies in diagram notes\n- **Resources without clear relationships**: Group in \"Other Resources\" section\n\n## Output Format Specifications\n\n### Mermaid Diagram Syntax\n- Use `graph TB` (top-to-bottom) for vertical layouts\n- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)\n- Subgraph syntax: `subgraph \"Descriptive Name\"`\n- Node syntax: `ID[\"Display Name\u003Cbr\u002F>Details\"]`\n- Connection syntax: `SOURCE -->|\"Label\"| TARGET`\n\n### Markdown Structure\n- Use H1 for main title\n- Use H2 for major sections\n- Use H3 for subsections\n- Use tables for resource inventories\n- Use bullet lists for notes and recommendations\n- Use code blocks with `mermaid` language tag for diagrams\n\n## Success Criteria\n\nA successful analysis includes:\n- ✅ Valid resource group identified\n- ✅ All resources discovered and analyzed\n- ✅ All significant relationships mapped\n- ✅ Detailed Mermaid diagram with proper grouping\n- ✅ Complete markdown file created\n- ✅ Clear, actionable documentation\n- ✅ Valid Mermaid syntax that renders correctly\n- ✅ Professional, architect-level output\n\nYour goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":12,"version":45},"1.2.3","main","fbda857c484a85c7ce644f56809b7f204471fb69","skills\u002Fazure-resource-visualizer",266,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 02:03:16",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Fazure-skills --skill azure-resource-visualizer",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Fazure-skills --skill azure-resource-visualizer",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Fazure-skills --skill azure-resource-visualizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002FSKILL.md",true,[69,75,79],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Fexample-diagram.md","ASSET","资产文件",1778,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002Fassets\u002Fexample-diagram.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ftemplate-architecture.md",970,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002Fassets\u002Ftemplate-architecture.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fazure-resource-graph.md","REFERENCE","参考文档",2390,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002Freferences\u002Fazure-resource-graph.md",[86,116,143,165,182,198],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":39},"01M699VFT1T15GFDGC4K4ZHY4N","python-appservice-deploy","Deploy Python (Flask\u002FDjango\u002FFastAPI) code to Azure App Service Linux. WHEN: \"Flask App Service\", \"Django App Service\", \"FastAPI App Service\", \"deploy Python to App Service\". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform\u002FBicep\u002FIaC, full infra — use azure-prepare.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpython-appservice-deploy\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[98,99,100,101,102,103,104,105,106,107,20,108,109,110,111,112,22,113,114,115],"python appservice deploy","deploy","python","linux","infra","app","do","django","for","azure app service","container","iac","fastapi","use","apps","code","functions","fastapi app",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":39},"01M699VDV3PT5P0YDXRT4GM2TJ","preset","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).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002Fpreset\u002FSKILL.md",[122,123],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",[118,99,127,9,128,129,104,130,131,106,132,133,134,20,135,136,137,111,138,139,140,141,142],"setup","capacity","customize","quick","availability","deployment","alternatives","selection","custom","deployments","high availability","version","across","check","multi","first",{"skillNo":144,"name":129,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":39},"01M699VBT6YFAKBWCK890XDB6N","Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard\u002FStandard\u002FProvisionedManaged), 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).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002Fcustomize\u002FSKILL.md",[148],{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},[129,118,9,128,150,151,130,152,153,154,155,156,134,157,158,159,160,161,162,163,164,104,106,132],"policy","SET","processing","advanced","model","select","choose","configure","filter","azure openai","options","flow","openai","throughput","full",{"skillNo":166,"name":128,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":39},"01M699V9FXHBSWG3Y48057VAYZ","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002Fcapacity\u002FSKILL.md",[],[128,118,99,9,129,171,154,172,173,174,175,176,139,159,177,178,162,179,180,104,131,106,181,132],"projects","project","search","analysis","listing","hand","limits","azure portal","direct","TPM","discovery",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":190,"publishedAt":39},"01M699V7GW2RF4AB3RE3Z8Y048","deploy-model","Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version\u002FSKU\u002Fcapacity\u002FRAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent\u002Fcreate), project creation (use project\u002Fcreate).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002FSKILL.md",[188,189],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},[99,191,154,118,192,193,9,128,150,151,171,130,194,172,195,174,175,139,33,159,196,197,162,104,131],"deploy model","MCP","foundry","creation","up","intent","list",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":39},"01M699V3NA4YQKCHJTVWHBQH10","finetuning","Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmicrosoft-foundry\u002Ffinetuning\u002FSKILL.md",[204],{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},[200,206,99,193,207,9,208,194,154,209,210,211,212,213,214,215,216,217,104,106,218,219,132,220],"placeholder","microsoft foundry","Prompt Optimization","training","dataset","optimizer","Evaluation","tuning","grader","data","supervised","distillation","Optimization","calibrate","submission"]