MC1162276 - Microsoft Teams: Trust Indicators – a new way of representing users outside your organization

Message Center

This announcement expired on Apr 13, 2026 and is no longer active in Message Center.

Summary

Microsoft Teams will introduce Trust Indicators—visual badges identifying external, guest, or anonymous users—to reduce oversharing risks. Public preview starts late September 2025; general rollout begins mid-February 2026. The feature is on by default, requires no admin action, and appears across multiple Teams surfaces.

Last Updated

Dec 11, 2025

Published Sep 29, 2025

View version history

Service

Microsoft Teams

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Android
Desktop
iOS
Mac

More information

Updated December 11, 2025: We have updated the timeline. Thank you for your patience.

Introduction:

To help users quickly identify external participants in Microsoft Teams and reduce the risk of oversharing sensitive information, we’re introducing Trust Indicators—visual labels (badges or icons) next to people’s names. These indicators signal whether someone is external to your organization, a guest, or an anonymous meeting participant.

This message is associated with Microsoft 365 Roadmap ID 515169.

When this will happen:

Public Preview: Begins rolling out late September 2025; expected completion by late November 2025.

General Availability (Worldwide, GCC, GCC High, DoD): Begins rolling out mid-February 2026 (previously mid-January); expected completion by early March 2026 (previously early February).

How this affects your organization:

Who is affected: All Microsoft Teams users across commercial, GCC, GCC High, and DoD environments.

What will happen:

  • Users will see badges or icons next to names of external participants in Teams:
  • user settings

    user settings

  • The visual indicator will vary depending on the relationship (guest, external, anonymous):
  • user settings

  • These indicators will appear across multiple Teams surfaces.
  • No admin action is required to enable this feature; it will be ON by default.

What you can do to prepare:

No action is required to enable the feature.

Admins can:

Compliance considerations:

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

Version history

5 versions tracked

Updated 4 times since Sep 29, 2025. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Dec 11, 2025 · 06:43 PMLatest · v5

    Changed: Body, End date

  2. Nov 19, 2025 · 05:59 PMv4

    Changed: Body, End date

  3. Nov 4, 2025 · 05:34 PMv3

    Changed: Body

  4. Sep 30, 2025 · 08:05 PMv2

    Changed: Title, Body, Tags

  5. Sep 29, 2025 · 11:05 PMOriginal · v1

    Changed: Initial version