Microsoft Purview DLP - Getting Outlook Mobile Policy Tips and Override Prompts to work

I've been spending some time testing Microsoft Purview DLP in a Business Premium environment, specifically looking at how policy tips and override prompts behave across Outlook desktop and mobile.

The interesting part was that the DLP policy itself was working as expected. Emails were being blocked, alerts were generated, and the Windows Outlook experience was working fine. However, Outlook mobile was a different story.

I could get the DLP enforcement working, but the policy tips and the option to override with a justification were not appearing on mobile. After a lot of soul searching, I finally got it to work. Here's how I went about it.

The initial configuration

At first I worked with a DLP policy based on a sensitivity label, with user notifications enabled. The policy was configured to cover multiple workloads. Nothing crazy about this as it was working fine over desktops. Then I enabled the Outlook DLP policy-tip setting through Microsoft 365 Apps Cloud Policy Management expecting that this is all I needed.


I know it says for Mac, but it is actually applicable for mobile devices.

But things didn't work on the mobiles. No Outlook Tips, nothing. After researching a bit I realised that I need additional licensing. As it turns out, an E5 level add-on is required to unlock the "Show the policy tip as a dialog before send" setting in Purview, which powers interactive user overrides. Now on Windows, this license provides immediate value by activating a local client engine that pauses outbound emails to display your custom override prompt, but on mobile devices, there is absence of a local scanning engine, meaning they ignore the override prompt and fall back to a server-level hard block. During my testing, I found out that an E5 add-on is required after all to unlock interactive mobile prompts.

After adding the appropriate Information Protection add-on licensing in my tenant, the override feature showed up in the DLP policy.


As for the license, I just went ahead and bought an M365 E5 Information Protection and DLP (add-on) to compliment my Business Premium license.


Now on Windows, everything behaved as expected. Outlook displayed the policy tip and, when an override was permitted, the user could provide a justification. However, on mobiles, the policy tip nor the override prompt still didn't appear. I was at my wits before I stumbled upon another requirement.

The required configuration

I started looking deeper and that is when I realise that I needed to use some sort of recipient conditions. Now the original DLP rule included the condition, 'Recipient scope = Outside the organization', so technically that should satisfy this requirement. More on that later..


At first I couldn't see the recipient conditions when I tried editing the original multi-workload policy. I decided to create a separate policy scoped specifically to Exchange Online. Lord behold, with this configuration, I could access the recipient-based conditions, including 'Recipient domain is' -


To test, I added an external test domain to see if it resulted in a different behaviour or not. Luckily, this time it worked. Both Outlook mobile policy tip and override prompt appeared. That was a useful finding, although it raised another question. Maintaining a list of external recipient domains isn't particularly practical in a real production environment.

The solution? It is using an exception for the internal domain. Rather than relying solely on the original recipient-scope condition, I added an exception for my internal domain:

Recipient domain not is = <yourinternaldomain>


Voila! The exception worked during my testing. This allowed me to retain the external recipient condition while excluding the internal domain.

End-user & Admin experience

After making the changes, I went back to Outlook mobile. At first it took a while to sync and things still didn't work. In fact one one rare occasion, I had to reset the Outlook app to drop the cached settings. But things eventually started to work. The policy tip was now appearing, and the override option was available.

With the alerting on, alerts got generated as expected and ready for analysis.



Final thoughts

A few things I took away from this exercise that are worth keeping in mind:

1. DLP enforcement and the Outlook mobile policy-tip experience are not necessarily the same thing.

2. Enabling DLP policy tips through Microsoft 365 Apps Cloud Policy is an important part of the configuration. 

3. Exchange Online-only policies expose recipient conditions that may not be available when using a multi-workload policy.

4. Recipient-domain conditions and exceptions are worth testing when troubleshooting the mobile experience.

5. Don't assume that a policy working correctly in desktop Outlook means that the same user experience will automatically be available in Outlook mobile.

6. I also wouldn't generalise the recipient-domain configuration based on a single test domain. Mixed internal and external recipients should be tested separately.

As always, these are observations from my own tenant testing. Your results may vary depending on licensing, policy configuration, Outlook version and device management.

References:

Comments

Popular posts from this blog

Fixing Tamper Protection Blob Error 65000 using Microsoft Intune

Defender Offboarding using Intune - The EDR way!

Enable and Configure Windows Defender Firewall rules using Intune