check before: 2024-05-18
Product:
Defender, Defender for Office 365, Defender XDR, Exchange
Platform:
Online, US Instances, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message
Links:
Details:
Summary:
Microsoft Defender for Office 365 is changing the subject line format for end-user reported notification messages to improve readability and rule creation. The rollout starts mid-June 2024 and ends mid-July 2024. No action is required from users as existing settings remain unaffected.
Details:
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).
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2024-05-04
updated:
2024-06-07
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
Direct effects for Operations**
- Direct Impact on IT Operations
- Change in subject line format for reported mailbox notifications may require updates to existing automated processes or scripts that rely on the previous subject line format.
- Roles impacted: IT Operations Team, Automation Engineers
- Potential increase in user inquiries or support tickets related to confusion over the new subject line format, leading to additional workload for IT support staff.
- Roles impacted: IT Support Team, Help Desk Staff
- Monitoring and reporting tools may need adjustments to accommodate the new subject line format for accurate data analysis and reporting.
- Roles impacted: IT Operations Analysts, Data Analysts
- Direct Impact on IT Services
- The change may affect email filtering rules set up by administrators, requiring them to review and possibly update these rules to ensure they function correctly with the new subject line format.
- Roles impacted: IT Administrators, Email System Administrators
- Integration with third-party security tools that analyze email subject lines may be disrupted, necessitating coordination with vendors for updates.
- Roles impacted: IT Security Team, Vendor Management Team
- The change could impact user training materials and documentation, requiring updates to ensure users understand the new format.
- Roles impacted: Training and Development Team, IT Documentation Specialists
- Direct Impact on IT Users
- Users may initially experience confusion regarding the new subject line format, leading to misinterpretation of reported messages and potential delays in addressing security issues.
- Roles impacted: End Users, Employees
- Users may need to adapt to the new subject line format when creating rules in their email clients, which could lead to temporary disruptions in their workflow.
- Roles impacted: End Users, Employees
- Increased communication from IT regarding the change may be necessary to ensure users are informed and prepared, potentially leading to information overload.
- Roles impacted: IT Communications Team, Change Management Team
References:
- Microsoft Defender for Office 365 documentation: [Microsoft Docs](https://learn.microsoft.com/defender-office-365/submissions-user-reported-messages-custom-mailbox)
- Microsoft Security settings: [Microsoft Security](https://security.microsoft.com/securitysettings/userSubmission)
- Outlook rules setup: [Microsoft Support](https://support.microsoft.com/office/set-up-rules-in-outlook-75ab719a-2ce8-49a7-a214-6d62b67cbd41)
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
** AI generated content. This information is not reliable.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2024-06-07 | MC Messages | 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 late May 2024 and expect to complete mid-June 2024. | 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). |
| 2024-06-07 | MC Title | Microsoft Defender for Office 365: Reported mailbox notifications messages subject change | (Updated) Microsoft Defender for Office 365: Reported mailbox notifications messages subject change |
| 2024-06-07 | MC Last Updated | 05/04/2024 06:06:53 | 2024-06-06T22:54:54Z |
| 2024-06-07 | MC MessageTagNames | Feature update, Admin impact | Updated message, Feature update, Admin impact |
| 2024-06-07 | MC Summary | Microsoft Defender for Office 365 is changing the subject line format for end-user reported notification messages to improve readability and rule creation. The rollout starts late May 2024 and ends mid-June 2024. No action is required from users as existing settings remain unaffected. | Microsoft Defender for Office 365 is changing the subject line format for end-user reported notification messages to improve readability and rule creation. The rollout starts mid-June 2024 and ends mid-July 2024. No action is required from users as existing settings remain unaffected. |
Last updated 3 months ago
