Hello, 
We are in the process of moving some of our mail-flow / transport rules over to Microsoft Purview. 
We don’t want the DLP policy to apply when people click their “Encrypt” or “Do not Forward” buttons (RMS templates; OME encryption.)

Putting “Permission Controlled” in the exceptions group should theoretically let the emails go through. The exception we have for when people put “Encrypt” in the subject line works (we have a mail-flow rule that encrypts those emails.)
But actually clicking “Options” > “Set permissions on this item” > “Encrypt” doesn’t remove the policy tip on an email draft, and people are unable to send the emails. 

Can someone verify this is rule constructed properly? If so, we may have to reach out to Microsoft Support. Thank you so much for your time and help!

​Hello, We are in the process of moving some of our mail-flow / transport rules over to Microsoft Purview. We don’t want the DLP policy to apply when people click their “Encrypt” or “Do not Forward” buttons (RMS templates; OME encryption.)Putting “Permission Controlled” in the exceptions group should theoretically let the emails go through. The exception we have for when people put “Encrypt” in the subject line works (we have a mail-flow rule that encrypts those emails.)But actually clicking “Options” > “Set permissions on this item” > “Encrypt” doesn’t remove the policy tip on an email draft, and people are unable to send the emails. Can someone verify this is rule constructed properly? If so, we may have to reach out to Microsoft Support. Thank you so much for your time and help!  Read More

​