Public mode

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

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Office 365: Four override alerts retire in August 2024

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

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions we saw
  • Seen 30 Aug 2024 August 30, 2024 → September 15, 2024

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 August 28, 2024: We have updated the rollout timeline and content below. Thank you for your patience.

Microsoft Defender for Office 365 is retiring four legacy override alerts that are now mostly redundant due to Secure by default. With Secure by default, ZAP (zero-hour auto purge) blocks high confidence phishing emails by default despite the legacy overrides. The four alerts are:

  1. Phish not zapped because ZAP is disabled
  2. Malware not zapped because ZAP is disabled
  3. Phish delivered due to ETR override
  4. Phish delivered due to IP allow

As part of the deprecation and rollout,

  • These policies will no longer be part of the Alert policies in the Microsoft Defender portal.
  • Existing alerts that are already generated will be in the system (part of Alerts) until data retention applies.
  • Any features like AIR built on these policies will not function (return no data) but will not result in any crashes or issues to the system.
  • Any features like Investigations or post-breach functionalities will not have these alerts as part of the selection, filtering, or processing.

When is the change?

We plan to turn off these alerts starting August 18, 2024 and ending September 15, 2024.

Who is impacted?

  1. Phish not zapped because ZAP is disabled: E5/G5 or Microsoft Defender for Office 365 P2 add-on subscription
  2. Malware not zapped because ZAP is disabled: E5/G5 or Defender for Office 365 P2 add-on subscription
  3. Phish delivered due to ETR override: E1/F1/G1, E3/F3/G3, or E5/G5
  4. Phish delivered due to IP allow: E1/F1/G1, E3/F3/G3, or E5/G5

What should I do if I am impacted?

This change will happen automatically by the specified date. No admin action is required. Since these alerts are mostly redundant, we do not expect any impact. Defender XDR Customers using Defender for O365 as a secondary filter (MX record pointed to 3rd party service) and still want the alerts can create a custom detection rule on EmailEvents table with filters on OrgLevelAction & OrgLevelPolicy.

What changed

Between archive captures, newest first
    • Tags User impact, Admin impact, Retirement → Updated message, User impact, Admin impact, Retirement

    Updated August 28, 2024: We have updated the rollout timeline and content below. Thank you for your patience. Microsoft Defender for Office 365 is retiring four legacy override alerts that … plan to turn off these alerts starting August 18, 2024 and ending August 30,September 15, 2024. Who is impacted? Phish not zapped because ZAP is disabled: E5/G5 … Since these alerts are mostly redundant, we do not expect any impact. Defender XDR Customers using Defender for O365 as a secondary filter (MX record pointed to 3rd party service) and still want the alerts can create a custom detection rule on EmailEvents table with filters on OrgLevelAction & OrgLevelPolicy.

  1. · first version seen

Learn more

Links from the notice and their documentation checks

No related announcements were found in the saved public history. Check the source for newer announcements.

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 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current