2.1.2. Guest Users and External Access
💡 First Principle: External collaboration has two separate questions: who may bring outsiders in (invitation settings), and how much those outsiders may see and do once inside (guest access level, cross-tenant access, Conditional Access). Microsoft splits them into separate settings so you can open one without opening the other.
Microsoft Entra B2B collaboration is the mechanism behind guest users: an external person is invited, redeems the invitation with their own identity (their work account, a Microsoft account, or a one-time passcode), and appears in your directory as a user whose type is Guest. The settings live in the Microsoft Entra admin center under External Identities > External collaboration settings.
Who can invite. Four options, from most to least inclusive: anyone in the organization (including guests and non-admins) can invite; member users and users in specific admin roles; only users in specific admin roles (such as User Administrator or Guest Inviter); no one. By default, all users — including existing guests — can invite. The Guest Inviter role can invite guests regardless of how the "members can invite" setting is configured, which is how you let one coordinator invite while locking everyone else out.
What guests can see. Three guest access levels: Same as members; Limited access to properties and memberships — the default, where guests can't enumerate users and groups; and Restricted to their own objects, the most restrictive. Collaboration restrictions are a separate list: allow invitations to any domain, deny specified domains, or allow only specified domains.
Cross-tenant access settings govern collaboration with other Microsoft Entra organizations, inbound and outbound, with defaults plus organization-specific overrides. Out of the box, B2B collaboration is enabled with every external organization, but your Conditional Access does not trust MFA or device claims from the guest's home tenant — so guests may be asked for MFA again in your tenant. Trust settings fix that for a named partner. B2B direct connect, which lets users from another organization join Teams shared channels without becoming guests, is blocked by default inbound and outbound, and both organizations must enable it for each other.
| Model | Account created in your tenant? | Conditional Access applies? | What it enables |
|---|---|---|---|
| Teams external access (federation) | No | No | Chat, calls and meetings with another organization's users |
| Guest access (B2B collaboration) | Yes — a guest user | Yes | Membership of teams, access to files and sites |
| B2B direct connect | No (a mutual trust) | Yes, via cross-tenant settings | Teams shared channels across organizations |
⚠️ Exam Trap: If a requirement says "external users must satisfy our Conditional Access policies" or "external users must access files in a team," the answer is guest access, not external access. External access never creates a directory object for Conditional Access to evaluate.
Reflection Question: A partner company's users are prompted for MFA twice — once at home and again in your tenant — every time they open a shared file. Which setting removes the second prompt without weakening security, and why is it not on by default?