Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 467/469 docs · 7/9 advisories · checked 11:16 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Office 365: Enable users to report suspicious Teams messages in Plan 1

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
531760

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 13 Feb 2026 mid-March 2026, late March 2026 → late February 2026, end of February 2026
  • Seen 9 Feb 2026 mid-February 2026 → mid-March 2026, late March 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 structured

Updated February 13, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We’re expanding the ability for users to report suspicious Microsoft Teams messages to customers with Microsoft Defender for Office 365 Plan 1. Previously available only to Plan 2, this update helps security teams identify and investigate potential phishing, malware, and spam across internal and external Teams chats, channels, and meeting chats. This enhancement strengthens protection by incorporating user-reported signals into existing Defender detections.

Users will be able to report messages in two ways:

  • Report as security risk — for messages suspected to contain phishing, malware, or other malicious content.
  • Report as not a security risk — for messages that were incorrectly identified as threats (false positives).

This message is associated with Microsoft 365 Roadmap ID 531760.

When this will happen

General Availability (Worldwide): Rollout begins in late February 2026 (previously mid-March) and is expected to complete by end of February 2026 (previously late March).

How this affects your organization

Who is affected:

  • Microsoft 365 tenants using Microsoft Defender for Office 365 Plan 1
  • Users across Microsoft Teams
  • Security admins reviewing reported messages

What will happen:

  • Users will see options to report messages as security risks or not security risks.
  • Reports will appear on the User reported page in the Defender portal and/or your configured mailbox.
  • This feature is opt-in and respects your existing User reported settings.
  • Teams admin center toggles for reporting will be automatically enabled when User reported settings are turned on.

What you can do to prepare

  • Enable and configure User reported settings in the Defender portal.
  • Review message reported destination preferences for reported messages.
  • Communicate reporting guidance to users.
  • Review supporting documentation.
  • Update internal documentation as needed.

Learn more:

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

What changed

Between archive captures, newest first
  1. Updated February 9,13, 2026: We have updated the timeline. Thank you for your patience.  Introduction … ID 531760. When this will happen General Availability (Worldwide): Rollout begins in mid-Marchlate February 2026 (previously mid-February)  mid-March) and is expected to complete in late Marchby end of February 2026 (previously mid-February). late March). How this affects your organization Who is affected: Microsoft 365 tenants using …

    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated February 9, 2026: We have updated the timeline. Thank you for your patience.  Introduction We’re expanding the ability for users to report suspicious Microsoft Teams … ID 531760. When this will happen General Availability (Worldwide): Rollout begins in mid-February mid-March 2026 (previously mid-February) and is expected to complete in mid-February 2026. late March 2026 (previously mid-February). How this affects your organization Who is affected: Microsoft 365 tenants using …

  2. · first version seen

Learn more

Links from the notice and their documentation checks

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.
  • 2 linked pages have not been read yet.
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 27 Oct 11:16 UTC · 271 of 272 readable · 270 fully read · documentation 467/469 current