azure-architecture-autopilot

Design Azure infrastructure, generate architecture diagrams, and deploy with Bicep templates.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/lettucebo/Skills --skill azure-architecture-autopilot-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-architecture-autopilot
Source: https://github.com/lettucebo/Skills/tree/main/skills/azure/azure-architecture-autopilot
Command: npx skills add https://github.com/lettucebo/Skills --skill azure-architecture-autopilot-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Designing Azure infrastructure requires deep knowledge of service configurations, networking patterns, and Bicep syntax, and mistakes like missing private endpoint DNS zones or incorrect API versions cause deployment failures. This Skill guides the entire lifecycle from natural-language architecture design through diagram generation, Bicep code review, and validated deployment. ## Core Features & Use Cases - Interactive Architecture Design: Conversationally gather requirements, verify SKUs and model availability against live MS Docs, and produce interactive HTML diagrams with 605+ official Azure icons using the embedded Python diagram engine. - Bicep Generation and Review: Generate modular Bicep templates (network, AI, storage, Key Vault, private endpoints) with enforced patterns like RBAC role assignments, managed identities, and network isolation, then compile and auto-fix issues. - Existing Resource Analysis: Scan an existing resource group, infer relationships, visualize the current architecture, and apply natural-language modifications before redeploying. - Use Case: Ask to set up a RAG chatbot on Azure; the Skill confirms the region and models, draws the Foundry + AI Search + ADLS Gen2 architecture diagram, generates reviewed Bicep code, and deploys after what-if validation. ## Quick Start Ask the agent to design and deploy a RAG architecture on Azure with private networking in your chosen region.

Frequently Asked Questions about azure-architecture-autopilot

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

FAQPage Schema
How do I generate Azure architecture diagrams from existing resources?▼

Point the Skill at a resource group and it scans existing resources, infers relationships, and renders an interactive HTML diagram using its embedded Python engine with official Azure icons. No pip install or network access is needed for diagram generation.

How do I deploy Azure infrastructure with Bicep from a natural language description?▼

Describe the workload, such as a RAG chatbot, and the Skill confirms region, SKUs, and models through questions, generates modular Bicep files, compiles them with az bicep build, and deploys only after what-if validation and your approval.

Does the Bicep generation verify API versions and model availability?▼

Yes. Before generating code it fetches the MS Docs Bicep reference for each service to confirm the latest stable API version, and checks model availability per region via MS Docs or az cognitiveservices account list-models. Hardcoded versions are explicitly prohibited.

What Azure services are supported for private endpoint configuration?▼

Optimized coverage includes Microsoft Foundry, AI Search, ADLS Gen2, Key Vault, Fabric, Data Factory, and VNet/private endpoints, each with the full PE plus DNS zone plus VNet link pattern. Other Azure services are supported by fetching MS Docs at generation time.

Why does my Foundry deployment fail without a Foundry Project resource?▼

The Foundry Project (Microsoft.CognitiveServices/accounts/projects) must be created as a child resource of the AIServices account, or the resource is not accessible in the portal. The Skill enforces this pairing along with customSubDomainName and managed identity requirements.

What are the limitations of the automated Bicep review?▼

az bicep build validates only syntax and types; it cannot catch retired SKUs, per-region availability, invalid model names, or quota issues. These are finally verified by the az deployment group what-if step before any actual deployment occurs.