Landing zones¶
Placeholder
This page will be auto-populated from Azure Resource Graph in a later phase. For now, the structure below is the agreed model.
Topology¶
flowchart TB
MG[Management Group] --> P[Platform subs]
MG --> L[Landing zone subs]
P --> ID[Identity]
P --> MGMT[Management + monitoring]
P --> CON[Connectivity / hub]
L --> EMEA[EMEA workloads]
L --> BR[Brazil workloads]
L --> CN[China workloads - separate cloud]
Conventions¶
- Naming:
<region>-<env>-<workload>-<type>(see Standards). - Tagging:
costcenter,env,owner,data_residencymandatory. - Networking: hub-and-spoke; private endpoints for PaaS; egress via firewall.