ALZ Accelerator
Learn how to use the Azure Landing Zone Accelerator to get to a GitHub CI/CD configuration recommended by Microsoft.
Microsoft regularly updates Azure Landing Zones and its governance guardrails, so it makes sense to use that. But how do you customise it, extend it, and merge it with your own IP? These labs are aimed at partners but anyone who wants to go deeper with ALZ will get something from these labs.
Azure Landing Zones (ALZ) has evolved significantly. Microsoft maintains the open source repositories including governance guardrails and best practices. There is enormous value in leveraging that IP and knowing that you are building your platform landing zone based on Microsoft’s recommended configuration and that it will be updated to keep pace with the velocity of innovation in public cloud.
The introduction of the Azure Landing Zone Accelerator means you can quickly establish a solid CI/CD configuration, and these labs will walk through an example process. It is not mandatory to use the ALZ Accelerator if you are experienced in setting up CI/CD pipelines for Terraform deployments, but it is highly recommended to secure powerful workload identities in line with recommended standards.
The move to Azure Verified Modules (AVM) for modular and structured infrastructure deployment has been a game changer, especially when combined with the flexibility of the alz Terraform provider.
Learn how to use the Azure Landing Zone Accelerator to get to a GitHub CI/CD configuration recommended by Microsoft.
Follow this guide to deploy an Azure Landing Zone using Azure Verified Modules
A reference guide to common library patterns if you know what you are doing with Landing Zone libraries and the alz provider.
Historically you could have accused Azure Landing Zones of being monolithic, forcing you to choose between adopting and falling in line with the Microsoft approach, or forging your own path and developing your own platform landing zone infrastructure as code standards including policy.
Now the combination of Azure Verified Modules and the Azure Landing Zone library approach allows you to build on the Microsoft managed IP, giving you the ability to extend, augmenting and override that baseline with your own IP and definitions for a true level of flexibility.
These labs are designed for partners who need to deeply understand how ALZ works — particularly those with existing landing zone IP or custom Azure Policy guardrails. You’ll learn how to integrate your assets alongside the Microsoft-maintained baseline and get the best of both worlds.
Before diving in, you should be familiar with:
Understanding the Azure Landing Zone approach provides a solid foundation that will help with: