We’re updating the chart view, list view and filter options to clarify email delivery latency and latency due to detonation of the attachments / URLs (for those items that are subject to Safe Attachments and Safe Links policies). This message is associated with Microsoft 365 Roadmap ID 93213.
we are making some enhancements to the existing Mail latency report in Defender for Office 365. The chart and filter options will be updated for more clarity.
When this will happen
Table of Contents
We will begin rolling this out in mid-April and expect to complete rollout late May.
How this will affect your organization
The Mail latency report shows you an aggregate view of the mail delivery and detonation latency within your organization. As part of this enhancement, we’re updating the chart view, list view and filter options.
The existing report is represented in a stacked bar chart, with Mail delivery and Detonations on top of each other. The updated chart shows these values in a grouped bar chart with Mail delivery and Detonations values next to each other.
Note: We’ve changed the terminology from ‘Mail delivery’ latency to ‘Overall’ latency to better reflect the meaning.
The list view now shows a single row for all the percentiles (50th, 90th and 99th). Earlier each percentile was shown in a single row.
The existing report has the following filter options ‘All email’, ‘Messages that contain attachments or URLS’ and ‘Detonated email’.
These options are enhanced to give more clarity in the new report. The new options are ‘All email’ and ‘Detonated email’. The ‘Detonated email’ has two options: ‘Inline detonation’ and ‘Asynchronous detonation’. These options help show the impact on latency due to respective configurations of Safe Attachments and Safe Links policies.
What you need to do to prepare
You might want to update your documentation as appropriate.
- Mail latency report
- Asynchronous detonation in Safe Attachments policy settings (see Dynamic Delivery)
- Asynchronous detonation in Safe Links settings for email messages (see disable setting in ‘Wait for URL scanning to complete before delivering the message’)
Message ID: MC353490
Published: 05 April 2022
Updated: 05 April 2022