Every cloud provider will happily sell you a landing zone. None of them will tell you the part that matters: landing zones don't fail at launch — they fail at month 14, when the second platform team has arrived, the first customization framework has been deprecated, and the governance bill has quietly compounded. This guide compares the three providers' landing-zone models as they actually behave in production, with named deployments, real cost math, and the failure points nobody puts in the reference diagram.

The three definitions diverge more than the marketing admits. AWS Control Tower orchestrates existing services (Organizations, Service Catalog, IAM Identity Center, Config) into a governed multi-account structure and calls the result a landing zone. Microsoft's Azure landing zone model splits into a centralized platform landing zone plus per-team application landing zones, deployed from Azure Verified Modules accelerators. Google doesn't even lead with the term — Google Cloud's landing zone design calls it a cloud foundation: a modular configuration of resource hierarchy, identity, network, and policy that you assemble yourself from Terraform blueprints.

That divergence is not cosmetic. It determines who owns the toil when the foundation drifts, which automation framework you'll be forced to migrate off of, and which line item eats your Year Two budget.

The Pattern: Three Layers, Three Very Different Owners

Strip the branding away and every landing zone is the same three-layer pattern:

LAYER 1 — RESOURCE HIERARCHY (the blast-radius boundary)
  AWS:    Organization -> OUs -> accounts        (account = hard boundary)
  Azure:  Management groups -> subscriptions    (subscription = boundary)
  GCP:    Organization -> folders -> projects  (project = boundary)

LAYER 2 — POLICY & IDENTITY (the guardrails)
  AWS:    SCPs + Control Tower controls (preventive/detective via Config)
  Azure:  Azure Policy + RBAC/Entra ID, assigned at management-group scope
  GCP:    Organization policies (constraints) + IAM, inherited down the tree

LAYER 3 — AUTOMATION (the part that rots)
  AWS:    Account Factory / AFT / CfCT  (three overlapping frameworks)
  Azure:  ALZ accelerators (Bicep/Terraform AVM) — after Blueprints died
  GCP:    Cloud Foundation Fabric / Stellar Engine / terraform-example-foundation

WHO OWNS YEAR-TWO DRIFT:
  AWS:    you own drift detection (Config rules, aggregators)
  Azure:    you own drift detection (Policy compliance state)
  GCP:    org policies are enforced at the API — drift is mostly impossible