Microsoft Entra Suite Tech Accelerator
Aug 14 2024, 07:00 AM - 09:30 AM (PDT)
Microsoft Tech Community
SOLVED

DLP Policy with nested conditions including "message type is" condition

Brass Contributor

Hello Everyone,

 

I have the below use case. Basically  my requirement is if user mail contains SSN( up to <= 2 instances) AND mail is sent to gmail.com. Block if the mail is not encrypted and Allow if it is encrypted.

 

Afsar_Shariff_0-1687182920068.png

 

This is how I have created the policy as shown below. However it is getting blocked whether the message is encrypted or not.  As per the logic it should allow only if it is encrypted and block if its not encrypted. Kindly advice if I am missing a logic. Thanks

 

Afsar_Shariff_2-1687183098746.png

 

 

Afsar_Shariff_3-1687183104478.png

 

Regards

Afsar

 

2 Replies
best response confirmed by Afsar_Shariff (Brass Contributor)
Solution

Hi @Afsar_Shariff 

 

I have configured an identical policy and it is functioning as expected. Can you see any data on the activity of sending the SSN through Activity Explorer? Or have you confirmed that the SSN and content you're entering in the email match the Social Security Number sensitive information type? You can copy the content you're using to a word file then upload it to the purview portal to see if it is a match. To do so:

 

  • Navigate to Home - Microsoft Purview
  • Drop-down data classification > select classifiers > sensitive info types
    • miller34mike_0-1687273245845.png

       

  • Find and select your social security number option from the list
  • On the SSN page, select Test
    • miller34mike_1-1687273373951.png

       

  • Upload the file with the same data you were testing through exchange and see if it finds a match

If you aren't getting a match, I recommend leveraging test data that you can download from dlptest.com to test your policies.

 

 

Also, do you have any other exchange online DLP policy that may be conflicting or preventing this policy from taking effect?

 

I'd also add the condition for Message Type Is = Permission Controlled to also see if the message is using a pre-built protection template like "Encrypt" or "Do Not Forward" or if you have configured Sensitivity Labels that enforce encryption will be covered by the "Permission Controlled" type as well, which I highly recommend and encourage you to leverage labels as well as DLP.

Thanks You
I have selected "Encrypt" and was using OME templates to encrypt the message. After selecting permission controlled it is working.
1 best response

Accepted Solutions
best response confirmed by Afsar_Shariff (Brass Contributor)
Solution

Hi @Afsar_Shariff 

 

I have configured an identical policy and it is functioning as expected. Can you see any data on the activity of sending the SSN through Activity Explorer? Or have you confirmed that the SSN and content you're entering in the email match the Social Security Number sensitive information type? You can copy the content you're using to a word file then upload it to the purview portal to see if it is a match. To do so:

 

  • Navigate to Home - Microsoft Purview
  • Drop-down data classification > select classifiers > sensitive info types
    • miller34mike_0-1687273245845.png

       

  • Find and select your social security number option from the list
  • On the SSN page, select Test
    • miller34mike_1-1687273373951.png

       

  • Upload the file with the same data you were testing through exchange and see if it finds a match

If you aren't getting a match, I recommend leveraging test data that you can download from dlptest.com to test your policies.

 

 

Also, do you have any other exchange online DLP policy that may be conflicting or preventing this policy from taking effect?

 

I'd also add the condition for Message Type Is = Permission Controlled to also see if the message is using a pre-built protection template like "Encrypt" or "Do Not Forward" or if you have configured Sensitivity Labels that enforce encryption will be covered by the "Permission Controlled" type as well, which I highly recommend and encourage you to leverage labels as well as DLP.

View solution in original post