Forum Discussion
Query Regarding Data Labeling in Microsoft Purview
As I delve into learning about Microsoft Purview, I have a question regarding data labeling. Is it required to perform labeling through the compliance portal, or can it be done directly within Microsoft Purview? For instance, if we classify data into groups such as public, private, confidential, and restricted within the classification feature of Purview, can we then create data policies based on this classification? Additionally, if we use this method of classification, what is the purpose of sensitivity labels?
myself new to Purview, you asked a very good question and from the documentation I read the screen capture below, lets look into this together.....?
Technical details are on this link, I am still reading it so might be able to answer in more accurate terms after figuring out something...
thanks for sharing the link... surely, we both will try to figure out. I have read a little bit, will update if I will get the answer for my query.
- Hello,
From my experience,
label and Labe policies : Label is used for Data classification,record managmnet and Data lifecycle(retain,destory). Label can travel with file with in M365 estate. Only one label can attach to file at a time. To attach label we need label policies.
sensitivity labels and policies : These also can be used to classify data.But these are mostly used to Protect data ( Block access, stop sharing, data loss, encryption, watermarks) . Similar to above label policies here are we can use label policy to publish sensitivity labels. Hi Gaurav_Rajput ,
Microsoft Purview is the main portal for all information governance and compliance-related solutions (For example: Data Loss Prevention, Classifiers, Labeling, Insider Risk Management, eDiscovery, etc.)
Below are the high-level three steps for setting up Data Labeling in the Purview portal (https://compliance.microsoft.com/)
1. Create a Sensitivity Label (On the portal, click under "Solutions" on the left -- "Information Protection" -- "Labels" -- "+ Create a label")
2. Once created, Publish the Label via a Policy to make this label available to users (On the portal, click under "Solutions" -- "Information Protection" -- Use either "Label Policies" or "Auto-Labeling" depending on the requirements)
3. Policy will first run in Sumulation Mode to assess the impact and then it can be turned On.You can create your Sensitivity SubLabels under default predefined parent Labels (Public, Internal, Confidential, and Highly Confidential) and then publish by calling "Parent/SubLabel" via a Label policy (Manual or Auto-Labeling)
https://learn.microsoft.com/en-us/purview/sensitivity-labels#sublabels-grouping-labels
Example:
A snippet from the below article from Microsoft specifically related to the default out of the box default labels:
"Microsoft recommends no more than five top-level parent labels, each with five sub-labels (25 total) to keep the user interface (UI) manageable. Levels are typically arranged from least to most sensitive such as Public, Internal, Confidential, and Highly Confidential."thanks
