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: User submission automatic feedback response

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

Rollout

Roadmap
186575

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

In Microsoft Defender for Office 365 (MDO), the user submission automatic feedback response enables organizations to automatically respond to end user submissions of phish based on the verdict from the automated investigation and response (AIR) investigation. This feature is configurable and allows organizations to dictate which threat scenarios they would like end users to receive feedback emails about. Once enabled, Microsoft Defender for Office 365 will automatically respond to end user submissions based on the investigation verdict and the configured settings.

This message is associated with Microsoft 365 Roadmap ID 186575

When this will happen

Worldwide, GCC: Rollout completed in late February 2024.

How this will affect your organization

Customers will have the ability to automatically respond to end user reports of phish based on the verdict of the AIR investigation.

The feature may be configured in Settings > Email & collaboration > User reported settings within the Email notifications > Results email section. On this page, the first step to enabling this feature is to check the box to Automatically email users the results of the investigation. Includes results for reported messages from all monitored platforms. Upon making this selection, three additional checkboxes will appear titled Phishing or Malware, and No threats found. These three checkboxes represent the options for the user submission automatic feedback response and allow organizations to dictate which threat scenarios they would like end users to receive feedback emails about. At least one of these options should be selected to enable this feature.

  • Phishing or Malware: Selecting this box indicates that the organization would like end users to receive an automatic response email on email submissions of phish when the associated user submission investigation identifies a threat of normal phish, high confidence phish, or malware.
  • Spam: Selecting this box indicates that the organization would like end users to receive an automatic response email on email submissions of phish when the associated user submission investigation shows the threat of spam.
  • No threats found: Selecting this box indicates that the organization would like end users to receive an automatic response email on email submissions of phish when the associated user submission investigation finds no threats.

Responses to end users will be sent at the conclusion of the automated investigation based on the verdict, if configured.

What you need to do to prepare

Customers may further familiarize themselves with the new feature by reviewing the learn document Automatic user notifications for user reported phishing results in AIR | Microsoft Learn that contains additional details. To learn more about automated investigation and response (AIR) in Microsoft Defender for Office 365 visit Automated investigation and response in Microsoft Defender for Office 365 - Office 365 | Microsoft Learn.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

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