Sovereign landing zone now uses the same platform as Azure landing zone. Use these labs to deploy a set of sovereign guardrails for your Azure environment and learn how to add country or industry packs.
Sovereign landing zone (SLZ) now builds on the same platform as Azure landing zone (ALZ). Microsoft has transposed the sovereign guardrails to use ALZ library constructs, ensuring consistency with the core platform while maintaining sovereignty controls.
The underlying ALZ platform leverages Azure Verified Modules (AVM) for infrastructure and the ALZ Terraform provider for policy management. This modular approach means you can layer sovereign requirements alongside the Microsoft-maintained baseline without forking the codebase.
These labs focus on deploying sovereign guardrails and understanding how to extend them with country or industry-specific packs. The ALZ labs provide deeper context on the platform architecture and customization patterns that are equally relevant when working with SLZ.
An overview for Azure landing zones, Sovereign landing zone as a variant of an Azure landing zone and where it sits in the Microsoft Sovereign Cloud portfolio, plus Azure Verified Modules in the Terraform Registry. Then a summary of what is in these labs.
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 a Sovereign landing zone using Azure Verified Modules
Deep dive into Azure landing zone library format. Run through its various assets and constructs. See how you can create your own libraries and how the alz provider and metadata files can be used to achieve customisation and extensibility.
A set of examples for commonly used alz provider and library metadata patterns for Sovereign landing zones.
Before diving in to the, you should be familiar with:
Understanding the Azure landing zone approach provides a solid foundation that will help with: