How to Enable or Disable Guest Access in Microsoft Teams (Admin Center, Entra B2B & PowerShell Runbook)

Allowing external partners, vendors, and contractors to collaborate inside Microsoft Teams requires more than flipping a single switch in the Teams Admin Center. In a modern Microsoft 365 tenant, Guest Access is governed by a four-layer authorization chain spanning Microsoft Entra ID (B2B External Identities), Microsoft 365 Groups (Group.Unified), SharePoint Online, and Microsoft Teams Guest Policies.

If an administrator disables Guest Access in the Teams Admin Center alone without restricting the underlying Group.Unified directory settings, team owners may still invite external guests via Outlook or Entra ID, or conversely, if Guest Access is enabled globally, sensitive executive or compliance teams may inadvertently allow external guests unless blocked via a per-Team Group.Unified.Guest directory setting override.

In this enterprise governance guide, we cover how to enable or disable Microsoft Teams Guest Access globally, how to block guests on specific confidential Teams while keeping tenant-wide guest collaboration open, and how to audit pending guest invitations using Microsoft Graph PowerShell.


The 4-Layer Microsoft Teams Guest Access Architecture

For an external user to be invited to and participate in a Microsoft Team, all four governance layers must align:

  1. Layer 1 — Microsoft Entra External Collaboration Settings: Controls who in the organization can send B2B guest invitations (allowInvitesFrom: Everyone, Admins and Guest Inviters, Member users, or No one) and enforces cross-tenant domain allow/block lists.
  2. Layer 2 — Microsoft 365 Groups (Group.Unified Directory Settings): Controls whether guests can be added to Unified Groups (AllowToAddGuests) and whether existing guests can access group resources (AllowGuestsToAccessGroups).
  3. Layer 3 — SharePoint Online & OneDrive External Sharing: Controls whether guests can access files stored in the Team's backing SharePoint site (ExistingExternalUserSharingOnly or ExternalUserAndGuestSharing).
  4. Layer 4 — Microsoft Teams Admin Center & Per-Team (Group.Unified.Guest) Settings: Controls Teams client access, calling, meeting, messaging, and per-Team guest restrictions.
Microsoft Teams Guest Access: 4-Layer Governance & Per-Team Override Flow 1. Entra External ID • B2B Collaboration - allowInvitesFrom policy - Cross-Tenant Access - Domain Allow/Blocklist • Identity Protection - Guest MFA & Terms of Use - #EXT# UPN Provisioning 2. M365 Group.Unified • Tenant Template - ID: 62375ab9-6b52-... - AllowToAddGuests: true - AllowGuestsToAccessGroups • Ownership Guardrail - AllowGuestsToBeGroupOwner: false (Default & Enforced) 3. Teams Guest Policy • Teams Admin Center - Users > Guest Access: On - Calling & Meeting controls - Screen sharing mode • Team Client Controls - AllowCreateUpdateChannels - AllowDeleteChannels 4. Per-Team Override • Group.Unified.Guest - ID: 08d542b9-071f-... - Applied to specific GroupId - AllowToAddGuests: false • Confidential Teams - Blocks new guest invites on HR / Board / Compliance Enterprise Teams Guest Governance Checklist: 1. Keep tenant-wide Guest Access enabled in Teams Admin Center, but restrict confidential Teams via Group.Unified.Guest (`08d542b9-071f-4e16-94b0-74abb372e3d9`) or Sensitivity Labels. 2. Note the difference between AllowToAddGuests=false (blocks new guests; existing stay) and AllowGuestsToAccessGroups=false (revokes all guest access). 3. Periodically purge stale guests stuck in externalUserState = 'PendingAcceptance' for more than 30 days.

Method 1: Enable or Disable Guest Access in Microsoft Teams Admin Center (GUI)

By default, Microsoft Teams Guest Access is enabled in modern Microsoft 365 tenants. To verify or toggle tenant-wide Guest Access in the portal:

  1. Sign in to the Microsoft Teams Admin Center (https://admin.teams.microsoft.com) as a Teams Administrator or Global Administrator.
  2. In the left navigation menu, expand Users and click Guest access.
  3. Toggle Guest access to On (to allow external guest members in Teams) or Off (to block guest access across the Teams client).
  4. Configure granular Calling, Meeting, and Messaging permissions for guests:

- Calling: Make private calls (On / Off). - Meetings: Allow IP video (On / Off), Screen sharing mode (Single application, Entire screen, or Disabled), Allow Meet Now (On / Off). - Messaging: Edit sent messages, Delete sent messages, Chat, Giphy in conversations (with content rating filter).

  1. Click Save. Changes take between 2 to 6 hours to propagate across the tenant.

Method 2: Audit & Configure Tenant-Wide Guest Settings via Microsoft Graph PowerShell

While the Teams Admin Center controls the Teams client UI, the underlying Microsoft 365 Groups (Group.Unified) directory setting determines whether guest users can actually be added to the Entra ID group backing each Team.

Below is the live-tested script verified against the LAB 365 (lab365.in / xzf58.onmicrosoft.com) tenant using certificate-based unattended authentication to inspect your Group.Unified template (62375ab9-6b52-47ed-826b-58e47e0e304b) and audit existing guest accounts:

POWERSHELL
# Connect to Microsoft Graph (Unattended Certificate Auth or Interactive)
$TenantId       = "ab85c7a1-366d-44ba-acc6-924fa0950045"
$ClientId       = "c841ae33-4093-4385-8a90-6a530761f9b9"
$CertThumbprint = "BEAC429DE404B46FF030811C0C9DE00DE701C027"

Connect-MgGraph -TenantId $TenantId -ClientId $ClientId -CertificateThumbprint $CertThumbprint -NoWelcome

# 1. Inspect Tenant-Level Group.Unified Guest Settings (Template ID: 62375ab9-6b52-47ed-826b-58e47e0e304b)
$DirSettings = (Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/beta/settings").value
$UnifiedSetting = $DirSettings | Where-Object { $_.templateId -eq "62375ab9-6b52-47ed-826b-58e47e0e304b" }

if ($UnifiedSetting) {
    Write-Host "=== Tenant Group.Unified Guest Configuration ($($UnifiedSetting.id)) ===" -ForegroundColor Cyan
    $UnifiedSetting.values | Where-Object { $_.name -like "*Guest*" } | ForEach-Object {
        [PSCustomObject]@{
            SettingName = $_.name
            Value       = $_.value
        }
    } | Format-Table -AutoSize
}

# 2. Audit All External Guest Accounts & Invitation Redemption Status
$Guests = Get-MgUser -Filter "userType eq 'Guest'" -All `
    -Property Id,DisplayName,UserPrincipalName,Mail,ExternalUserState,CreatedDateTime

Write-Host "=== External Guest Users in Tenant ($($Guests.Count)) ===" -ForegroundColor Cyan
$Guests | Select-Object DisplayName, UserPrincipalName, ExternalUserState, CreatedDateTime | Format-Table -AutoSize

Live Output from the LAB 365 Dev Tenant (lab365.in):

TEXT
=== Tenant Group.Unified Guest Configuration ===

SettingName               Value
-----------               -----
AllowGuestsToBeGroupOwner false
AllowGuestsToAccessGroups true
GuestUsageGuidelinesUrl   
AllowToAddGuests          true

=== External Guest Users in Tenant (1) ===

DisplayName UserPrincipalName                             ExternalUserState CreatedDateTime
----------- -----------------                             ----------------- ---------------
sunil Gmail sunilkms_gmail.com#EXT#@xzf58.onmicrosoft.com PendingAcceptance 2023-04-05T12:48:28Z

Understanding the Key Group.Unified Guest Parameters

ParameterDefaultOperational Impact
AllowToAddGueststrueControls whether Team owners can invite new guests across the tenant. Existing guests retain access.
AllowGuestsToAccessGroupstrueMaster kill-switch. Setting this to false immediately blocks both new guest invitations and existing guests from accessing any Microsoft 365 Group or Team.
AllowGuestsToBeGroupOwnerfalseControls whether an external guest can be promoted to Group/Team Owner. Always keep set to false.

Method 3: Block Guest Access on a Single Sensitive Team (Group.Unified.Guest)

In enterprise environments, you rarely want to disable Guest Access across the entire tenant. Instead, you want Guest Access enabled globally for project teams, while blocking Guest Access on specific confidential Teams (such as Compliance Admins, Executive Board, or M&A Legal).

You can accomplish this per-Team override using the Group.Unified.Guest directory setting template (08d542b9-071f-4e16-94b0-74abb372e3d9) against the specific Team's GroupId:

POWERSHELL
# Target Sensitive Team / M365 Unified Group (e.g., 'Compliance Admins' in LAB 365)
$GroupId = "f8092e73-ed1b-4826-92a9-b9c1e408761b"
$GuestTemplateId = "08d542b9-071f-4e16-94b0-74abb372e3d9" # Group.Unified.Guest

# Check if a per-group setting already exists
$ExistingGroupSettings = (Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/beta/groups/$GroupId/settings").value
$TargetSetting = $ExistingGroupSettings | Where-Object { $_.templateId -eq $GuestTemplateId }

$Payload = @{
    templateId = $GuestTemplateId
    values     = @(
        @{
            name  = "AllowToAddGuests"
            value = "false" # Block adding any external guests to this specific Team
        }
    )
} | ConvertTo-Json -Depth 4

if ($TargetSetting) {
    Invoke-MgGraphRequest -Method PATCH -Uri "https://graph.microsoft.com/beta/groups/$GroupId/settings/$($TargetSetting.id)" -Body $Payload
    Write-Host "[✔] Updated per-Team Guest restriction on GroupId: $GroupId" -ForegroundColor Green
} else {
    Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/beta/groups/$GroupId/settings" -Body $Payload
    Write-Host "[✔] Created per-Team Guest restriction (AllowToAddGuests = false) on GroupId: $GroupId" -ForegroundColor Green
}

Once applied, when a Team Owner of Compliance Admins attempts to add an external email address in the Microsoft Teams client, Teams will display "We didn't find any matches" and prevent the invitation while leaving Guest Access active for all other Teams.


Method 4: Configure Team-Level Guest Channel Permissions (Set-Team)

Even when guests are allowed inside a Team, they should never be allowed to create, rename, or delete channels by default. You can enforce strict guest channel permissions using the MicrosoftTeams PowerShell module (v6+) or the Microsoft Graph Update-MgTeam cmdlet:

POWERSHELL
# Option A: Using MicrosoftTeams PowerShell Module (v6+)
Connect-MicrosoftTeams

Set-Team -GroupId "f8092e73-ed1b-4826-92a9-b9c1e408761b" `
    -AllowGuestCreateUpdateChannels $false `
    -AllowGuestDeleteChannels $false

# Option B: Using Microsoft Graph PowerShell SDK
Update-MgTeam -TeamId "f8092e73-ed1b-4826-92a9-b9c1e408761b" -BodyParameter @{
    guestSettings = @{
        allowCreateUpdateChannels = $false
        allowDeleteChannels       = $false
    }
}

How End Users & Team Owners Add a Guest to Microsoft Teams

Once tenant and per-Team policies permit guest invitations:

  1. Open the Microsoft Teams client, navigate to the target Team, click More options (...) next to the Team name, and select Manage team.
  2. On the Members tab, click Add member.
  3. Type the external partner's full email address (any business or consumer email address is supported via Entra B2B one-time passcode or federated login) and click Add.
  4. The guest receives an invitation email and is provisioned in Entra ID as user_domain.com#EXT#@tenant.onmicrosoft.com with externalUserState = PendingAcceptance until they redeem the invite.

Frequently Asked Questions (FAQ)

1. Does an external guest need a Microsoft 365 account to join our Team?

No. Earlier versions of Teams required guests to hold a work or school account, but modern Microsoft Entra B2B Collaboration supports any external email address. If the guest does not have an Entra ID or Microsoft account, Entra ID automatically authenticates them using Email One-Time Passcode (OTP).

2. Do we need additional Microsoft Teams licenses for Guests?

No. Microsoft Teams Guest Access is included with all Microsoft 365 Business Basic/Standard/Premium and Office 365 / Microsoft 365 E3/E5 subscriptions. For Microsoft Entra ID governance features (such as Conditional Access for guests or Access Reviews), Microsoft Entra External ID uses a Monthly Active Users (MAU) billing model where the first 50,000 MAU per month are free.

3. Why can't a Team Owner add a guest even though Guest Access is ON in the Teams Admin Center?

Check the following three places:
  • Entra External Collaboration Settings: Verify that Guest invite settings allow members to invite guests (or ensure the Team Owner holds the Guest Inviter directory role).
  • Per-Team Group.Unified.Guest Override or Sensitivity Label: Verify whether the Team has a sensitivity label applied that blocks external users, or check GET /beta/groups/{id}/settings for AllowToAddGuests = false.
  • Cross-Tenant Domain Restrictions: Verify that the guest's email domain is not blocked in Entra ID External Identities > Cross-tenant access settings.