Domain-specific language for declaring Azure infrastructure as code, which is compiled into ARM templates.
Read more: Microsoft Learn
In the Ultra Transcenders books
AZ-305AZ-104SC-500AI-300AZ-900AZ-400
Each book explains Bicep in context, with comparison tables and the common traps.
Terms in this definition
Related terms
- ARM template test toolkit
Run via
Test-AzTemplate, these PowerShell checks compare templates and parameter files against best practice for ARM. For Bicep, use the Bicep linter, since the toolkit can't check it. - Azure Deployment Environments
Retiring on 22 February 2027 (Microsoft points people to Azure Verified Modules, Bicep or ARM deployments and Azure DevOps or GitHub workflows). Until then, it gives developers self-service app infrastructure built from curated IaC definitions kept in dev center catalogs, governed by platform engineers.
- Azure Landing Zones IaC Accelerator
Microsoft's preferred route to deploying and running the platform. A PowerShell bootstrap prepares GitHub or Azure DevOps with repositories, pipelines and runners, together with Bicep or Terraform code based on Azure Verified Modules.
- Azure landing zones library
Released in numbered versions and found under
platform/alz, this is where the Bicep and Terraform modules get the policy content and archetypes they deploy. Sovereign Landing Zone extends it. - Azure Verified Modules
Building blocks in Terraform or Bicep, backed by Microsoft, for deploying Azure resources and whole patterns according to Well-Architected guidance.
- azure/arm-deploy
Action deploying Bicep or ARM templates to management groups, subscriptions or resource groups from GitHub.
- Bicep linter
bicepconfig.json decides how serious each rule is. The rules, which descend from the ARM template test toolkit, run as static analysis inside both the VS Code extension and Bicep's CLI.
- Bicep module
One Bicep file can deploy another, referencing it by a local path, a br: registry reference or a template spec; the deployed file is known as a module.