azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions with Bicep or Terraform.
What is azure-enterprise-infra-planner?
This skill helps cloud architects and platform engineers plan and deploy enterprise-scale Azure infrastructure including networking, identity, security, and compliance. Use it when designing landing zones, hub-spoke networks, multi-region topologies, or subscription-scope deployments with WAF alignment.
- Plan enterprise Azure infrastructure from workload or architecture descriptions
- Design networking: VNets, subnets, firewalls, private endpoints, VPN gateways
- Architect landing zones, hub-spoke networks, and multi-region disaster recovery topologies
- Generate production-ready Bicep or Terraform code with security validation
- Handle greenfield and brownfield (referenced) infrastructure scenarios with incremental deployment
- Validate generated IaC against security standards using checkov and local build tools
How to install azure-enterprise-infra-planner
npx skills add https://github.com/microsoft/azure-skills --skill azure-enterprise-infra-planner- Azure CLI installed and authenticated
- Bicep or Terraform installed locally
- Checkov installed for security validation
- Access to target Azure subscription(s)
How to use azure-enterprise-infra-planner
- 1.Describe your workload requirements or reference existing infrastructure (greenfield or brownfield scenario)
- 2.Follow the 7-phase gated pipeline: extract insights, research best practices, research resources, generate plan, approve plan, generate and validate IaC, deploy with confirmation
- 3.Review the generated infrastructure plan (.azure/infrastructure-plan.json) and approve before IaC generation
- 4.Validate generated Bicep or Terraform locally (az bicep build / terraform validate) and review checkov security scan results
- 5.Deploy using az deployment or terraform apply; for referenced (brownfield) scenarios, deployment is additive only
Use cases
- Architect a hub-spoke network topology with firewalls and private endpoints for a multi-workload enterprise
- Plan a multi-region disaster recovery infrastructure with failover and high-availability design
- Design an Azure landing zone with identity, RBAC, and compliance controls from scratch
- Generate Bicep modules for subscription-scope deployments of networking and security infrastructure
- Extend existing Azure infrastructure by inventorying current resources and adding new workloads incrementally
- Cloud architects planning enterprise Azure deployments
- Platform engineers designing landing zones and infrastructure-as-code
- DevOps teams managing multi-region or multi-resource-group topologies
- Infrastructure teams implementing disaster recovery and high-availability strategies
azure-enterprise-infra-planner FAQ
azure-enterprise-infra-planner is for infrastructure-centric, architecture-first planning (networking, identity, compliance, multi-region topologies). azure-prepare is for app-centric workflows. Use this skill for enterprise infrastructure; use azure-prepare for application deployment.
Yes. If you reference existing resources, resource groups, subscriptions, or IaC, the skill inventories them and generates additive deployments only—never modifying or destroying referenced resources.
Bicep or Terraform, depending on your preference. The skill generates subscription-scope or multi-resource-group deployments with modular structure.
Phase 6 is a hardened gate: generated IaC must pass az bicep build / terraform validate with zero errors and checkov security scan with no unresolved high/critical findings before deployment approval.
The skill stops, shows the validation errors, and prompts you to fix the generated code before re-validating and proceeding to deployment.
Full instructions (SKILL.md)
Source of truth, from microsoft/azure-skills.
name: azure-enterprise-infra-planner description: "Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows." license: MIT metadata: author: Microsoft version: "1.4.1"
Azure Enterprise Infra Planner
When to Use This Skill
Activate this skill when user wants to:
- Plan enterprise Azure infrastructure from a workload or architecture description
- Architect a landing zone, hub-spoke network, or multi-region topology
- Design networking infrastructure: VNets, subnets, firewalls, private endpoints, VPN gateways
- Plan identity, RBAC, and compliance-driven infrastructure
- Generate Bicep or Terraform for subscription-scope or multi-resource-group deployments
- Plan disaster recovery, failover, or cross-region high-availability topologies
Quick Reference
| Property | Details |
|---|---|
| MCP tools | insights_get, get_azure_bestpractices_get, wellarchitectedframework_serviceguide_get, microsoft_docs_fetch, microsoft_docs_search, bicepschema_get |
| CLI commands | az deployment group create, az bicep build, az resource list, terraform init, terraform plan, terraform validate, terraform apply, checkov |
| Output schema | schema.md |
| Key references | workflow.md, waf-checklist.md, resources/, constraints/ |
Workflow (Start Here)
Follow the step-by-step instructions in workflow.md to execute the 7 phases of infrastructure planning and provisioning.
Architecture
The skill runs a 7-phase, gated pipeline. Input is triaged into one of two flows:
- Greenfield — only new requirements; run the phases straight through.
- Referenced (brownfield) — the user supplies something that already exists (a live resource / resource group / subscription, IaC or an infra plan, or a requirements doc). The same phases run, plus referenced-workload.md: existing resources are inventoried and referenced (never recreated), the new workload is wired into them, and Phase 7 deploys additively (incremental only — never modifying or destroying the referenced resources).
Every phase advances only after its gate passes. Phase 5 requires explicit user approval; Phase 6 is a
hardened, self-verifying gate — the generated IaC must be secure-by-default, pass local validation
(az bicep build / terraform validate) with zero errors, pass a checkov security scan with no
unresolved high/critical findings, and the skill must show the command output and emit a completion
self-check before advancing; Phase 7 requires an explicit, risk-acknowledged deploy confirmation.
flowchart TD
IN([Input]) --> TRIAGE{Existing infra<br/>referenced?}
TRIAGE -- "No (greenfield)" --> P1
TRIAGE -- "Yes (referenced)" --> RW[/referenced-workload.md:<br/>inventory + assign roles<br/>reference, never recreate/]
RW --> P1
subgraph PIPE [7-phase gated pipeline]
direction TB
P1[Phase 1 · Extract insights] --> P2[Phase 2 · Research best practices]
P2 --> P3[Phase 3 · Research resources]
P3 --> P4[Phase 4 · Generate plan]
P4 --> P5{Phase 5 · Verify<br/>user approves?}
P5 -- "no" --> P4
P5 -- "approved" --> P6[Phase 6 · Generate IaC]
P6 --> VAL{Validate<br/>az bicep build /<br/>terraform validate}
VAL -- "errors" --> P6
VAL -- "clean" --> P7{Phase 7 · Deploy<br/>risk-ack confirm?}
end
P7 -- "greenfield" --> DEP[az deployment / terraform apply]
P7 -- "referenced" --> DEPADD[Additive deploy · incremental only<br/>what-if preview · no destroy of<br/>referenced resources]
DEP --> OUT([Deployed])
DEPADD --> OUT
classDef gate fill:#fff3cd,stroke:#d39e00,color:#000;
classDef ref fill:#e2f0d9,stroke:#548235,color:#000;
class P5,VAL,P7,TRIAGE gate;
class RW,DEPADD ref;
Artifacts (written under <project-root>/): .azure/insights.json (Phase 1),
.azure/infrastructure-plan.json (Phase 4, status draft→approved→deployed), and
infra/main.bicep + infra/modules/* or infra/main.tf + infra/modules/** (Phase 6).
MCP Tools
| Tool | Purpose |
|---|---|
insights_get | Retrieve insights about the user's existing Azure environment to guide planning decisions |
get_azure_bestpractices_get | Azure best practices for code generation, operations, and deployment |
wellarchitectedframework_serviceguide_get | WAF service guide for a specific Azure service |
microsoft_docs_search | Search Microsoft Learn for relevant documentation chunks |
microsoft_docs_fetch | Fetch full content of a Microsoft Learn page by URL |
bicepschema_get | Bicep schema definition for any Azure resource type (latest API version) |
Error Handling
| Error | Cause | Fix |
|---|---|---|
| MCP tool error or not available | Tool call timeout, connection error, or tool doesn't exist | Retry once; fall back to reference files and notify user if unresolved |
| Plan approval missing | meta.status is not approved | Stop and prompt user for approval before IaC generation or deployment |
| IaC validation failure | az bicep build or terraform validate returns errors | Fix the generated code and re-validate; notify user if unresolved |
| Pairing constraint violation | Incompatible SKU or resource combination | Fix in plan before proceeding to IaC generation |
| Infra plan or IaC files not found | Files written to wrong location or not created | Verify files exist at <project-root>/.azure/ and <project-root>/infra/; if missing, re-create the files by following workflow.md exactly |
Related skills
More from microsoft/azure-skills and the wider catalog.
