Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 13:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Office 365: Teams user reporting enabled by default

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Rollout

Ends
30 Nov 2026

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Microsoft's start date
24 Sep 2026
Last changed by Microsoft
25 Sep 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and why

To help organizations identify and respond to security threats in Microsoft Teams, Microsoft Defender for Office 365 will enable Teams user reporting by default. Users can report suspicious messages, calls, and meetings, helping organizations improve detection of phishing, spam, impersonation, malicious content, and other threats.

This capability is available for organizations licensed for Microsoft Defender for Office 365 Plan 1 or Plan 2, Microsoft 365 E5, or Office 365 E5.

Rollout schedule

  • General Availability (Worldwide): Beginning in late October 2026 and expected to complete by late October 2026

Impact on your organization

Who is affected

  • Organizations licensed for Microsoft Defender for Office 365 Plan 1 or Plan 2, Microsoft 365 E5, or Office 365 E5
  • Microsoft Teams and security administrators
  • Teams users in affected organizations

Platforms/Services

  • Microsoft Teams
  • Microsoft Defender portal
  • Microsoft Defender for Office 365

What will happen

  • Users can report suspicious messages, calls, and meetings directly from Teams. Reported content is submitted per your configured reported destination for security analysis.
  • Security risk items can include phishing, spam, impersonation, malicious content, and phishing URLs.
  • Beginning October 7, 2026, Teams user-reported settings will be managed on a dedicated page in the Microsoft Defender portal.
  • If you have already configured Teams user-reported settings, your existing settings will be carried over. Changes made after migration may not be reflected until the week of October 15, 2026.
  • If you have not already configured Teams user-reported settings, Teams user reporting will be enabled by default beginning October 25, 2026, unless you opt out.

Image 1 - Teams user reported settings view:

Image 2 - Email user reported settings view:

Action required/Recommendations

Review your Teams user-reported settings before October 25, 2026, if you do not want Teams user reporting enabled by default or want reported content sent to a destination other than Microsoft.

Recommended actions:

  • Review Teams user-reported settings in the Microsoft Defender portal.
  • Decide whether user-reported Teams content should be submitted to Microsoft for security analysis.
  • Opt out before October 25, 2026, if desired.
  • Inform security administrators and help desk staff about this change.

Learn More

Compliance considerations

QuestionAnswer
Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Teams user-reported settings will move to a dedicated configuration page in the Defender portal.
Does the change include an admin control, and can it be controlled through Entra ID group membership?Administrators can opt out by configuring Teams user-reported settings in the Defender portal. Group-based controls are not specified.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

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.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 13:25 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current