2.1.1.6. Manage External Users
2.1.1.6. Manage External Users
💡 First Principle: The safest external account is one you never have to manage a password for. B2B collaboration lets a partner sign in with the identity their own organization (or provider) already controls, while your tenant keeps a user object you can put in groups, assign roles to, and remove when the project ends.
Scenario: Your company is starting a six-month project with Fabrikam. Fifteen Fabrikam engineers need access to a shared resource group and an internal app. Security wants only approved staff to send invitations, wants guests unable to browse the directory, and wants to stop anyone inviting personal Gmail or Outlook.com addresses.
What It Is: Microsoft Entra B2B collaboration is the External ID capability for workforce tenants that invites external people into your directory. When you invite someone, Microsoft Entra ID creates a user object with a UserType of Guest and a user principal name in the form email_domain#EXT#@yourtenant.onmicrosoft.com (for example john_contoso.com#EXT#@fabrikam.onmicrosoft.com). The guest authenticates with their own identity provider; your tenant stores no password for them.
Guest vs. Member User Type: UserType describes the person's relationship to your organization, not how they sign in:
- External guest: the normal B2B case. Their account lives elsewhere and they get guest-level (restricted) directory permissions.
- External member: an account from another tenant that should be treated as part of your organization, common in multitenant companies. You can invite as Member through the invitation API.
- You can convert Guest to Member (or back) on the user's profile, but do it only when the business relationship really changes.
By default, guests can manage their own profile and see limited information about other objects, but can't enumerate the directory. Directory permissions and Azure RBAC are separate: an invitation never grants an Azure role, so you still assign roles to the guest (or, better, to a group the guest joins).
Inviting Guests:
- One at a time: Microsoft Entra admin center, Entra ID > Users > New user > Invite external user (at least User Administrator). Enter the email, display name and an optional message, then assign groups or roles on the Assignments tab.
- In bulk: Users > Bulk operations > Bulk invite, download the CSV template, and fill in the two required columns, Email address to invite and Redirection url (bulk invite). Don't edit the template's first two rows.
- Script:
New-MgInvitationin Microsoft Graph PowerShell.
Redemption: Until the guest accepts, the profile's Invitation state is Pending acceptance, and you can Resend invitation from the user's B2B collaboration tile. Invitations don't expire. If the inviting tenant has published a privacy statement URL, the guest consents to it during first redemption.
External Collaboration Settings (Entra ID > External Identities > External collaboration settings, see configure external collaboration):
| Setting | Options (default in bold) |
|---|---|
| Guest user access | Same access as members; Limited access to properties and memberships of directory objects; Restricted to their own directory objects |
| Guest invite settings | Anyone in the organization, including guests; Member users and specific admin roles; Only users assigned to specific admin roles; No one, including admins |
| Collaboration restrictions | Allow invitations to any domain; Deny invitations to specified domains; Allow invitations only to specified domains |
The Guest Inviter role lets a user invite guests without a broader admin role, and it still works when invites are limited to specific admin roles. For allow and deny lists, you choose one list type, never both; switching type discards the existing list. A list doesn't affect guests who already redeemed, but a guest whose invitation is still pending fails to redeem once their domain is blocked.
Cross-Tenant Access Settings (Overview): Cross-tenant access settings govern collaboration with other Microsoft Entra organizations. Inbound settings control what their users can reach in your tenant; outbound settings control what your users can reach in theirs; trust settings decide whether your Conditional Access accepts their MFA and compliant-device claims. By default, B2B collaboration is enabled, B2B direct connect is blocked, and partner MFA isn't trusted. Organization-specific settings override the defaults. Use external collaboration settings for non-Entra identities such as social accounts.
Practical Implementation: Inviting a Guest with Microsoft Graph PowerShell
Connect-MgGraph -Scopes User.Invite.All
New-MgInvitation -InvitedUserDisplayName "Ana Ruiz" -InvitedUserEmailAddress "ana@fabrikam.com" -InviteRedirectUrl "https://myapplications.microsoft.com" -SendInvitationMessage:$true
# List guest accounts in the tenant
Get-MgUser -Filter "UserType eq 'Guest'"
⚠️ Common Pitfall: Leaving the default Guest invite settings in place. By default any user, including existing guests, can invite more guests, so a single partner account can quietly widen your external footprint.
⚠️ Exam Trap: Know which blade solves which problem. Blocking a domain or limiting who can invite belongs in External collaboration settings; trusting a partner tenant's MFA or limiting which of its users can come in belongs in Cross-tenant access settings. Also, a guest's UserType doesn't decide their Azure permissions; RBAC role assignments do.
Key Trade-Offs:
- Allow List vs. Deny List: An allow list is the tightest control but can push users towards emailing files when a legitimate partner isn't listed. A deny list is easier to live with but only stops the domains you anticipated.
- Open vs. Restricted Inviting: Letting members invite speeds collaboration; restricting invites to admins and Guest Inviters gives an audit trail at the cost of helpdesk requests.
Reflection Question: A partner already has 40 redeemed guests in your tenant when you add their domain to a deny list. What does the list change for those guests, and what would you use instead to review and remove their access?