DeltaPulse now has a public MCP server. Add / integrate this tool with your Copilot Agent(s).

MCP Documentation

(Updated) Microsoft Defender for Office 365: Admins can block external users in Microsoft Teams from Defender Portal

Message ID
MC1200058
View in Message Center
Services
Microsoft TeamsMicrosoft Defender XDR
Category
Stay Informed
Tags
New featureAdmin impact
Rollout
February 2026
Roadmap ID
542189
View in M365 Roadmap
Platform
Web

Summary

Starting mid-February 2026, admins can block external Microsoft Teams users via the Tenant Allow/Block List in the Microsoft Defender portal, controlling access and deleting existing communications. This applies to Teams and Defender XDR, with audit logging and limits of 4,000 domains and 200 emails blocked.

Details

Updated January 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing an integration between Microsoft Teams and Microsoft Defender for Office 365 that allows security admins to manage blocked external users in Teams through the Tenant Allow/Block List (TABL) in the Microsoft Defender portal. This centralized approach enhances security and compliance by enabling organizations to control external user access across Microsoft 365 services.

This message is associated with Roadmap ID 542189.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-February 2026 (previously early January) and is expected to complete by end of February 2026 (previously mid-January).

[How this affects your organization:]

Who is affected: Organizations using Microsoft Teams and Microsoft Defender for Office 365 Plan 1 or Plan 2.

What will happen:

  • Security admins (with Teams admin permission) can add, delete, and view blocked external users and domains for Teams in the Microsoft Defender portal.
  • Screenshot 1: Image showcasing the teams block sender and block domain list in Microsoft Teams

    user settings

  • Incoming communications (chats, channels, meetings, and calls) from blocked users will be prevented.
  • Existing communications from blocked users will be automatically deleted.
  • Audit logs will track actions taken to block users for compliance monitoring.
  • Entry limits: Up to 4,000 blocked domains and 200 email addresses can be configured for Teams.
  • This applies to all Teams clients and the Defender XDR web portal.
  • Existing federation configurations and domain blocks in the Teams admin center remain unaffected.

[What you can do to prepare:]

  • Enable the setting “Block specific users from communicating with people in my organization” in the Teams admin center (default: Off).
  • Screenshot 2:  Image showing the teams toggle for blocking sender email addresses in Microsoft Teams

    user settings

  • Enable the setting “Allow my security team to manage blocked domains and blocked users” in the Teams admin center (default: Off).
  • Grant security team access to manage blocked domains and users in the Teams admin center.
  • Review internal documentation and inform helpdesk staff about this change.
  • Learn more: Tenant Allow/Block List documentation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Change History

Show
January 24, 2026 at 4:31 AM Updated
Title
Previous
Microsoft Defender for Office 365: Admins can block external users in Microsoft Teams from Defender Portal
New
(Updated) Microsoft Defender for Office 365: Admins can block external users in Microsoft Teams from Defender Portal
Summary
Previous
Admins can now block external users in Microsoft Teams via the Tenant Allow/Block List in the Microsoft Defender portal, controlling access and communications. This feature, rolling out January 2026, supports up to 4,000 domains and 200 emails, with audit logging and no impact on existing Teams settings.
New
Starting mid-February 2026, admins can block external Microsoft Teams users via the Tenant Allow/Block List in the Microsoft Defender portal, controlling access and deleting existing communications. This applies to Teams and Defender XDR, with audit logging and limits of 4,000 domains and 200 emails blocked.
Last Updated Date
Previous
2025-12-19T07:08:18.120Z
New
2026-01-24T00:51:04.060Z
Tags
Previous
New feature,Admin impact
New
Updated message,New feature,Admin impact
Body Content
Previous

[Introduction]

We’re introducing an integration between Microsoft Teams and Microsoft Defender for Office 365 that allows security admins to manage blocked external users in Teams through the Tenant Allow/Block List (TABL) in the Microsoft Defender portal. This centralized approach enhances security and compliance by enabling organizations to control external user access across Microsoft 365 services.

This message is associated with Roadmap ID 542189.

[When this will happen:]

General Availability (Worldwide): Rollout begins early January 2026 and is expected to complete by mid-January 2026.

[How this affects your organization:]

Who is affected: Organizations using Microsoft Teams and Microsoft Defender for Office 365 Plan 1 or Plan 2.

What will happen:

  • Security admins (with Teams admin permission) can add, delete, and view blocked external users and domains for Teams in the Microsoft Defender portal.
  • Screenshot 1: Image showcasing the teams block sender and block domain list in Microsoft Teams

    user settings

  • Incoming communications (chats, channels, meetings, and calls) from blocked users will be prevented.
  • Existing communications from blocked users will be automatically deleted.
  • Audit logs will track actions taken to block users for compliance monitoring.
  • Entry limits: Up to 4,000 blocked domains and 200 email addresses can be configured for Teams.
  • This applies to all Teams clients and the Defender XDR web portal.
  • Existing federation configurations and domain blocks in the Teams admin center remain unaffected.

[What you can do to prepare:]

  • Enable the setting “Block specific users from communicating with people in my organization” in the Teams admin center (default: Off).
  • Screenshot 2:  Image showing the teams toggle for blocking sender email addresses in Microsoft Teams

    user settings

  • Enable the setting “Allow my security team to manage blocked domains and blocked users” in the Teams admin center (default: Off).
  • Grant security team access to manage blocked domains and users in the Teams admin center.
  • Review internal documentation and inform helpdesk staff about this change.
  • Learn more: Tenant Allow/Block List documentation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

New

Updated January 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing an integration between Microsoft Teams and Microsoft Defender for Office 365 that allows security admins to manage blocked external users in Teams through the Tenant Allow/Block List (TABL) in the Microsoft Defender portal. This centralized approach enhances security and compliance by enabling organizations to control external user access across Microsoft 365 services.

This message is associated with Roadmap ID 542189.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-February 2026 (previously early January) and is expected to complete by end of February 2026 (previously mid-January).

[How this affects your organization:]

Who is affected: Organizations using Microsoft Teams and Microsoft Defender for Office 365 Plan 1 or Plan 2.

What will happen:

  • Security admins (with Teams admin permission) can add, delete, and view blocked external users and domains for Teams in the Microsoft Defender portal.
  • Screenshot 1: Image showcasing the teams block sender and block domain list in Microsoft Teams

    user settings

  • Incoming communications (chats, channels, meetings, and calls) from blocked users will be prevented.
  • Existing communications from blocked users will be automatically deleted.
  • Audit logs will track actions taken to block users for compliance monitoring.
  • Entry limits: Up to 4,000 blocked domains and 200 email addresses can be configured for Teams.
  • This applies to all Teams clients and the Defender XDR web portal.
  • Existing federation configurations and domain blocks in the Teams admin center remain unaffected.

[What you can do to prepare:]

  • Enable the setting “Block specific users from communicating with people in my organization” in the Teams admin center (default: Off).
  • Screenshot 2:  Image showing the teams toggle for blocking sender email addresses in Microsoft Teams

    user settings

  • Enable the setting “Allow my security team to manage blocked domains and blocked users” in the Teams admin center (default: Off).
  • Grant security team access to manage blocked domains and users in the Teams admin center.
  • Review internal documentation and inform helpdesk staff about this change.
  • Learn more: Tenant Allow/Block List documentation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.