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: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 18:49 UTC Customize Public modeDiscuss ChangeIntel on Discord

Mail Bombing Detection technology in Microsoft Defender for Office 365

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

Rollout

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 1 Jul 2025 late July 2025 → early July 2025

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, with source markup removed
Updated July 1, 2025: We have updated the timeline below. Thank you for your patience. We’re introducing a new detection capability in Microsoft Defender for Office 365 to help protect your organization from a growing threat known as email bombing. This form of abuse floods mailboxes with high volumes of email to obscure important messages or overwhelm systems. The new “Mail Bombing” detection will automatically identify and block these attacks, helping security teams maintain visibility into real threats. When this will happen: General Availability (Worldwide): We will begin rolling out in late June 2025 and expect to complete by early July 2025 (previously late July). How this affects your organization: Security Operations Analysts and Administrators will see a new detection type labeled Mail Bombing in the following locations: Threat Explorer Email entity view Email Summary Panel Advanced Hunting Messages identified as part of a mail bombing campaign will be automatically sent to the Junk folder. Safe Senders settings will continue to be honored—messages from those senders will not be impacted. This feature is on by default and requires no manual configuration. What you can do to prepare: Inform your Security Operations team about this new detection. Update internal documentation and training materials as needed. Review Junk folder handling policies to ensure alignment with your organization’s expectations. Compliance considerations: Alters processing/storage of existing data Yes – modifies how email messages are classified and routed Introduces/modifies AI/ML capabilities Yes – introduces new detection logic Impacts Purview capabilities Maybe – may affect audit logging or eDiscovery visibility for junked messages Alters compliance monitoring/reporting Maybe – new detection may appear in compliance dashboards

What changed

Between archive captures, newest first
    • Tags New feature, Admin impact → Updated message, New feature, Admin impact

    Updated July 1, 2025: We have updated the timeline below. Thank you for your patience. We’re introducing a new detection capability in Microsoft Defender for Office 365 … begin rolling out in late June 2025 and expect to complete by lateearly July 2025.2025 (previously late July). How this affects your organization: Security Operations Analysts and Administrators will see …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

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

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.
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 26 Oct 18:49 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current