CoursesAzure securityGovernance & incident response

Management groups & landing zones

Inherited guardrails, secure-by-default subscriptions.

Advanced30 min · lesson 14 of 15

Preventive guardrails only scale when they are applied automatically to every subscription. Management groups plus an Azure Landing Zone give you a hierarchy where policy, RBAC, networking, and logging are inherited, so a new subscription arrives already fenced rather than after a hardening sprint.

Management groups and inherited baselines

Management groups sit above subscriptions and form a tree that policy and RBAC inherit down. Assign your security-benchmark initiative, your logging deployIfNotExists policies, and your break-glass RBAC once at a top-level management group, and every subscription beneath — including ones created next year — gets them automatically. Deny assignments (from Blueprints or managed applications) can lock specific resources so that even a subscription Owner cannot alter them, giving you controls that survive delegated administration.

guardrails inherited from a management group
# Structure: root MG → platform / landing-zones / sandbox MGs → subscriptions.
# Assign the baseline once at the top; it inherits to every subscription below.
az account management-group create --name landing-zones
az policy assignment create --name require-diag \
--policy "Deploy diagnostic settings to Log Analytics" \
--scope /providers/Microsoft.Management/managementGroups/landing-zones \
--location eastus --mi-system-assigned # deployIfNotExists needs an identity
# New subscriptions moved under landing-zones inherit logging automatically.

Secure-by-default subscriptions

An Azure Landing Zone (Cloud Adoption Framework) is the packaged version: a management-group hierarchy with baseline policies, RBAC, hub-and-spoke networking, and centralized logging pre-applied, provisioned through infrastructure as code. A subscription-vending process then hands teams a subscription that is already fenced — policies enforcing encryption and private networking, diagnostics wired to the logging workspace, Defender enabled — with no window of exposure and no checklist to forget. Security becomes a property of how subscriptions are created.

Subscription vending applies the baseline
1subscription request
a team needs a subscription
2landing-zone vending (IaC)
placed under the right MG
3baseline inherited
policy, RBAC, network, logging, Defender
4secure on day zero
no unprotected window
Guardrails as code make the secure path the default path — the strongest security is the one nobody has to remember.
Manual subscription setup always drifts
Hand-configuring each new subscription guarantees inconsistency and a window where it exists without its guardrails. Automate the baseline through management-group inheritance and landing-zone vending so every subscription — including the one spun up in a hurry — arrives fully fenced.