Cloud Foundation — Cluster Overview Map

A navigation map for the Cloud Foundation cluster. The four cluster maps — Landing Zone Foundations, Cloud Operating Model, Hybrid Connectivity, Sovereign Cloud — in sequence, each represented by its starting node. Use this to understand how the four maps compose into one curriculum.

BusinessCapabilityTechnologySource
Compass
  • Businesspersona, use case, outcome
  • Capabilitywhat the org needs to do
  • Technologythe technology choices
  • Sourcewhere the evidence sits
Guided journey · Step 1 of 4

Landing Zone — Identity Foundation

Map 1 — Landing Zone Foundations. Build the platform. Identity, network, governance, operations as the foundational quartet. 12–36 weeks; moderate spend and risk.

~ 24 weeks

Search any SKU, capability, risk, or source on this map.

Filter by type

Narrative intro

The Cloud Foundation cluster is a quartet, not a single map. Landing Zone Foundations builds the platform; Cloud Operating Model runs it as a product; Hybrid Connectivity extends it across the estate; Sovereign Cloud applies it under regulation. This map navigates the four — each cluster member represented by its starting node, in the order most large enterprises encounter them. Not all four apply to every organisation. Cloud-native digital natives may skip Hybrid Connectivity; unregulated industries may skip Sovereign Cloud. The first two maps — LZ and Operating Model — apply to every Microsoft-first cloud estate without exception.

Key takeaways

  • The Cloud Foundation cluster is a multi-year arc, not a single programme. Think in waves, not sprints.
  • Operating Model work starts inside the LZ build, not after it. Sequential delivery of these two produces a platform v1 that nobody adopts.
  • Hybrid Connectivity is often parallel to LZ; Sovereign Cloud is usually a regulatory trigger rather than a sequence step.
  • Two maps apply to everyone, two are conditional. Plan accordingly.

Programme shape

Estimated duration
52–156 weeks
Estimated FTE
The Cloud Foundation cluster as a whole. Platform engineering team standing up the landing zone, then running it as a product, extending it across the hybrid estate, and applying sovereign controls where regulated.
Spend tier
significant
Risk level
elevated

Not a single programme. The cluster is a multi-year arc. Most large enterprises will run the four maps in overlapping waves rather than strict sequence — Operating Model work starts inside the LZ build, Hybrid Connectivity may follow or run in parallel, Sovereign Cloud often follows a regulatory trigger rather than the natural sequence.

Back to all maps