Skip to Content

MC360646: Exchange Online Protection: Anti-malware policy notification settings change

Updated June 14, 2022: We have updated this message to ensure visibility for affected organizations. Thank you for your patience.

Updated June 1, 2022: We have updated this message to ensure visibility for affected organizations. Thank you for your patience.

Updated May 17, 2022: We have updated the rollout timeline below. Thank you for your patience.

The previous Message Center post MC303513 (Dec ’21) mentioned that we’re planning to retire the recipient and sender notification configuration in anti-malware policies. After reviewing customer feedback, we’re changing how we’re planning to retire those recipient and sender notifications. This message is associated with Microsoft 365 Roadmap ID 93212.

The anti-malware policy can be configured with recipient and sender notifications when a message is quarantined. We are redesigning this notifications option and delivery.

MC360646: Exchange Online Protection: Anti-malware policy notification settings change

The current notification settings are commonly used for messages that are blocked/quarantined as detected malware, or due to a file attachment in the common attachment filter settings.

As part of this change, we’re separating out the handling of notifications based on whether the message was scanned and found to be malicious vs. matches from the common attachment filter:

  • True malware: Both recipient and sender notifications will be retired. The message will be quarantined, and the selected quarantine policy configuration determines whether to send the end-user notifications. There is no option for sender notification.
  • Common attachment filter: Notifications are split into two distinct options that the admin can choose (one or the other): Recipient notifications only: As with true malware detections, the selected quarantine policy configuration determines whether to send end-user notifications. There is no option for sender notifications.
  • Non delivery report (also known as NDR or bounce message)) to sender: The message is rejected in an NDR to the sender. The message is not quarantined, is not recoverable, and there’s no option for recipient notifications.

Effected Workload

  • Exchange Online
  • Microsoft 365 Defender

When this will happen

Starting late June (previously early June) and completion of deployment by late July (previously late June)

How this will affect your organization

Once these changes are rolled out, the current email notifications for recipients and senders will be stopped. Instead, any recipient notifications will be based on the selected quarantine policy (dropdown in the anti-malware policy).

What you need to do to prepare

Review the ‘Quarantine Policy’ selection in your current anti-malware policies. With this feature change, for default and all existing policies,

  • The selection in the ‘Quarantine Policy’ dropdown will be used for any recipient notifications.
  • For the new settings in ‘Common attachment filter detections’, the selection will be set to ‘Quarantine the message’ option (which is the same as the Quarantine policy dropdown).

Review the following resources below to learn more:

Message ID: MC360646
Published: 18 April 2022
Updated: 14 June 2022

Alex Lim is a certified IT Technical Support Architect with over 15 years of experience in designing, implementing, and troubleshooting complex IT systems and networks. He has worked for leading IT companies, such as Microsoft, IBM, and Cisco, providing technical support and solutions to clients across various industries and sectors. Alex has a bachelor’s degree in computer science from the National University of Singapore and a master’s degree in information security from the Massachusetts Institute of Technology. He is also the author of several best-selling books on IT technical support, such as The IT Technical Support Handbook and Troubleshooting IT Systems and Networks. Alex lives in Bandar, Johore, Malaysia with his wife and two chilrdren. You can reach him at [email protected] or follow him on Website | Twitter | Facebook

    Ads Blocker Image Powered by Code Help Pro

    Your Support Matters...

    We run an independent site that is committed to delivering valuable content, but it comes with its challenges. Many of our readers use ad blockers, causing our advertising revenue to decline. Unlike some websites, we have not implemented paywalls to restrict access. Your support can make a significant difference. If you find this website useful and choose to support us, it would greatly secure our future. We appreciate your help. If you are currently using an ad blocker, please consider disabling it for our site. Thank you for your understanding and support.