Data Protection Issues

How to Populate DetectedValuesForSITS in Microsoft Purview DLP Alerts

Maira MehtabMaira Mehtab Oct 28, 2026 869 views

Question details

The user needs to populate the DetectedValuesForSITS field in Microsoft Purview Data Loss Prevention (DLP) alerts, which is currently empty despite metadata showing policy and rule matches.

How to Populate DetectedValuesForSITS in Microsoft Purview DLP Alerts
Product
Microsoft Purview
Device & OS
not provided
Scenario
Reviewing DLP alerts and attempting to view the specific sensitive content that triggered the policy match.
Observed behavior
The DetectedValuesForSITS field returns empty because the viewing account lacks the necessary permissions to access matched sensitive content.
Before you start

Ensure you have global administrator or compliance administrator rights in your Microsoft 365 tenant to assign the necessary roles and API permissions.

Solution 1Recommended

Assign the Content Explorer Content Viewer Role

Grant the least-privileged role required to view the actual sensitive content that triggered the DLP alert.

By default, administrators cannot see the actual sensitive data (such as credit card numbers or SSNs) that caused a DLP policy violation. To populate fields like DetectedValuesForSITS, the account accessing the alerts must be explicitly granted permission to view matched sensitive content.

1
Access the Microsoft Purview compliance portal

Log in to the Microsoft Purview compliance portal using your administrative credentials.

2
Navigate to Roles & scopes

In the left navigation pane, expand the 'Permissions' section and select 'Roles'.

3
Assign the Content Viewer role

Search for the 'Content Explorer Content Viewer' role group. Edit the role group and add your user account (or the designated security group) as a member.

4
Allow time for replication

Save the changes. It may take some time for the permissions to propagate across the tenant before the DetectedValuesForSITS field begins populating in new alerts.

Assign the Content Explorer Content Viewer Role
Permission Scope: The Content Explorer Content Viewer role is highly privileged as it exposes plain-text sensitive information. Assign this role only to authorized compliance officers.
Free Microsoft Office alternative

Secure and Manage Your Everyday Documents with WPS Office

While managing enterprise-level Data Loss Prevention (DLP) alerts requires Microsoft Purview, WPS Office provides a free, highly compatible, and secure alternative for your daily document creation and local data protection needs. Enjoy seamless format compatibility without the heavy overhead.

  1. 1. Visit the WPS Website: Go to the official WPS Office website.
  2. 2. Download the Installer: Click the 'Free Download' button to get the latest version for your operating system.
  3. 3. Install and Secure Documents: Run the installer, launch WPS Office, and start creating password-protected documents instantly.
Fully compatible with Microsoft Office formats (Word, Excel, PowerPoint)Built-in document encryption and password protection featuresFree and lightweight alternative to heavy enterprise productivity suitesFamiliar user interface for quick and seamless migration
microsoft office alternative - wps office

Frequently Asked Questions

What does the DetectedValuesForSITS field represent in DLP alerts?

It represents an array of names and the actual text values of the offending data that triggered a Sensitive Information Type (SIT) match in your DLP policy.

Why is the DetectedValuesForSITS field empty even when rules match?

This field remains empty if the viewing account or API application has not been granted the specific permissions required to view plain-text sensitive content, such as the Content Explorer Content Viewer role.

Is 'Read DLP sensitive data' an Azure role or an API permission?

It is an API permission used when making calls to Microsoft Graph or related compliance APIs, rather than a standard Azure AD user role.