azure-iac-bicep

name

azure-iac-bicep

description

Author, refactor, validate, and deploy Azure infrastructure as code in Bicep (preferred) and ARM JSON. Use when creating or editing .bicep / .bicepparam files, designing modules, decompiling or migrating ARM templates to Bicep, wiring what-if and deployment-stack workflows, hardening IaC for security (managed identity, private endpoints, no secrets in templates), or generating GitHub Actions pipelines that deploy Bicep. Triggers on "write a Bicep module", "convert this ARM template", "deploy this to a resource group", "what-if", "bicepparam", "az deployment", or any Azure infrastructure-as-code authoring request.

Azure IaC: Bicep + ARM

Production-grade Azure infrastructure as code. Bicep is the default authoring language; ARM JSON is the compile target and the fallback for tooling that has not adopted Bicep. Decompile legacy ARM to Bicep, never hand-author new ARM JSON.

When to load reference files

This file is the index. Load the deeper material only when the task needs it:

You are...	Read
Authoring a module, picking a scope, choosing decorators, wiring outputs	references/module-patterns.md
Migrating ARM JSON to Bicep, or deciding Bicep vs ARM vs Terraform	references/arm-vs-bicep.md
Running lint / what-if / deploy / deployment stacks, or building a CI pipeline	references/deploy-runbook.md

Documentation-first mandate

Resource API shapes drift. Before emitting any resource declaration, confirm the type, apiVersion, and required properties against the live schema rather than memory:

• Call the mcp__azure__bicepschema tool for the exact resource type (for example Microsoft.Storage/storageAccounts) to get current apiVersion and property names.