Cloud reference architecture
Azure landing zone
Management groups, policy-driven governance and a hub-and-spoke network for Azure subscriptions at scale.
Design principles
- Management groups reflect governance, not org charts
- Azure Policy assigned at the highest sensible scope
- Platform and application landing zones separated
- Subscriptions vended with network and policy baselines
Components
| Component | Role |
|---|---|
| Management groups | Policy and access inheritance |
| Azure Policy initiatives | Preventive and corrective controls |
| Connectivity subscription | Hub VNet, firewall, DNS |
| Management subscription | Log Analytics, automation |
| Defender for Cloud | Posture and workload protection |
More Cloud architectures
AWS landing zone
A multi-account AWS foundation with organization-wide guardrails, centralized logging and a shared network hub.
View architectureKubernetes platform architecture
A shared EKS or AKS platform with tenancy, identity, policy, GitOps and observability as platform services.
View architectureHybrid cloud
Connecting data centers and colocation to AWS and Azure with consistent identity, networking and operations.
View architectureAdapt this to your environment
We'll help you apply this pattern to your constraints and existing estate.

