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: Reported mailbox notifications messages subject change

From 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 we saw
  • Seen 6 Jun 2024 late May 2024 → mid-July 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 June 6, 2024: We have updated the rollout timeline below. Thank you for your patience.

Currently, in Microsoft Defender for Office 365, when a notification message is reported by an end user and arrives at the reporting mailbox, the subject lines begin with:

  • "1|" to denote email messages reported as junk.
  • "2|" to denote email messages reported as not junk.
  • "3|" to denote email messages reported as phishing.

Moving forward, the subject lines of notification messages reported by end users will start with

  • "Junk:" to denote email messages reported as junk.
  • "Not junk:" to denote email messages reported as not junk.
  • "Phishing:" to denote email messages reported as phishing.

This change is being made to ensure readability and enable you to create better rules inside your reporting mailbox.

The subject line for the team's end-user reported notification messages will remain the same, continuing to start with "Security risk:"

When will this happen

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-June 2024 (previously late May) and expect to complete mid-July 2024 (previously mid-June).

How this will affect your organization

After the rollout is complete, notification messages reported by end users will be affected. However, notification messages reported by end users prior to the rollout will remain unchanged.

What you need to do to prepare

No action is required on your part. There won't be any change to your existing user reported settings.

What changed

Between archive captures, newest first
    • Tags Feature update, Admin impact → Updated message, Feature update, Admin impact

    Updated June 6, 2024: We have updated the rollout timeline below. Thank you for your patience. Currently, in Microsoft Defender for Office 365, when a notification message is … General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-June 2024 (previously late May 2024 May) and expect to complete mid-June 2024.mid-July 2024 (previously mid-June). How this will affect your organization: After the rollout is complete, notification …

  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 12:11 UTC · 256 of 275 readable · 252 fully read · documentation 469/469 current