Contents
In brief
Azure is navigable when you start from identity, the hierarchy, and a landing zone, not from a catalog of service names.
Original CloudExchangers explainer. It describes established public practice and labels the desk’s judgment as analysis. It is not a report of a newly announced event.
Start with the hierarchy
Microsoft’s Cloud Adoption Framework is the public map for how an organization should adopt Azure, not a shopping list. The useful top of that map is structure. Management groups hold subscriptions. Subscriptions hold resource groups. Resource groups hold resources. Identity, through Microsoft Entra ID, is what makes a person or a pipeline allowed to create any of it.
