Public mode

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

Some sources or documents need attention: 258/260 feeds/APIs · 417/444 docs · checked 17:18 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Office 365: Remediation actions from the Teams message entity flyout

Rollout

Ends
12 Nov 2026

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

What the notice says

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

What and why

We are enhancing the Teams message entity flyout in Microsoft Defender for Office 365 to help security teams investigate and remediate malicious Teams messages more efficiently. Administrators will be able to submit messages to Microsoft and block external senders or associated domains from a single workflow, reducing the need to navigate between investigation experiences.

Rollout schedule

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

Impact on your organization

Who is affected

  • Security administrators and analysts in organizations with Microsoft Defender for Office 365 Plan 1 or Plan 2 who investigate Teams messages through Submissions, Alerts, Advanced Hunting, or Quarantine

Platforms and services

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

What will happen

Administrators investigating Teams messages through Submissions, Alerts, Advanced Hunting, or Quarantine will be able to open the Teams message entity flyout and access the Take action workflow directly from the message.

The updated action wizard will support the following actions:

  • Submit to Microsoft: Submit the Teams message to Microsoft for review and analysis:
  • Block sender: Add the external sender to the Tenant Allow/Block List (TABL). When available, sender information will be prepopulated to reduce manual entry.
  • Block domain: Add one or more domains associated with the investigated message to TABL. The wizard will identify and prepopulate domains associated with an external sender, allowing administrators to select the domains to block.

Administrators can perform multiple actions in a single workflow. For example, they can submit a message to Microsoft while also blocking the associated sender or domain.

These actions will be available to Microsoft Defender for Office 365 Plan 1 and Plan 2 customers. Existing investigation experiences and workflows will remain available. No configuration changes are required for this capability.

Action required and recommendations

No action is required before rollout.

We recommend that organizations:

  • Review internal security operations procedures for Teams message investigations.
  • Update administrator training materials and documentation to include the new remediation actions available from the Teams message entity flyout.
  • Inform security operations teams about the streamlined investigation and remediation workflow.

Learn more

Compliance considerations

No compliance considerations were identified in the source content. Review this change as appropriate for your organization.

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

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

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 17:18 UTC · 258 of 260 readable · 256 fully read · documentation 417/444 current