Home
Important
The Future of ALZ-Bicep Classic
With Bicep AVM now generally available and set as the default in the ALZ Accelerator for Bicep, we're beginning the deprecation process for classic ALZ-Bicep.
| Date | Action |
|---|---|
| Now | Bicep - Azure Verified Modules for Platform Landing Zone (ALZ) is the default starter module |
| February 16th, 2026 | Bicep (Classic) starter module removed from Accelerator |
| February 16th, 2027 | ALZ-Bicep repository archived |
Currently, ALZ-Bicep is still supported in the Accelerator as "Bicep Classic - Complete" (documentation), but this was removed in its entirety on February 16th, 2026.
Although it has been removed from the Accelerator, the ALZ-Bicep repository is still supported in terms of:
- Bug fixes
- Security patches
- Policy refreshes
...for a period of 12 months after that date. After February 16th, 2027, the ALZ-Bicep repository will be archived and no longer supported.
Migration Support: For guidance on migrating to Bicep AVM, please visit aka.ms/alz/acc/bicep.
Welcome to the wiki of the Azure Landing Zones Bicep repo. This repo contains the Azure Landing Zone Bicep modules that help you create and implement the Azure Landing Zone Conceptual Architecture in a modular approach.
Artefacts like policies etc. are pulled down from the Azure/Enterprise-Scale repo to ensure the choice of tooling to implement the architecture, produce the same outputs.
Have you seen our page in the Azure Architecture Center here: Azure landing zones - Bicep modules design considerations
- Wiki Home
- Deployment Flow
- Consumer Guide
- How Does ALZ-Bicep Implement Azure Policies?
- How Does ALZ-Bicep Implement resilient deployments across availability zones?
- Contributing
- Telemetry Tracking Using Customer Usage Attribution (PID)
- Azure Container Registry Deployment - Private Bicep Registry
- Sample Pipelines
- Code Tours
We have created a short 3-part series of video on the Azure Enablement Show that can be found below:
