
Azure Architecture Autopilot
Describe or analyze Azure workloads in natural language, get interactive architecture diagrams, iterate on design, and generate Bicep for deployment.
Overview
Azure Architecture Autopilot is an agent skill most often used in Validate (also Build, Operate) that designs or analyzes Azure infrastructure from natural language, renders official-icon diagrams, and supports Bicep-ori
Install
npx skills add https://github.com/github/awesome-copilot --skill azure-architecture-autopilotWhat is this skill?
- Natural-language paths for net-new designs and for analyzing existing resource groups
- Embedded diagram engine under `scripts/` with 605+ official Azure icons—no `pip install`
- Interactive HTML architecture diagrams generated locally from bundled Python scripts
- Bicep / IaC generation and deployment flow after conversational refinement
- Coverage across Foundry, AI Search, OpenAI, Fabric, ADLS Gen2, Databricks, and broader Azure services
- Embedded diagram engine uses bundled Python scripts with 605+ official Azure icons
- No pip install required for the diagram engine per skill documentation
Adoption & trust: 1.2k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know the Azure services you need—or already have a messy resource group—but lack a fast loop from intent to diagram to editable IaC.
Who is it for?
Indie builders and small teams planning or refactoring Azure systems (especially AI/RAG and data platforms) who want diagram plus IaC in one guided flow.
Skip if: Purely on-prem or AWS/GCP-only estates, or teams that forbid generated IaC without a separate enterprise architecture review gate.
When should I use this skill?
Use for “Create X on Azure,” RAG setup, analyzing current Azure infrastructure, drawing diagrams for resource groups, natural-language modifications (performance, cost, security), and Bicep or broader IaC generation acro
What do I get? / Deliverables
You get an interactive architecture diagram and a refinement path toward Bicep deployment after aligning design in conversation.
- Interactive HTML Azure architecture diagram
- Conversationally refined architecture narrative
- Bicep-oriented IaC output for deployment
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate/scope is the canonical shelf because the pipeline starts with architecture design or as-is analysis before implementation and deploy commits. Scope captures greenfield designs (“RAG on Azure”), resource-group reviews, and cost/security refinement conversations.
Where it fits
Sketch a Foundry + AI Search RAG layout from a one-line product idea before writing application code.
Turn an agreed diagram into Bicep modules for APIs, storage, and model endpoints.
Finalize launch-ready infra documentation from the interactive HTML diagram for stakeholders.
Re-analyze an existing resource group after a latency or cost incident and propose architectural diffs.
How it compares
Use instead of disconnected draw.io sessions plus hand-written Bicep when you want NL-driven design, analysis, and template generation in one skill package—not an MCP telemetry bridge.
Common Questions / FAQ
Who is azure-architecture-autopilot for?
Solo builders and small teams on Microsoft Azure who design new workloads, document existing resource groups, or tune cost, performance, and security with agent assistance.
When should I use azure-architecture-autopilot?
Use in Validate when scoping RAG or data platforms; in Build when translating architecture to Bicep/backend layout; in Operate when analyzing live infra (“draw rg-xxx”, cost or security hardening)—especially for Foundry, AI Search, OpenAI, Fabric, ADLS, and Databricks scenarios.
Is azure-architecture-autopilot safe to install?
Review the Security Audits panel on this Prism page before use; generated Bicep and deploy steps can modify real subscriptions, so restrict agent permissions and require human approval for production applies.
SKILL.md
READMESKILL.md - Azure Architecture Autopilot
# Azure Architecture Builder A pipeline that designs Azure infrastructure using natural language, or analyzes existing resources to visualize architecture and proceed through modification and deployment. The diagram engine is **embedded within the skill** (`scripts/` folder). No `pip install` needed — it directly uses the bundled Python scripts to generate interactive HTML diagrams with 605+ official Azure icons. Ready to use immediately without network access or package installation. ## Automatic User Language Detection **🚨 Detect the language of the user's first message and provide all subsequent responses in that language. This is the highest-priority principle.** - If the user writes in Korean → respond in Korean - If the user writes in English → **respond in English** (ask_user, progress updates, reports, Bicep comments — all in English) - The instructions and examples in this document are written in English, and **all user-facing output must match the user's language** **⚠️ Do not copy examples from this document verbatim to the user.** Use only the structure as reference, and adapt text to the user's language. ## Tool Usage Guide (GHCP Environment) | Feature | Tool Name | Notes | |---------|-----------|-------| | Fetch URL content | `web_fetch` | For MS Docs lookups, etc. | | Web search | `web_search` | URL discovery | | Ask user | `ask_user` | `choices` must be a string array | | Sub-agents | `task` | explore/task/general-purpose | | Shell command execution | `powershell` | Windows PowerShell | > All sub-agents (explore/task/general-purpose) cannot use `web_fetch` or `web_search`. > Fact-checking that requires MS Docs lookups must be performed **directly by the main agent**. ## External Tool Path Discovery `az`, `python`, `bicep`, etc. are often not on PATH. **Discover once before starting a Phase and cache the result. Do not re-discover every time.** > **⚠️ Do not use `Get-Command python`** — risk of Windows Store alias. > Direct filesystem discovery (`$env:LOCALAPPDATA\Programs\Python`) takes priority. az CLI path: ```powershell $azCmd = $null if (Get-Command az -ErrorAction SilentlyContinue) { $azCmd = 'az' } if (-not $azCmd) { $azExe = Get-ChildItem -Path "$env:ProgramFiles\Microsoft SDKs\Azure\CLI2\wbin", "$env:LOCALAPPDATA\Programs\Azure CLI\wbin" -Filter "az.cmd" -ErrorAction SilentlyContinue | Select-Object -First 1 -ExpandProperty FullName if ($azExe) { $azCmd = $azExe } } ``` Python path + embedded diagram engine: refer to the diagram generation section in `references/phase1-advisor.md`. ## Progress Updates Required Use blockquote + emoji + bold format: ```markdown > **⏳ [Action]** — [Reason] > **✅ [Complete]** — [Result] > **⚠️ [Warning]** — [Details] > **❌ [Failed]** — [Cause] ``` ## Parallel Preload Principle While waiting for user input via `ask_user`, preload information needed for the next step in parallel. | ask_user Question | Preload Simultaneously | |---|---| | Project name / scan scope | Reference files, MS Docs, Python path discovery, **diagram module path verification** | | Model/SKU selection | MS Docs for next question choices | | Architecture confirmation | `az account show/list`, `az group list` | | Subscription selection | `az group list` | --- ## Path Branching — Au