Error when applying Sensitive Labels with Encryption

Question

Hi community,

I can see the sensitivity labels in my office apps correctly but when I select one label with encryption I get the following error:

I have configured the required sensitive labels, assigned the proper permissions, and published them as you can see.

Checking the MSIPC logs I can see the only templates it gets are the default and not the configured sensitivity labels.

[msipc]: ++++++++ INFORMATION: Adding template: ++++++++

      Id: "{f148296a-9a9a-4764-a12f-44523fc0cebf}", 

      Name: "Confidencial \ Todos Los Empleados", 

      Description: "Datos confidenciales que requieren protección pero conceden todos los permisos a todos los empleados. Los propietarios de los datos pueden hacer un seguimiento del contenido y revocarlo.", 

      IssuerName: "Corporación S.A.". 

}}{{[787][msipc]:[Info]:[704]:[2021-12-20 15:59:45.669]: win7ippstore.cpp:Microsoft::InformationProtection::TemplateManager::copyTemplateInfoToList:518

[msipc]: ++++++++ INFORMATION: Adding template: ++++++++

      Id: "{d262518a-36de-4962-8b27-4966ca9416ed}", 

      Name: "Extremadamente Confidencial \ Todos Los Empleados", 

      Description: "Datos extremadamente confidenciales que conceden a los empleados los permisos de visualización, edición y respuesta en relación con el contenido. Los propietarios de los datos pueden hacer un seguimiento del contenido y revocarlo.", 

      IssuerName: "Corporación S.A.". 

}}{{[788][msipc]:[Info]:[704]:[2021-12-20 15:59:45.669]: win7ippstore.cpp:Microsoft::InformationProtection::TemplateManager::GetTemplateList:196

++++++++ INFORMATION: Getting templates succeeded. ++++++++

Any ideas are welcome!

Answer 1

Hi @Ethan,

So after 11 days since sensitivity labels were created...end-users communicate they are now able to apply all the labels including the ones that apply encryption. It is kind of concerning the time it takes to propagate the labels within the tenant. 

I also had to open a support case with Microsoft, I have not received a response yet but in the meantime and after a lot of waiting (11 days) finally, labels are available. Other configurations like Coauthoring and enabling labels for Teams, Sharepoint, and M365 Groups also take a lot of time.

Hopefully, Microsoft improves the time it takes to speed up all of these configurations.

Have a good one all of you. I will post again if another roadblock is found.

Answer 2

Hi @Ethan

" So first I want to confirm with you:After your deployment, did you have this problem alone, or did other members of the organization have the same problem?"

Yes, It happens with all the users in the Pilot deployment.

"And in order to prevent the problem from your local client, please try it on the Word web page and check whether the problem still exists or not ?"

Yes, we tried it on the web after enabling "coauthoring" and it prompts an error when trying to apply it.

Today I received a notification from a user that it seems to be working now after doing nothing more and waiting 11 days.

I will confirm with you and the community later today or tomorrow.

Thanks for your support.

Answer 3

Hi，

I wrote this reply to follow up on this thread. Have you checked my last reply?

Has your problem been resolved? I look forward to your reply!

Best Regards，

Ethan

Answer 4

Hi

Thank you for your question in this community, based on your description, when you applied Sensitive Labels with Encryption got an error message,

So first I want to confirm with you:

After your deployment, did you have this problem alone, or did other members of the organization have the same problem?

And in order to prevent the problem from your local client, please try it on the Word web page and check whether the problem still exists or not ?

After I tested it on my local machine, there was no problem, so we may need to eliminate the possibility of the problem step by step and find the root cause of the problem in order to better help you solve this problem. Thank you for your support and understanding!

Best Regards，
Ethan