Jan 16 2018
- last edited on
Feb 19 2021
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/get-started/infoprotect-quick-start-tutorial
However, after completing every step the following error will pop up when trying to select a custom policy. I have tried creating different policies with different setups in vain:
I wonder what else is needed?
Mar 11 2019 03:12 PM
I'm getting the same error with and without firewall, We don't see any of the templates downloaded.
any Other help would be appreciated.
Mar 22 2019 07:20 AM
One thing that worked for me after getting this error message was to go to a random Word document saved anywhere on your computer. In File Explorer, right-click the Word document and click Classify and protect to open the AIP Client.
Next, select one of your custom labels, it shouldn't matter which one and click apply. This forces the custom label in a way that you can't do in Word. After that I was able to assign custom labels within Word after that with no issues. Hope that helps.
Sep 19 2019 08:22 PM
I've got same problem with you today.
I created a label and a label policy in M365 Security Center (I'm using Unified Labeling client as required)
But it doesn't work well.
After hours of troubleshooting and found that I've met all of those requirements mentioned in technet docs.
But, a strange default "Archived" state of the label (template) caused my custom label to stop working.
You can try using the following commands to troubleshoot:-
Get-AipServiceTemplate | FL
Get-AipServiceTemplateProperty -TemplateId <xxxxxxxx> -Status <--- this reports the custom label is at "Archived" state by default, what the hell.
To fix it:-
Set-AipServiceTemplateProperty -TemplateId <xxxxxx> -Status Published
After these, I can now apply the label in either Office apps or File Explorer
This link helped me in troubleshooting
Sep 20 2019 07:25 AM
@Larry_ChanThanks for the update, as I have expanded my uses of Labels and Policies I encountered this and this fix one of my label issues.
Aug 25 2020 07:01 AM
@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:
Check the following before proceeding
Solution 1: - Delete Crypto Keys from the effected user profile