Microsoft Defender for Office 365: Admins can block external users in Microsoft Teams from Defender Portal
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 542189
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 24 Jan 2026
early January 2026, mid-January 2026→ mid-February 2026, end of February 2026
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated 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.
- 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).
- 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.
What changed
Between archive captures, newest first- Tags
New feature, Admin impact→ Updated message, New feature, Admin impact
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 … Roadmap ID 542189. When this will happen: General Availability (Worldwide): Rollout begins mid-February 2026 (previously early
January 2026January) and is expected to complete bymid-January 2026.end of February 2026 (previously mid-January). How this affects your organization: Who is affected: Organizations using Microsoft Teams …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checks- 542189
- Tenant Allow/Block List documentationNot read yet
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 1 linked page has not been read yet.