Microsoft Teams: Information Barriers enforcement for same‑tenant users in external group chats

Microsoft Teams will enforce Information Barriers between same-tenant users in external group chats, calls, and meetings starting June 15, 2026. This ensures consistent compliance across all communication scenarios without requiring policy changes. Existing external conversations remain unchanged initially, with ongoing enforcement applied as policies or memberships change.

[What and Why]

Microsoft Teams is enhancing Information Barriers (IB) enforcement to provide consistent compliance protection across all communication scenarios, including external collaboration.

With this update, IB policies will be enforced between users within the same tenant even when they participate in external group chats, calls, or meetings. This improvement ensures that organizations with regulatory or compliance requirements can maintain policy enforcement regardless of how conversations are initiated or who else is included.

This feature strengthens enterprise-grade compliance and risk management while enabling safer external collaboration.

[Rollout Schedule]

General Availability (Worldwide):

• Rollout start: June 15, 2026
• Rollout completion: June 18, 2026

[Impact on Your Organization]

Who is affected

• Organizations that have Information Barriers configured
• Users in those organizations who participate in external chats, calls, or meetings

Platforms/Services

• Microsoft Teams (chat, group chat, meetings, and calls)
• Applies across desktop, web, and mobile clients

What will happen

Pre-existing external conversations are not retroactively modified at rollout.

• IB policies will be enforced between internal users in external conversations.
• This feature is enabled by default for tenants with IB policies configured.
• Existing IB configurations and policies are respected; no reconfiguration required.

New and updated behavior:

• Creating new external group chats or calls:
  • Teams will validate IB policies between internal participants.
  • Users who are not allowed to communicate will be excluded automatically.
• Adding participants to existing external conversations:
  • IB policies are validated before allowing the addition.
  • The action will be blocked if policies prevent communication.
• Existing external conversations at rollout:
  • External threads that already include non-compliant internal participants are not automatically changed at rollout.
  • Non-compliant participants will remain in those threads unless a re-evaluation occurs.
• Ongoing and conditional enforcement:
  • If IB policies or user segment membership changes, the conversation may be reprocessed.
  • At that time, users who are no longer allowed to communicate will be automatically removed.
  • Conversations will continue for compliant participants.

[Action Required/Recommendations]

No immediate action is required.

However, we recommend that administrators:

• Review your existing Information Barriers policies to understand potential impact on external collaboration scenarios.
• Inform helpdesk and support teams about:
  • Existing external chats may retain non-compliant participants initially
  • Changes in behavior when adding users to chats or meetings
  • Possible participant removal from existing conversations after rollout
• Communicate this update to users in regulated teams or roles that frequently collaborate externally.
• Update internal documentation if you describe external collaboration or IB enforcement scenarios.

Learn more: [To be updated closer to rollout.] Information Barriers in Microsoft Teams | Microsoft Purview | Microsoft Learn

[Compliance considerations]

Question	Answer
Does the change alter how existing customer data is processed, stored, or accessed?	Yes. IB policies are now applied in additional conversation contexts (external chats), changing how communication data is governed and access controlled.
Does the change provide a new way of communicating between users, tenants, or subscriptions?	Yes. It expands enforcement to external collaboration scenarios, affecting how users interact across tenant boundaries.
Does the change modify Purview capabilities (DLP, Information Protection, eDiscovery, etc.)?	Yes. This strengthens Information Barriers enforcement, a Purview compliance capability, by extending its scope without altering underlying policy configuration.