Changes to a data loss prevention policy don't take effect in Outlook 2013 in Office 365

Important 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:
To have us fix the problem for you, go to the "Fix it for me" section. If you prefer to fix this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To fix this problem automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

Download

Notes

• This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
• If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD, and then run it on the computer that has the problem.

Then, go to the "Did this fix the problem?" section.

Let me fix it myself

To work around this issue, force Outlook 2013 to download the updated DLP policies. To do this, follow these steps:

1. Use Registry Editor to remove existing DLP policies that are applied to Outlook 2013. To do this, follow these steps:
   1. Exit Outlook 2013.
   2. Click Start, click Run, type regedit, and then click OK.
   3. In Registry Editor, locate the following subkey:

      HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Outlook\PolicyNudges

   4. Delete the LastDownloadTimesPerAccount registry entry.
   5. Exit Registry Editor.
2. 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.
  • If the problem is fixed, you are finished with these steps.
  • If the problem is not fixed, visit Microsoft Community or contact support.
• We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email message.