Why Landing Zones Matter (What are they and How to Build One)
summary
Explains what a landing zone actually provisions and why it matters: platform subscriptions for identity, connectivity, management and per-app boundaries to avoid subscription limits and accidental deletes. Shows two production-ready routes that work in real projects: using Azure verified modules to compose reusable patterns, or the Landing Zone Accelerator to generate a GitHub repo, CI/CD and a ready Terraform/Bicep pipeline. Demonstrates subscription vending that programmatically creates a subscription, managed identity, storage, monitoring and cost alerts, and exports ClickOps to code with Terraform state with backups.
AI-written summary · about
chapters (10)
- 0:00Introduction and agenda
- 0:54Why landing zones matter
- 5:48Understanding landing zone components
- 9:20Designing and vending
- 14:09Approaches for building
- 19:56Using the ALZ accelerator
- 26:33Making environments production-ready
- 38:13Addressing multi-geo requirements
- 42:43Handling brownfield migrations
- 47:02Resources and conclusion
related talks
41mBuilding a solid foundation on Azure: Landing Zones best-practices
12mAzure Landing Zone: Accelerating Cloud Transformation
45mThe Automation of a Landing Zone- 45mThe Automation of a Landing Zone
42mHands-on with the Terraform Module for AWS Landing Zone
40mFrom Launch Pad to Landing Zone: DevOps Governance with Terraform
23mInfrastructure and application landing zones on HCP
45mAccelerate your Azure Platform Journey with...