1.1. The Tenant as a Control Plane
💡 First Principle: A tenant is the boundary inside which every user, setting and piece of data lives, but control over it is split across specialist portals — each portal owns one class of decision. If you know which kind of decision a requirement is (who someone is, what threat to stop, what data to protect, what a workload or AI feature should do), you know where to configure it.
Why does this matter? Because a large share of exam questions are, underneath the scenario, "where would you do this?" questions. A candidate who pictures Microsoft 365 as a single admin center will pick the right-sounding setting in the wrong portal, and every one of the four answer options can look like a real menu item. A candidate who knows that authentication decisions belong to Microsoft Entra, threat decisions to Microsoft Defender, data decisions to Microsoft Purview, and service and AI configuration to the Microsoft 365 admin center can usually eliminate half the options before reading them closely.
The mental model is a city with one population register and several departments. The register (Microsoft Entra ID) records who everyone is. The police (Defender), the records office (Purview) and city services (the Microsoft 365 admin center and the workload admin centers) each make their own decisions, but they all look people up in the same register.
⚠️ Common Misconception: It's easy to assume the Global Administrator can do anything, anywhere. In practice, Global Administrator holds the widest tenant-scoped role, but control can be deliberately carved out of it: objects in a restricted management administrative unit can be changed only by admins whose role is scoped to that unit — a Global Administrator without such a scoped role can't modify them. "Most powerful role" is not the same as "unlimited."