Default Sensitivity (Information Protection) Labels in a SharePoint Online Document Library

Copper Contributor

I am currently in the process of implementing information protection in a new SharePoint Online architecture that I am building to replace our one classic site (to rule them all), but I am experiencing an issue when trying to assign a default sensitivity label to an existing or new document library.


When accessing the basic library settings for any existing document library, I get two grey boxes that look like they are loading in, but never load where the default sensitivity label settings should be.



When creating a new document library, I can see the default sensitivity label setting, but there are no labels available.




For some context, I have created four sensitivity labels so far, and have created a test label policy that has assigned all four labels to my own account for testing.

For licensing, I have the following:

  • Office 365 E3
  • Enterprise Mobility + Security E5
  • Microsoft Defender for Office 365 (Plan 2)
  • Microsoft 365 E5 Compliance

This Licensing structure came out cheaper than M365 E5 and I was under the assumption that it had all of the functionality that my organisation requires at this point in time.


I have raised this issue with Microsoft support on the April 25th and still have not yet had a proper consultation let alone a resolution, so I am hoping the community here would be a bit more responsive.


Let me know if there is any more information that might be of help.

6 Replies
How are these sites create? From the built-in order form in SharePoint or from a provisioning engine and template.
The sites are created manually through the SharePoint admin portal.

The issue is happening in both team and communication sites.
As it turns out, if I use an account with an M365 E5 license, I don't encounter this issue.

So, what is the point of the M365 E5 Compliance add-on? What does it add?

When it seems like I can do everything except for this one piece of functionality without it, just using Enterprise Mobility and Security E5.


It should be included there from what I can gather :



Have you contacted Microsoft support or your License provider regarding this? Sounds like a bug or a miss 

Hi @NicolasKheirallah,
Thank you for replying again, I have recently closed the ticket that I raised with Microsoft on the 25th April because within those almost two months, I didn't receive any help whatsoever. Mainly because they didn't seem to be able to understand how to work with me in a New Zealand time zone. If I was able to get at least one useful conversation, would have made all the difference I feel.
How has it gone ? Have you gotten it fixed? :)