i create sensitivity label in microsoft compliance portal, the lable is not working

Mohan Raj 20

Remote server returned '550-5.7.162 OmeEncryptionAgent; Permanent Failure 550-5.7.162 Exception encountered: RmException. 550-5.7.162 Exception message: Failed get licensing URI. FailureCode:CorruptConfiguration. Recoverable:False.. 550 5.7.162 Please contact your system administrator for more information.'

SokiGuo-MSFT 23,481 Reputation points Microsoft Vendor

2024-04-04T07:03:42.3166667+00:00

Hi

Thank you for your question.

We are currently looking into this issue and will give you an update as soon as possible.
Kael Yao-MSFT 37,496 Reputation points Microsoft Vendor

2024-04-05T01:13:57.5533333+00:00

Hi @Mohan Raj,

Do you get this error message when adding the sensitive label as an end user?

If yes, what is the license assigned to this user?
Mohan Raj 20 Reputation points

2024-04-05T11:08:41.6066667+00:00

yes, i get this error after apply the sensitivity label. we assign bussiness premium license for the users.
Catherine Kyalo 570 Reputation points Microsoft Employee

2024-04-09T19:58:43.98+00:00
This error is usually related to the Office Message Encryption (OME) configuration. The error message suggests that there might be a corrupt configuration in your Office 365 setup.

Here are a few troubleshooting steps to resolve this issue:

Check the configuration of your sensitivity label and make sure it's published correctly. You can refer to this documentation on how to create and configure sensitivity labels: Create and configure sensitivity labels

Verify your OME configuration. This error might occur if there's an issue with your OME setup. You can refer to this documentation on how to configure OME: Configure Office Message Encryption

Contact Office 365 support. If you've checked your sensitivity label and OME configurations and everything seems to be in order, you might need to contact Office 365 support for further assistance. They can help you diagnose and fix configuration issues in your Office 365 environment.

If the issue persists, consider using Microsoft Graph API to manage sensitivity labels. Here is a link to the API reference: Microsoft Graph API Sensitivity Labels

Remember to ensure that your Azure AD application has the necessary permissions to access and manage sensitivity labels via the Microsoft Graph API.
Jayce Yang-MSFT 1,246 Reputation points Microsoft Vendor

2024-04-24T03:09:32.65+00:00

Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.