2.1. Manage Identities in Microsoft Entra
💡 First Principle: Every access decision in Microsoft 365 is a question about a directory object — a user, a guest, a group, a role assignment or an administrative unit. If you choose the right kind of object for each job, permissions, licensing and policy fall into place. If you choose the wrong kind, no amount of policy will make the design clean.
Why care? Identity mistakes compound. A distribution list used where a security group was needed can't grant access to a SharePoint site. A guest added through Teams external access instead of guest access can't be governed by Conditional Access. A help desk given User Administrator across the whole tenant, instead of a role scoped to an administrative unit, can reset passwords it should never touch. Most of these mistakes are made once, at design time, and then copied a thousand times.
The mental model for this section is a set of comparison tables. Each identity topic has two or three look-alike options — mail contact vs mail user, external access vs guest access, Microsoft 365 group vs security group, eligible vs active role assignment — and the exam asks you to pick the one that meets a stated requirement. Learn the deciding difference between each pair and most questions in this area become straightforward.
⚠️ Common Misconception: Teams external access and guest access are often treated as the same thing. External access (federation) lets your users chat, call and meet with people in other organizations without creating any account in your tenant, so Conditional Access can't apply to those people. Guest access creates a Microsoft Entra B2B guest account in your directory, which can be added to teams and governed by Conditional Access and MFA.