Microsoft Defender for Office 365
Email and collaboration

Mdo Integrate Security Service

In brief

The guidance now states that malware and high-confidence phishing messages quarantined when MX points to Microsoft 365 cannot bypass their verdict when released.

What Defender admins need to know

Resolve the verdict before releasing these messages from quarantine.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Mail flow rules (transport rules) that look at original verdicts aren't ideal, because they can introduce other issues and lead to effectiveness challenges.
  1. When your MX record points to Microsoft 365, messages quarantined as malware or high confidence phishing (HPHISH) are protected by secure by default behavior. Resolve the malware or HPHISH verdict before you release the message from quarantine, because these verdicts can't be bypassed when the message returns from a non-Microsoft service. For more information, see Secure by default in Office 365.

  2. Minimize false positives by overriding spoof for email arriving from the non-Microsoft service. For example, if the non-Microsoft service has an IP address of 172.17.17.35, create two allowed spoofed sender entries in the Tenant Allow/Block List: one External and one Internal as shown in the following screenshot:

    A screenshot of the allowed spoofed sender entries in the Tenant Allow/Block List.

    Be sure to remove these override entries if you ever leave the non-Microsoft protection service or change how it functions.

  3. False negative (bad mail allowed) and false positive email submissions to Microsoft should come from the initial version of the message, not the one that returns from the non-Microsoft service. False positives attributed to the non-Microsoft service should be sent to the non-Microsoft service. This requirement can be complex to manage:

    • Microsoft false negative (missed at initial reception): You need a copy of the message before to delivery to the mailbox. Submit the copy in quarantine from the non-Microsoft service, if it's available.
    • Microsoft + non-Microsoft service false negative: If both services miss it, we recommend reporting the original item to Microsoft and reporting the item in the recipient's mailbox to the non-Microsoft service. The item returned to Microsoft 365 from the non-Microsoft service includes details from the non-Microsoft service (for example, the non-Microsoft service's sending IP addresses, custom headers, etc.) which can lead to decreased machine learning effectiveness.