Have you ever heard claims about sensitivity labels and information governance that made you raise an eyebrow or two? Well, you’re not alone! In my time with Microsoft 365 Purview, I’ve come across a number of “established truths” that turn out to be more myth than reality. From functionality and licensing to implementation, let’s try to dispel some of the many misconceptions. Ready to get some myths busted?
First of all, let's look at the two main forms that sensitivity labeling comes in:
Manual and automatic. Manual labeling requires users to manually select and assign a label to files, emails, or other types of data.
Auto-tagging, on the other hand, applies labels automatically based on predefined conditions, either on the client side* or the service side**, ensuring protection without user intervention.
*This refers to the settings that are configured directly in a sensitivity label when it is created. This setting is used to automatically assign labels in real-time as users create or edit documents and emails in Office applications such as Word, Excel, PowerPoint, and Outlook
**This is a policy used to automatically assign labels to existing content that is already stored in SharePoint, OneDrive, or sent via Exchange Online
Assertion: We cannot start with sensitivity labels because we do not have E5... - Wrong❌
For manual/user driven labeling
Microsoft 365: E5, A5, G5, E3, A3, G3, F1, F3, Business Premium, and OneDrive for Business (Plan 2)
Enterprise Mobility + Security: E3, E5
Office 365: E5, A5, E3, A3
Azure Information Protection (AIP): Plan 1, Plan 2
However, for automatic content labeling, E5 or equivalent is required.
Enterprise Mobility + Security: E5, A5, G5
Microsoft 365: E5, A5, G5
Microsoft 365 Compliance: E5, A5, G5, F5
Microsoft 365 Security & Compliance: F5
Microsoft 365 Information Protection and Governance: E5, F5, G5
What I often see is that you can go far with the license portfolio you have to get started and get well on your way, as long as you are within the requirements described under manual/user-driven labeling.
Claim: Labels in Purview are not working. We tried rolling out labels but they didn't show up so we scrapped it... - Wrong❌
I can relate to this.. Often you sit around testing, rolling out, waiting... Make some changes, rolling out again.. But nothing ever shows up and you give up. 😮💨
From the time you press publish in a label policy until the labels actually appear, Microsoft says it can take up to 24 hours, in reality it can take up to 72 hours before they are actually in place in all the nooks and crannies. The same applies to changes you make after the labels have been published.
Claim: The labels seem unstable and different from user to user... - Well...❌
There is room for error here. Like everything else in life, labels of sensitivity have rank. ⭐
Priority order:
The label placed first has the lowest priority (least sensitive), while the label placed last has the highest priority (most sensitive).
Evaluation of multiple labels:
If multiple labels meet the classification criteria, the label with the highest priority (the one placed last) will be selected
Change of order:
You can change the order of the labels by moving them up or down in the list in the portal.
This system ensures that the most appropriate label is applied to the content, based on the sensitivity of the data.
Bjørnar&AI
Комментарии