Changes to a data loss prevention policy don't take effect in Outlook 2013 in Office 365
Original KB number: 2823261
Microsoft 365 compliance is now called Microsoft Purview and the solutions within the compliance area have been rebranded. For more information about Microsoft Purview, see the blog announcement.
After you make a change to a data loss prevention (DLP) policy, the change doesn't take effect in Microsoft Outlook 2013 in Office 365. For example, you experience one or more of the following symptoms:
- Policy tips aren't displayed correctly when the conditions in the DLP policy are met.
- Messages aren't appropriately blocked by the DLP policy.
You experience these symptoms even though the DLP policies were working correctly before the change was made.
This problem occurs if the updated DLP policy wasn't downloaded to Outlook 2013. Outlook 2013 checks for changes to DLP policies one time every 24 hours.
This section contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see the following Microsoft Knowledge Base article:
322756 How to back up and restore the registry in Windows
To work around this issue, force Outlook 2013 to download the updated DLP policies. To do this, follow these steps:
Use Registry Editor to remove existing DLP policies that are applied to Outlook 2013. To do this, follow these steps:
Exit Outlook 2013.
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate the following subkey:
Delete the LastDownloadTimesPerAccount registry entry.
. Exit Registry Editor.
Start Outlook 2013, create a new message, and then type some text. When you do this, you force Outlook 2013 to download DLP policies.
Did this fix the problem?
- Check whether the problem is fixed.
For more information about DLP features in Exchange Online Protection, go to the following Microsoft TechNet website:
Still need help? Go to Microsoft Community.