Microsoft Defender for Office 365: Third-party add-in user report can be sent to Microsoft for analysis
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 406167
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 24 Mar 2025
late February 2025, early March 2025→ late March 2025, early April 2025 - Seen 24 Feb 2025
mid-May 2025, late May 2025→ late February 2025, early March 2025 - Seen 23 Jan 2025
early February 2025, mid-February 2025→ mid-May 2025, late May 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, safely structuredUpdated March 24, 2025: We have updated the rollout timeline below. Thank you for your patience.
Administrators and security operators who are using third-party report message solutions in Microsoft Outlook to allow their users to report suspicious messages (for example, Knowbe4, Hoxhunt, Cofense, Proofpoint add-ins, and so on) can now configure Defender for Office 365 to automatically send these messages to Microsoft for analysis.
This message is associated with Microsoft 365 Roadmap ID 406167.
When this will happen
General Availability: We will begin rolling out late March 2025 (previously late February) and expect to complete by early April 2025 (previously late March).
How this will affect your organization
You must configure this setting if you want the benefit of sending third-party reported messages to Microsoft.
To enable this setting:
- Go to User reported settings in the Microsoft Defender portal, select Monitor reported messages in Outlook, and then select Use a non-Microsoft add-in button.
- In the Reported message destination section, select Microsoft and my reporting mailbox, and then provide the email address of the internal Exchange Online mailbox where user-reported messages by the third-party add-ins are being routed to. If the third-party vendor follows the guidance for message submissions format, Defender for Office 365 will submit these messages automatically to Microsoft for analysis.
- The result from Microsoft after analysis is shown on the User reported page in the Defender portal.
For more details about how Microsoft handles user-reported suspicious messages, see Report suspicious email messages to Microsoft.
Alerts are automatically generated for user reported messages in Defender for Office 365. If you have Defender for Office 365 Plan 2, Automated investigation and response (AIR) is also automatically triggered for user reported phishing messages. Both alerts and their investigations are automatically correlated to Defender XDR Incidents, which helps SOC teams with automation to triage, investigate, and respond. Submitting these messages to Microsoft for analysis provides a response of this analysis to security analysts and also helps improve Defender for Office 365 filters.
What you need to do to prepare
If your user reporting settings are already set to Use a non-Microsoft add-in button and Microsoft and my reporting mailbox, you don't need to do anything to benefit from this change. However, if the destination is My reporting mailbox only, you need to change the destination to Microsoft and my reporting mailbox to benefit from this change.
What changed
Between archive captures, newest firstUpdated
FebruaryMarch 24, 2025: We have updated the rollout timeline below. Thank you for … When this will happen: General Availability: We will begin rolling out lateFebruaryMarch 2025 (previouslymid-May)late February) and expect to complete by earlyMarchApril 2025 (previously lateMay).March). How this will affect your organization: You must configure this setting if …Updated
January 23,February 24, 2025: We have updated thecontent.rollout timeline below. Thank you for your patience. Administrators and security operators who are using … 406167. When this will happen: General Availability: We will begin rolling outmid-Maylate February 2025 (previouslyearly February)mid-May) and expect to complete bylate Mayearly March 2025 (previouslymid-February).late May). How this will affect your organization: You must configure this setting if …- Tags
New feature, User impact, Admin impact→ Updated message, New feature, User impact, Admin impact
Updated January 23, 2025: We have updated the content. Thank you for your patience. Administrators and security operators who are using third-party report message solutions in … 406167. When this will happen: General Availability: We will begin rolling out mid-May 2025 (previously early
February 2025February) and expect to complete bymid-February 2025.late May 2025 (previously mid-February). How this will affect your organization: You must configure this setting if …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checks- 406167
- User reported settings
- follows the guidanceNot read yet
- result from MicrosoftNot read yet
- User reported page
- Report suspicious email messages to MicrosoftNot read yet
- AlertsNot read yet
- Automated investigation and response (AIR)Not read yet
- Notice image
Related public changes
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.
- 5 linked pages have not been read yet.