Azure Enterprise Infra Planner: Install, Source and Security | FunnelSlayer

Azure Enterprise Infra Planner

Published by microsoft in azure-skills

Review recommended417k installsAutomation & Infrastructure

What this skill does

Plans Azure infrastructure from workload requirements, checks it against Microsoft guidance, and creates Bicep or Terraform files. It can validate and deploy the plan after approval, with safeguards for existing environments. Best for Cloud architects and platform engineers planning or deploying enterprise Azure environments.

Add Azure Enterprise Infra Planner to your agent

Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.

Install with a prompt

Paste this into a compatible coding agent:

add this skill "azure-enterprise-infra-planner" from https://github.com/microsoft/azure-skills

Install with the CLI

Run this command in a controlled environment after reviewing the repository:

npx skills add https://github.com/microsoft/azure-skills --skill azure-enterprise-infra-planner

Skill instructions

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

PropertyDetails
MCP toolsinsights_get, get_azure_bestpractices_get, wellarchitectedframework_serviceguide_get, microsoft_docs_fetch, microsoft_docs_search, bicepschema_get
CLI commandsaz deployment group create, az bicep build, az resource list, terraform init, terraform plan, terraform validate, terraform apply, checkov
Output schemaschema.md
Key referencesworkflow.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

ToolPurpose
insights_getRetrieve insights about the user's existing Azure environment to guide planning decisions
get_azure_bestpractices_getAzure best practices for code generation, operations, and deployment
wellarchitectedframework_serviceguide_getWAF service guide for a specific Azure service
microsoft_docs_searchSearch Microsoft Learn for relevant documentation chunks
microsoft_docs_fetchFetch full content of a Microsoft Learn page by URL
bicepschema_getBicep schema definition for any Azure resource type (latest API version)

Error Handling

ErrorCauseFix
MCP tool error or not availableTool call timeout, connection error, or tool doesn't existRetry once; fall back to reference files and notify user if unresolved
Plan approval missingmeta.status is not approvedStop and prompt user for approval before IaC generation or deployment
IaC validation failureaz bicep build or terraform validate returns errorsFix the generated code and re-validate; notify user if unresolved
Pairing constraint violationIncompatible SKU or resource combinationFix in plan before proceeding to IaC generation
Infra plan or IaC files not foundFiles written to wrong location or not createdVerify files exist at <project-root>/.azure/ and <project-root>/infra/; if missing, re-create the files by following workflow.md exactly

Files included

  • references/bicep-generation.md
  • references/constraints/ai-ml.md
  • references/constraints/compute-apps.md
  • references/constraints/compute-infra.md
  • references/constraints/data-analytics.md
  • references/constraints/data-relational.md
  • references/constraints/messaging.md
  • references/constraints/monitoring.md
  • references/constraints/networking-connectivity.md
  • references/constraints/networking-core.md
  • references/constraints/networking-traffic.md
  • references/constraints/README.md
  • references/constraints/security.md
  • references/deployment.md
  • references/pairing-checks.md
  • references/phases/1-extract-insights.md
  • references/phases/2-research-best-practices.md
  • references/phases/3-research-resources.md
  • references/phases/4-generate-plan.md
  • references/phases/5-verify.md
  • references/phases/6-generate-iac.md
  • references/phases/7-deploy.md
  • references/referenced-workload.md
  • references/resources/ai-ml.md
  • references/resources/compute-apps.md
  • references/resources/compute-infra.md
  • references/resources/data-analytics.md
  • references/resources/data-relational.md
  • references/resources/messaging.md
  • references/resources/monitoring.md
  • references/resources/networking-connectivity.md
  • references/resources/networking-core.md
  • references/resources/networking-traffic.md
  • references/resources/README.md
  • references/resources/security.md
  • references/schema.md
  • references/terraform-generation.md
  • references/verification.md
  • references/waf-checklist.md
  • references/workflow.md
  • SKILL.md

More skills for Automation & Infrastructure