Skip to content
Tools/Policy Tip Checker

DLP Policy Tip Checker

A tip that shows in Outlook on the web often shows nowhere else. Describe your rule and see which clients will actually warn the user, and what is stopping the rest.

Turning tips on is the easy part

Email gets checked twice. Once by the client as the user types, which is the only check that can show a tip or a dialog, and again on the way out, where the rule actions are applied. The two run different engines and accept different conditions.

So a rule can apply perfectly while the user sees nothing, and a tip can work when you test it in Outlook on the web then vanish the moment someone tries the same thing on their laptop. .

10
places a tip can appear
6
places one never can
1
tip shown at a time

Start from an example

Or skip this and describe your own rule below.

1. The client

These three settings decide what Outlook on the desktop will accept.

Licence
Outlook build
Connected experiences

2. What the rule looks for

Pick every condition in the rule. One unsupported condition stops the tip on that client, even if the rest are fine.

Conditions in the rule
What it matches on

3. How the user gets warned

Two different things get called a policy tip. The bar that appears as they type, and the pop-up when they hit send. The pop-up is Exchange only and much narrower.

4. How the rule is set up

The settings that quietly switch tips off.

Who the policy is scoped to

Shows on 9 of 10 surfaces

1 with caveats, 0 blocked. 6 more places never show tips at all.

Email

Files and sites

Chat

Devices

Elsewhere

Check a built-in SIT

About 100 built-in SITs drive tips everywhere. The rest only work where the full catalogue applies: Outlook on a recent build with E5 and connected experiences on, SharePoint and OneDrive on the web, and Word, Excel and PowerPoint on the web.