Deploying Azure Landing zones
Evaluating Deployment Options
Use an Accelerator
This is the recommended approach. It deployes the conceptual architecure, which provides governance, security, and management from the start. You could use azure portal, Bicep or terraform to deploy.
Customize
Customize the environment to meet very specfic rquirements. It starts small and aim to align with the conceptual architecture.
Lets deploy few scenarios using ALZ Accelerator
Scenario 1:
Requirements:
- Scalable architecture
- No IaC
- Only public facing workloads
Architecture
- Deploy Enterprise-scale foundation using portal
- Dedicated Management subscription
- Online Application subscription
- No identity, connectivity (network) or Corp management groups or subscription
- Deploy Azure Policy
Solution
- login to portal and create 2 subscriptions. Here we are just creating subscriptions ahead of time and including them into landing zone. I call them Management and Online subscriptions.
We should be login with “Global Admin” for the tenant. Before we do that, goto Azure Entra / AD => Properties and make sure that “Access management for Azure resources” turned on.
Log off and login back. Now we also grant “Owner” access for tenant root management group.
- Launch the ALZ Accelerator from Landing zone documention provided below to deploy.
Scenario 2
This post is licensed under CC BY 4.0 by the author.