Compliance Problems

Microsoft 365 DLP: Content Contains vs. Document Property Is

Muhammad TalhaMuhammad Talha Nov 14, 2026 868 views

Question details

Understand why SharePoint DLP conditions based on sensitive content and document properties may be detected at different times.

Microsoft 365 DLP: Content Contains vs. Document Property Is
Product
Microsoft 365 Data Loss Prevention and SharePoint Online
Device & OS
not provided
Scenario
A user compares a DLP policy that detects sensitive information in a document with one that checks a mapped document property, such as an AIP label property.
Observed behavior
A content-based condition may be evaluated during sharing, while a property-based condition may be detected later after SharePoint crawls and indexes the property.
Before you start

Use an approved test site, a test document, and test sharing accounts rather than real sensitive data. Check that you have permission to view the DLP policy in Microsoft Purview and the SharePoint search schema.

Solution 1Recommended

Check property mapping and allow time for SharePoint indexing

Use this approach when a document-property DLP condition is detected later than a content-based condition.

Content-based conditions can be evaluated during sharing. Conditions that rely on document properties may depend on SharePoint crawling, the crawled-to-managed property mapping, and indexing, so detection can occur later.

The timing and enforcement behavior depend on the policy configuration and available property support. Do not assume that a delayed alert means sharing was blocked.

1
Review the DLP rule

In the Microsoft Purview portal, open Data loss prevention > Policies, select the policy, and review its SharePoint location, document-property condition, actions, and enforcement mode.

2
Inspect the search schema

In SharePoint site settings, open Search Schema and find the managed property used for the condition. Check its mapping to the relevant crawled property and confirm that the managed property has the attributes required for your policy, including being searchable where applicable.

3
Allow indexing to complete

After correcting a mapping, allow time for SharePoint to crawl and index the document again. If necessary, open the document library's settings and use the reindex option under Advanced settings.

4
Retest sharing and alerts

With test accounts, share the indexed document using the Share button, then check the sharing result and any DLP alerts or notifications in Microsoft Purview. Record whether access was blocked immediately or a notification arrived later.

Check property mapping and allow time for SharePoint indexing
Sharing restrictions can have other causes: An unavailable Anyone link or a disabled Send button can also result from SharePoint sharing settings, permissions, or other policies. Review those settings separately before attributing the behavior to a DLP condition.
Free Microsoft Office alternative

Edit Office documents with WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move everyday document work. Microsoft Purview and SharePoint still manage DLP policies; WPS does not fix their indexing or enforcement.

Edit documents used in SharePoint workflows with familiar toolsOpen and save common Microsoft Office formats, including DOCX, XLSX, and PPTXUse a free, lightweight office suite for everyday workMove between familiar document, spreadsheet, and presentation tools
microsoft office alternative - wps office

Frequently Asked Questions

Why can a document-property DLP alert arrive after sharing?

A property-based condition may depend on SharePoint crawling and indexing the mapped property. The alert can arrive later than the sharing action, depending on the policy and indexing status.

Where can I check the mapping for an AIP label property?

Open Search Schema in SharePoint site settings and inspect the managed property's crawled-property mapping and attributes. Confirm that the property is supported by the DLP condition in your environment.

Does a delayed DLP notification prove that sharing was blocked?

No. Check the policy's actions and enforcement mode in Microsoft Purview, and verify the actual sharing result with test accounts. A notification and an access restriction are different outcomes.

How can I tell whether the issue is specific to an AIP label property?

Add a custom property to a test document through File > Info > Properties > Advanced Properties > Custom, map it in the SharePoint search schema, and test a supported DLP condition after indexing.