Forum Discussion
Ion Zubia
Jan 16, 2018Brass Contributor
Azure information protection custom policies not working
Hello, I'm playing around with an Enterprise Mobility + E3 license and security and I was following the next tutorial/document from Microsoft: https://docs.microsoft.com/en-gb/information-protection...
- Jan 19, 2018
In addition to checking the firewall isn't blocking IP addresses and URLs, check it's not terminating your TLS connection, which breaks certificate pinning. I've added a tip how to check for this client-side, if you don't manage the firewall yourself. See https://docs.microsoft.com/en-us/information-protection/get-started/requirements#firewalls-and-network-infrastructure
subhendudas
Aug 25, 2020Copper Contributor
Ion Zubia and other in this thread
I have been following the entire thread and some of these solutions may not work. I found a solution that always works and I have tested all of the scenarios as follows:
- Improper installation of AIP Unified Labeling Client
- Improper upgrade of AIP Unified Labeling Client
- UL Client was unable to download protection template from RMS Service due to network issue
- UL Client unable to update stale protection template tokens cache stored locally in user profile
Check the following before proceeding
- User has AIP P1/P2 license
- User is logged into office App with correct account. If multiple account is used to login, please log out from all other account except the account that is supposed to use the AIP Protection.
- Ensure that there are no additional Work Account added to windows 10 other than the account using AIP Protection.
Solution 1: - Delete Crypto Keys from the effected user profile
- Close all the office apps. Word, Outlook, Excel and PowerPoint.
- On file explorer navigated to the folder "%APPDATA%\Microsoft\Crypto\" in there please rename the folder Keys to any name.
- Open Word and click on Sensitivity Icon -> Help and Feedback -> Reset Settings.
- Close Word and re-open, give couple of minutes for the UL client to retrieve labels and your Client will re-build the protection template cache too.