Compliance Problems

How to Handle Microsoft DLP False Positives in Email Signatures

Natalie TaylorNatalie Taylor Nov 2, 2026 870 views

Question details

Users are experiencing false positive DLP alerts triggered by standard information in email signatures, and administrators need to know if signatures can be excluded from DLP scanning.

Can Microsoft Purview DLP Ignore Email Signatures?
Product
Microsoft Purview Data Loss Prevention
Device & OS
not provided
Scenario
Scanning outbound emails where employee signatures contain sensitive-looking sequences like VAT, registration, or telephone numbers.
Observed behavior
Microsoft DLP triggers policy alerts based on email signature content, treating standard business numbers as data loss prevention violations.
Before you start

Ensure you have Compliance Administrator or Global Administrator privileges in Microsoft 365 to view and modify Data Loss Prevention policies in the Purview portal.

Solution 1Recommended

Enable Policy Tips and User Overrides

Since Microsoft Purview DLP does not natively support excluding email signatures, the recommended best practice is to allow users to override false positives via policy tips.

Microsoft DLP scans the entire message body, including appended signatures. Standard business details like telephone or VAT numbers often trigger unwanted alerts, and there is no UI setting or PowerShell cmdlet to skip the signature block.

The official Microsoft guidance is to empower users to report these false positives directly from their email client, allowing administrators to review incidents and adjust Sensitive Information Types (SITs) accordingly.

1
Access the Compliance Portal

Log in to the Microsoft Purview compliance portal using your administrator credentials and navigate to Data loss prevention > Policies.

2
Edit the Target DLP Policy

Select the specific DLP policy that is flagging the email signatures as false positives and click on 'Edit policy'.

3
Enable User Notifications

Proceed to the 'Advanced DLP rules' section. Edit the rule, scroll to 'User notifications', and turn it on to show policy tips to users in Outlook.

4
Allow User Overrides

In the 'User overrides' section, check the box to allow users to override the policy restriction with a business justification. This allows them to mark the alert as a false positive.

Enable Policy Tips and User Overrides
No Direct Exclusion Method: There is currently no PowerShell command or configuration option to natively bypass email signatures during a Microsoft Purview DLP scan.
Free Microsoft Office alternative

Looking for a Lightweight Office Suite? Try WPS Office

While enterprise compliance like Microsoft DLP requires specialized IT configuration, your everyday document creation should be simple and hassle-free. WPS Office provides a lightweight, highly compatible alternative to Microsoft Office for your daily productivity needs.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx)Built-in robust PDF editing and conversion toolsLightweight software that installs quickly and consumes minimal system resourcesFamiliar user interface requiring zero learning curve for easy migration
microsoft office alternative - wps office

Frequently Asked Questions

Can I exclude a specific text string from Microsoft DLP scanning?

Yes, you can add exceptions to a DLP policy based on specific text content or subjects using the 'Except if' condition. However, this exception applies to the entire email message, not just the signature block, which might bypass scanning for the actual email body.

Why do VAT or telephone numbers trigger DLP alerts?

These numbers often match the specific digit patterns, lengths, and checksum requirements of default Sensitive Information Types (SITs) configured in Purview, causing the system to mistake standard business information for regulated data.

Is there a PowerShell script to bypass email signatures in DLP?

No. Microsoft has not provided a specific cmdlet or parameter in Exchange Online PowerShell that allows administrators to exclude signature blocks or specific HTML divisions from DLP scanning.