1.1.1. Tenants, Workloads, and the Admin Center Map
💡 First Principle: Each portal exists because one team in a real organization owns that class of decision. Identity teams, security operations, compliance officers and service owners all need their own console, scoped to their own work — so Microsoft built the portals around those jobs, not around products.
A tenant is your organization's dedicated instance of Microsoft cloud services. When you create a Microsoft 365 subscription you get a tenant with an initial onmicrosoft.com domain, and every user, group, mailbox, site, policy and Copilot setting you configure lives inside that tenant. Workloads are the services inside it — Exchange Online, SharePoint and OneDrive, Microsoft Teams — and, increasingly, the AI services layered across them: Copilot, Copilot Chat, Copilot Cowork and agents.
The portals map to decisions like this:
| If the requirement is about... | Configure it in... | Examples from this exam |
|---|---|---|
| Tenant setup, licenses, users, Copilot and agent settings, service health | Microsoft 365 admin center | Org settings, domains, group-based licensing, Copilot settings, the agent registry, usage reports |
| Who someone is and how they prove it | Microsoft Entra admin center | Authentication methods, Conditional Access, PIM, administrative units, Microsoft Entra Agent ID |
| Threats in email and collaboration | Microsoft Defender portal | Threat policies, Threat Explorer, alerts and incidents, Attack simulation training |
| What data is, and what may happen to it | Microsoft Purview portal | Sensitivity labels, DLP, retention, Data Security Posture Management (DSPM) |
| How a single workload behaves | Exchange, SharePoint and Teams admin centers | Shared mailboxes, site permissions and SharePoint Advanced Management, meeting policies |
| How Microsoft 365 apps behave for users | Cloud Policy service (Microsoft 365 Apps admin center) | The Allow web search in Copilot policy |
The Microsoft 365 admin center is the hub, and that's exactly why it misleads people: it links to most of the others. Its Copilot settings page, for example, has an entry for web search — but that entry only links you to the Cloud Policy service, where the actual policy lives. When a question offers "a setting in the Microsoft 365 admin center" next to "a policy in the specialist portal," ask which portal actually owns the decision.
⚠️ Exam Trap: Watch for an answer that names a real setting in a portal that only links to it. If the Microsoft 365 admin center merely points to Cloud Policy, Entra or Purview for a decision, the correct answer is the portal that holds the policy.
Reflection Question: A security team wants to stop a phishing campaign, and a compliance team wants to stop customer card numbers from leaving the organization by email. Both involve email. Why do they configure their controls in different portals?