Entra B2B Guest Access Security: Invitations, Reviews and Limits

How are guest accounts managed in Entra ID? Narrowing invitation rights, cross-tenant MFA trust, Conditional Access for guests, access reviews and cleanup of old accounts.
Technical summary
Technology
Microsoft Entra External ID, B2B collaboration, Cross-tenant access settings, Conditional Access, Access reviews, Microsoft Graph PowerShell
Topic
Managing guest identities from invitation to deletion
Level
Intermediate
Prerequisites
  • Security Administrator, or the equivalent administrator role listed on Microsoft Learn, for cross-tenant access and external collaboration settings
  • The Microsoft Graph PowerShell module
  • An Entra ID Governance license for access reviews
In this article7 sections

A consultant is added to a Teams team, a folder is shared with a supplier; the work ends, the guest account stays. A few years later, hundreds of external identities have piled up in the tenant, with nobody knowing who invited them, what they can access or whether they’re still needed. In this guide we look at Microsoft Entra B2B guest access from the identity management side: invitation rights, cross-tenant access settings and MFA trust, Conditional Access for guests, lifecycle with access reviews, and safe cleanup of old accounts.

Why guest accounts accumulate risk

In B2B collaboration, the guest signs in with their own organization’s identity (their own Entra ID tenant, a Microsoft account, email one-time passcode or a federated provider); in your tenant, a user object with userType = Guest is created. The account is yours, the identity is someone else’s. This model has its own risks:

  • The lifecycle isn’t under your control. When the guest leaves their own company, their account in the home tenant may be closed; but this doesn’t always happen, and for a guest invited with a personal email address there is no such link at all.
  • Directory visibility: By default a guest can read directory information, albeit limited. With loose settings, the user and group list can be used for reconnaissance.
  • Access buildup: Access granted through Teams teams, SharePoint sites, app assignments and groups remains after the project ends.
  • Unclear authentication strength: Access is granted without knowing whether the guest has MFA in the home tenant or which method they use.

External collaboration settings and invitation rights

The first place to look is the External Identities → External collaboration settings page in the Entra admin center. The settings here apply to the whole tenant; one wrong click affects all external collaboration.

Setting Options Recommended approach
Guest user access Same as members / Limited / Most restrictive Most restrictive: the guest can’t list other users and group memberships
Guest invite settings Everyone / Members and role holders / Role holders only / No one Only holders of roles such as Guest Inviter, or an approved request process
Self-service sign up via user flows On / Off Off unless there is a real need
Collaboration restrictions All domains / Allow list / Deny list An allow list if the partners are known; otherwise, at least an assessment for personal email domains
Allow external users to remove themselves from your organization On / Off On; a guest being able to leave on their own makes cleanup easier

Restricting invitation rights to role holders only also affects sharing done from Teams and SharePoint; users can no longer add new external people. A restriction without a request path pushes users to personal sharing tools. That’s why the restriction is designed together with how guest requests will be met. The method that scales is entitlement management access packages in Entra ID Governance: the partner organization is defined as a “connected organization”, the external user requests the package, an internal sponsor approves, access ends automatically at the end of the set period, and a guest account whose last access has ended can be removed.

Cross-tenant access settings and MFA trust

Cross-tenant access settings define the relationship with other Entra ID tenants separately in the inbound and outbound directions. The default settings apply to all external tenants; separate “organizational settings” can be added for specific organizations.

The trust settings section in the inbound settings determines where guest MFA is performed:

Trust setting When off When on
Trust MFA from Microsoft Entra tenants The guest registers and verifies MFA separately in your tenant MFA completed in the home tenant is accepted
Trust compliant devices The compliant device condition can’t be met for a guest The home tenant’s Intune compliance claim is accepted
Trust Microsoft Entra hybrid joined devices The hybrid join condition can’t be met The home tenant’s device state is accepted

It’s more controlled to turn on MFA trust not in the default settings but per organization, only for partner tenants whose MFA enforcement you know. With trust off, the guest registers their own MFA method in your tenant; that means a separate method in each tenant, but the control is yours. When trust is on, you depend on the strength of the method in the home tenant. If you require a phishing-resistant authentication strength, the method in the home tenant must meet it. If it doesn’t, the guest is left at the door.

Outbound settings, on the other hand, determine which external tenants your own users can be guests in. From a data leakage and enterprise cybersecurity standpoint, this direction carries the same weight; Tenant Restrictions v2 can also be evaluated to enforce access only to approved tenants from corporate devices.

Applying Conditional Access to guests

The Guest or external users option in the user scope of Conditional Access allows targeting external user types separately: B2B collaboration guest users, B2B collaboration member users, B2B direct connect users (Teams shared channels), local guest users, service provider users and other external users. The scope can be narrowed further by selecting specific external tenants.

A typical policy set for guests:

  1. MFA for all guests: All cloud apps, “Require MFA” or an authentication strength defined for external users.
  2. Limiting app scope: Guests access only collaboration apps (Office 365, specific corporate apps); other apps are blocked for guests.
  3. Session controls: App-enforced restrictions for browser-only access and download restrictions in SharePoint and OneDrive from unmanaged devices.
  4. Risky sign-ins: If your license coverage allows, the sign-in risk condition can be applied to guests too. User risk remediation (a password change) for a guest can’t be done in your tenant; that’s why sign-in risk is more meaningful.

For the general framework of policy design, see the Conditional Access planning guide. Run guest policies in report-only mode first too, and see in the sign-in logs how external users are affected. A picture we often see in the field: a device compliance policy scoped to “all users” silently shuts out guests who can’t be enrolled in Intune, and the problem is only noticed when a partner calls.

Lifecycle with access reviews

Access reviews are the built-in way to have guest access periodically approved by a responsible person, and they require an Entra ID Governance (or relevant P2 coverage) license; verify the current license mapping in Microsoft’s documentation. Things to watch in the design:

  • Scope: All Microsoft 365 groups and Teams teams that contain guests, with the “Guest users only” option.
  • Reviewer: Group owners; for groups without an owner, a security or IT lead as the fallback reviewer. Guest self-review should be used only in low-risk scenarios.
  • Frequency: A risk-based cycle, such as every three months for sensitive project groups and every six months for general collaboration groups.
  • If no response: Remove access. Silence doesn’t count as approval. Showing the reviewer “recommendations” based on last sign-in information improves decision quality.
  • Auto-apply results: Should be on. In a tenant-wide guest review, the option that blocks a denied guest from signing in and removes them from the tenant after a set period gives you time to bring back a partner removed by mistake.

Finding and cleaning up old guest accounts

The first cleanup is done before the access review cycle starts; otherwise the first review round gets clogged with hundreds of records with no clear owner. Microsoft Graph PowerShell can retrieve guests’ creation date, invitation state and last sign-in information. Reading the signInActivity property requires the AuditLog.Read.All permission and an Entra ID P1 or higher license.

Connect-MgGraph -Scopes "User.Read.All","AuditLog.Read.All"

$threshold = (Get-Date).AddDays(-180)
Get-MgUser -Filter "userType eq 'Guest'" -All `
  -Property Id,DisplayName,Mail,CreatedDateTime,ExternalUserState,SignInActivity |
  Select-Object DisplayName, Mail, CreatedDateTime, ExternalUserState,
    @{n='LastSignIn';e={$_.SignInActivity.LastSignInDateTime}} |
  Where-Object { ($_.ExternalUserState -eq 'PendingAcceptance' -and $_.CreatedDateTime -lt $threshold) -or
                 ($_.LastSignIn -and $_.LastSignIn -lt $threshold) -or
                 (-not $_.LastSignIn -and $_.CreatedDateTime -lt $threshold) } |
  Export-Csv .\stale-guests.csv -NoTypeInformation -Encoding UTF8

The 180-day threshold in the example is a starting value; adjust it to your own collaboration cycle. The safe cleanup order:

  1. Share the list with the inviting department or the sponsor; set aside those with active contracts.
  2. Block the rest from signing in (Update-MgUser -UserId <id> -AccountEnabled:$false) and allow a waiting period.
  3. At the end of the waiting period, delete the accounts; deleted users remain restorable for a certain period.
  4. Remove old unaccepted invitations (PendingAcceptance) directly.

Disable first, then delete. This order lets you bring back a partner who ended up on the wrong list with a single command.

The Teams and SharePoint side works together with these identity settings: Teams’ guest access setting, SharePoint’s organization-level external sharing level and the SharePoint–Entra B2B integration determine how the guest is created and which policies apply to them. For details on sharing settings, see the SharePoint and OneDrive external sharing security article, and for other tenant-wide basic settings, the Microsoft 365 security checklist. Current descriptions of external identity settings are in the Microsoft Entra External ID documentation. Once identity and sharing boundaries are set, design user groups and portal access accordingly during a SharePoint intranet setup.

Setting up the guest access model, from the invitation process to access reviews, is part of identity and access management work; evaluating it together with Teams and SharePoint settings is part of the Microsoft 365 security scope.

Frequently asked questions

In whose tenant is MFA applied to guest users?

By default, when a Conditional Access policy in your tenant requires MFA, the guest registers and verifies MFA in your tenant. If MFA trust is turned on for that organization in cross-tenant access settings, MFA completed in the home tenant is accepted.

Is it right to turn off guest invitation rights completely?

It’s strict from a security standpoint, but if no request process is designed, users turn to personal sharing routes. Restricting invitation rights to role holders and meeting guest requests with sponsor-approved access packages is a more sustainable model.

What does a guest with no last sign-in information mean?

The account has either never been used or was used before sign-in activity started being recorded. If its creation date is old and its sponsor doesn’t confirm the need for access, it’s first disabled, then deleted.

Which license do access reviews require?

Access reviews are a Microsoft Entra ID Governance feature and require an appropriate license; for guests there may also be a billing model based on monthly active users rather than per user. Verify the current license terms in Microsoft’s documentation.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Cybersecurity

Firewall, VPN, endpoint security and threat prevention. We reduce the attack surface and measure and report the risks.

Knowledge Center

Other articles