Fix Microsoft Purview DLP Document Property Not Detected in SharePoint
Question details
The user's Microsoft Purview Data Loss Prevention (DLP) policy fails to detect specific document properties when files are uploaded to cloud storage.
- Product
- Microsoft Purview / SharePoint Online
- Device & OS
- not provided
- Scenario
- Uploading documents containing a specific property (Department: QC) to SharePoint and OneDrive environments.
- Observed behavior
- The DLP policy does not trigger, and the document property is not detected in the Activity Explorer or Alerts dashboards.
Ensure you have the necessary compliance administrator permissions in Microsoft 365 and verify that the target document actually contains the 'Department: QC' property metadata before uploading.
Escalate to Microsoft Purview Q&A
Because this issue involves specialized Microsoft Purview DLP processing rather than standard SharePoint Online functionality, the most effective solution is consulting Microsoft's dedicated Purview engineering support.
Data Loss Prevention (DLP) property detection issues in Activity Explorer often stem from backend sync delays, incorrect managed property mappings, or service-side Purview anomalies. Escalating to the specific product forum ensures specialized assistance.
Open your web browser and go to the official Microsoft Q&A platform tailored for enterprise administrators.
Visit the dedicated Microsoft Purview tag directly via: https://learn.microsoft.com/en-us/answers/tags/284/microsoft-purview
Click 'Ask a question' and provide the details of your DLP policy setup, specifying that the 'Department: QC' property is failing to trigger Alerts or log in Activity Explorer upon SharePoint uploads.
Experience Lightweight Document Creation with WPS Office
While Microsoft Purview handles complex enterprise compliance, dealing with heavy Microsoft services can sometimes slow down individual productivity. If you are looking for a fast, secure, and highly compatible tool for everyday document management, WPS Office is an excellent alternative.

Frequently Asked Questions
Why is my custom document property not triggering a DLP policy?
This usually happens if the property hasn't been crawled and mapped to a managed property in SharePoint's search schema, or if the Microsoft Purview sync hasn't fully completed across your tenant.
How long does it take for a new Purview DLP policy to take effect?
New or modified Microsoft Purview DLP policies can take anywhere from 1 hour to 24 hours to fully propagate and begin evaluating uploads in SharePoint and OneDrive.
Where can I view DLP policy matches and violations?
Policy matches, violations, and rule triggers can be monitored in the Activity Explorer and the Alerts dashboard within the Microsoft Purview compliance portal.




