How to Exclude Manually Encrypted Emails from Microsoft 365 DLP Policies
Question details
The user needs to prevent manually encrypted emails in Outlook from incorrectly triggering Microsoft 365 Data Loss Prevention (DLP) policies.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Configuring Microsoft 365 DLP policies in Purview with exceptions intended to skip scanning for encrypted messages.
- Observed behavior
- Emails that are manually encrypted by the user in Outlook still trigger the DLP policy, bypassing the configured exception rule.
Ensure you have global administrator or compliance administrator permissions in the Microsoft Purview portal to view and edit Data Loss Prevention policies.
Verify DLP Rule Conditions and Allow for Policy Propagation
Check that your DLP rule exception specifically matches the exact encryption method applied in Outlook, and allow sufficient time for the policy changes to sync across the environment.
Manually applied encryption (like AIP labels, S/MIME, or OME) alters the message envelope differently than automatic transport rules. The DLP engine might not detect the encryption if the exception rule is configured for a different message-type condition.
Check the exact encryption type being applied manually in the Outlook client (e.g., Office 365 Message Encryption, S/MIME, or an Azure Information Protection label) so you know which condition to target.
Log into the Microsoft Purview compliance portal, navigate to 'Data Loss Prevention' > 'Policies', select your active policy, and edit the rule to ensure the exception explicitly covers the manual encryption method identified.
Save any modifications to the DLP policy. Policy changes in Microsoft 365 Exchange environments can take up to 24 hours to fully propagate and take effect on client traffic.
After 24 hours, send a test email containing sensitive data but utilizing the manual encryption method to verify if the policy correctly excludes the message from triggering an alert.

Open a Microsoft Support Case with Rule Diagnostics
If the rule still fails to identify manually applied encryption after 24 hours, escalate the issue to Microsoft Support for backend message-type detection analysis.
Looking for a Lightweight and Free Office Suite? Try WPS Office
While Microsoft 365 handles complex enterprise compliance like Exchange DLP policies, for day-to-day document creation, WPS Office provides a free, fast, and lightweight alternative. Enjoy a familiar interface and essential tools for word processing, spreadsheets, and presentations without the heavy subscription costs.

Frequently Asked Questions
Why does my DLP exception for encrypted messages fail on manually encrypted emails?
Microsoft 365 DLP engines may not correctly parse the message-type condition if the manual encryption (like AIP labels or S/MIME) alters the message structure before the DLP transport rule evaluates it. The exception configuration must explicitly match the encryption protocol used by the sender.
How long does it take for a modified Microsoft 365 DLP policy to apply?
While some minor changes might sync quickly, Microsoft advises that modifications to Data Loss Prevention policies can take up to 24 hours to fully propagate across the entire tenant and Exchange workloads.
Can I exclude specific users from a DLP policy instead of filtering by encryption status?
Yes. In the Microsoft Purview compliance portal, you can add an exception to the DLP rule based on the sender's email address, domain, or Microsoft 365 group membership, which bypasses the encryption detection issue entirely for those specific users.




