Fix Microsoft 365 DLP Not Detecting Document Properties
Question details
Users need to block specific files from being emailed, but Microsoft 365 DLP policies fail to trigger when relying on standard document properties.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Attempting to prevent files on local servers or mapped drives from being attached to emails using DLP rules based on properties like Title, Size, or Owner.
- Observed behavior
- The DLP policy does not detect standard document metadata for email attachments, though it successfully triggers on sensitivity labels or document names.
Ensure your Microsoft 365 DLP policies are running in test mode to monitor their behavior without disrupting user productivity, and verify that your tenant has the appropriate licensing for Endpoint DLP.
Verify SharePoint Indexing and Searchability
Ensure the document property you are trying to detect is properly indexed and recognized by Microsoft 365 search services.
Microsoft 365 DLP conditions often rely on SharePoint Search managed properties. If a document property is not indexed or supported by the specific workload (like Exchange for local attachments), the policy will fail.
Upload your test file (e.g., from the local Z: drive) to a SharePoint site library to initialize metadata indexing.
In the SharePoint site search bar, run a query using the target property and value, such as 'Title:ISMS'. If the file does not appear, the property is not properly indexed.
Log in to the Microsoft Purview compliance portal. Navigate to Data loss prevention > Policies, and edit your rule to match the exact managed property verified in the search test.
Allow up to 24 hours for the new indexing and DLP policy changes to fully propagate across Exchange and SharePoint workloads.
Implement Supported Alternative Conditions
Switch from unreliable document properties to highly supported DLP conditions like sensitivity labels or file names.
Looking for a Lightweight and Secure Office Suite?
Enterprise Data Loss Prevention in Microsoft 365 can be complex to configure. For everyday document management, WPS Office provides a streamlined, highly compatible alternative with easy-to-use built-in file encryption to keep your data secure.
- 1. Download WPS Office: Visit the official WPS website to download the free installation package for your operating system.
- 2. Install the application: Run the installer and follow the on-screen instructions to set up the suite in minutes.
- 3. Secure your documents: Open your files in WPS Office and navigate to Menu > Document Encryption to easily apply password protection.

Frequently Asked Questions
Why does Microsoft 365 DLP detect document names but not properties like Title?
Document names are universally preserved as basic file metadata across all operating systems. In contrast, properties like 'Title' or 'Owner' are specific metadata fields that require SharePoint managed property indexing, which is often lost or unreadable when a file is moved from a local drive directly to an Exchange attachment.
Can I use DLP policies to block email attachments directly from a local mapped drive?
Yes, but standard Exchange DLP rules may not catch local file metadata. You generally need Microsoft Purview Endpoint DLP configured via Intune to monitor and block local file activities before the file is attached to an email, or rely on file name patterns and sensitivity labels instead.
How long does it take for a new Microsoft 365 DLP policy to apply?
After creating or modifying a DLP policy in the Microsoft Purview compliance portal, it typically takes 1 to 24 hours for the policy to fully sync and enforce across Exchange, SharePoint, OneDrive, and Endpoint workloads.
What is the most reliable way to prevent sensitive local files from being emailed?
Applying Microsoft Purview Information Protection sensitivity labels to your files is the most reliable method. Labels travel with the file regardless of whether it is stored on a local Z: drive or SharePoint, and DLP policies consistently recognize these labels during Exchange email transit.




