Microsoft Teams: Detect sensitive content shared in meetings

Microsoft Teams Premium will introduce a feature called "Detect sensitive content" during screen sharing, which will be enabled by default at the tenant level. Admins can disable it, and meeting organizers must enable it per meeting. Rollout starts in May 2025, requiring a Teams Premium license.

Coming soon to Microsoft Teams Premium: A new tenant-level feature called Detect sensitive content during screen sharing that will be on by default to proactively analyze onscreen content and alert meeting organizers, co-organizers, and presenter to any risk of exposure. This feature helps you build a shield of trust and security around your organization. When this feature is on at the tenant level, meeting organizers and co-organizers will still need to enable the feature at the meeting level. Admins can disable the feature at the tenant level if desired.

This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android.

A Teams Premium license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 487433.

[When this will happen:]

Targeted Release: We will begin rolling out early May 2025 and expect to complete by late June 2025.

General Availability (Worldwide): We will begin rolling out late June 2025 and expect to complete by late July 2025.

[How this will affect your organization:]

After this rollout, admins can find the Detect sensitive content during screen sharing toggle in the On position for the tenant in the Teams admin center > Meeting policies > Content protection:

A meeting organizer or co-organizer will need to turn on the feature in Teams for a scheduled meeting in Meeting options > Advanced protection > Detect sensitive content during screen sharing:

i

When an organizer or co-organizer has enabled Detect sensitive content during screen sharing, Teams will detect and notify the meeting organizers, co-organizers, and presenter if the presenter is sharing sensitive information (such as bank information, credit card numbers, and so on) on the screen:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.