“Sync Data Labels Now” failed with error “Something went Wrong. We are not able to fetch labels for this application”

After the authorization step is successfully completed, “Sync Data Labels Now” step fails to complete rendering an error “Something went Wrong. We are not able to fetch labels for this application” as shown below.

• Data Security
• Microsoft Purview environment
• Office 365 package
• Azure workspace

This mandatory description field is missing in Microsoft during the time of label creation. 

These following steps should be performed to identify and resolve the issue: 

1. Start off with a fresh session or an incognito browser session in to Data Security portal-> Settings->Data Label Settings-> Microsoft Information Protection -> Office 365 instance 
2. Ensure that there are no connection issues between Microsoft Purview and Data Security. 
3. Ensure that the “Authorization with Microsoft is successful” as per step3 of Microsoft-labeling-for-office-365 
4. For this use-case and sync to work, verify Data Labels are created on Purview. Make sure that all mandatory fields of each data label are entered with content 
5. For this issue, ensure that the “description field for both user level and admin level.“
6. Finally, after few hours of normalizing above data points, verify Data Security->Settings->Data Label Settings-> Microsoft Information Protection ->”Sync Data Labels Now”  status in Green. 
    

• On Microsoft Purview when admins defined MIP/AIP data labels, they may miss adding description field.
• The decryption comes in 2 variations per sensitivity label such as (1) description for users (2) description for admins. 
• This description field is a mandatory in Microsoft during the time of label creation. 
• To detect this error, a HAR file was taken during the time of “sync”. The error was pointing to a 500 “internal server error”. When correlated this error with the backend API call which rendered the error, there was an exception “internal server error” (500) from API call  SensitivityLabels .
• This exception was caused by not having content within description field in every data label part of Purview.