Fix Exchange DLP Rule Triggering on Email Body Instead of Attachments
Question details
The user wants to configure an Exchange Data Loss Prevention (DLP) rule to detect a specific volume of customer email addresses strictly within attachments, without evaluating the email message body.

- Product
- Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Creating a Microsoft 365 DLP policy to prevent data leakage by detecting documents containing 50 or more external email addresses.
- Observed behavior
- The DLP rule ignores the attachment-only intention and incorrectly triggers when it detects a single email address in the message reply body, overriding the minimum instance count of 50.
Ensure you have Exchange Administrator or Compliance Administrator privileges in your Microsoft 365 tenant to access and modify Data Loss Prevention policies.
Adjust Advanced Exchange DLP Rule Settings
Since Exchange DLP cannot natively exclude the email body from scans, adjusting the instance count and confidence levels in advanced settings helps minimize false positives.
Microsoft Exchange currently does not provide a direct option to exclude the email message body while scanning attachments for sensitive information types. The DLP engine evaluates the entire message item as a whole.
To work around this limitation, you can utilize the advanced rule editor to fine-tune the minimum instance count and match accuracy. While this does not completely eliminate body scanning, it significantly reduces unwanted triggers from normal email replies.
Sign in to the Microsoft Purview compliance portal using your administrator credentials.
On the left navigation pane, expand 'Data loss prevention' and click on 'Policies'.
Select the DLP policy that is triggering incorrectly and click 'Edit policy'.
Proceed through the wizard until you reach the 'Customize advanced DLP rules' page. Click 'Edit' on the specific rule you wish to modify.
Under the 'Conditions' section, locate the sensitive info type. Increase the minimum instance count (e.g., to 50) and adjust the confidence level to a higher threshold.
Save your changes and ensure the policy is set to 'Test it out first' so you can monitor the results without disrupting user email flow.

Utilize Exchange Mail Flow Rules as an Alternative
If standard DLP policies cannot isolate attachments effectively for your compliance needs, consider using Exchange Mail Flow (transport) rules targeted specifically at attachment properties.
Manage Your Sensitive Documents with WPS Office
While Microsoft 365 manages backend email compliance and DLP rules, you might be looking for a lightweight, cost-effective solution for creating and handling the actual document attachments. WPS Office provides a free, intuitive alternative to Microsoft Office for editing your important files.
- 1. Download the Installer: Visit the official WPS Office website and click the Free Download button for your operating system.
- 2. Install WPS Office: Run the downloaded installer file and follow the simple on-screen instructions to complete the setup.
- 3. Open Your Documents: Launch WPS Office and instantly open, edit, or save your existing Microsoft Word, Excel, and PowerPoint files.

Frequently Asked Questions
Can I configure an Exchange DLP rule to scan only attachments and ignore the email body?
Currently, Exchange DLP does not provide a native setting to explicitly exclude the email message body while scanning attachments for sensitive information types. The DLP engine evaluates the entire message item comprehensively.
Why is my DLP rule triggering on email replies even with a high instance count?
When users reply to emails, the message body accumulates historical text, headers, and signatures. If an external email address appears anywhere in the reply chain, the DLP scanner detects it. Sometimes, the structural formatting of replies can cause the scanner to miscalculate instance counts, leading to unexpected triggers.
How can I safely test a new Exchange DLP policy without blocking emails?
You should always deploy new or modified DLP rules using the 'Test it out first' mode in the Microsoft Purview portal. This allows the system to evaluate rule matches and generate incident reports so you can gauge accuracy without actually restricting the user's email flow.




