Back to latest version
Comparing Feb 14, 2024 latest (May 17, 2024) Swap

MC715687 - DLP: Adding matched attachment details in Activity Explorer for Data Loss Prevention rules in Exchange

Message Center

Metadata at latest

Last Updated

May 17, 2024

Published Feb 14, 2024

Service

Microsoft 365 suite

Tag

Updated message
New feature
Admin impact

Platforms

Web

Metadata changes

Title
Data Loss Prevention: Adding matched attachment details in Activity Explorer for Data Loss Prevention rules in ExchangeDLP: Adding matched attachment details in Activity Explorer for Data Loss Prevention rules in Exchange
Tags
Admin impact, New featureAdmin impact, New feature, Updated message
End date
Jun 30, 2024May 22, 2024

Body changes

removed textadded text

Updated May 17, 2024: We have determined that this is a duplicate message. Please disregard this message and refer to MC709981 moving forward. We apologize for the inconvenience.

We are adding new fields in Microsoft Exchange to help prevent data loss. With these updates, admins can see more details about the attachments that are present in the email that violated the Data Loss Prevention (DLP) rules, including name, size, and labels. There will be new fields for the attachments that are in emails when they match a DLP rule that will be displayed in Activity Explorer, DLP Alerts, and Microsoft Theft Protection (MTP) Alerts. With these updates, you can get better insights into the violation that has occurred even before you start getting into the finer details of the issue.

This message is associated with Microsoft 365 Roadmap ID 369015

[When this will happen:]

Standard Release: Rollout will begin in early March 2024 and is expected to be complete by late March 2024. 

[How this will affect your organization:]

You will see more details about the attachments that are present in emails when violations occur.

Activity Explorer



DLP Alerts


MTP Alerts



[What you need to do to prepare:]

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.