<img alt="" src="https://secure.hims1nice.com/151009.png" style="display:none;">
Skip to main content

Upcoming changes to Purview Information Protection Labeling

Tim Humphrey
Posted by Tim Humphrey
Upcoming changes to Purview Information Protection Labeling

If you have begun (or are considering) your Information protection (Sensitivity labeling) rollout using Microsoft Purview here is some news you need to be aware of.  There is a major User Experience (UX) change coming that could be just the opportunity you were looking for to help drive/redirect a better End User adoption experience for your Sensitivity Label rollout.

What is changing?

Microsoft is beginning to rollout a new feature for Sensitivity labels that we believe will make adoption/management of sensitivity labels for straightforward.  They are moving from the Parent/Sub label model to Label Groups.  This is meant to reduce the confusion for end-users who see the parent label where sub labels exist but cannot select the parent label.

  • Label Groups act as simple organizational units (containers) for labels. They do not have any settings or configurations associated with them.  This is a departure from what can be done with parent labels today
  • Labels will continue to be what users apply to content/files. Labels can either belong to a group or be stand alone, providing a significantly new flexibility in structuring sensitivity labels.

Why this matters?

  • Easier Management: Compliance Admins will no longer need to configure non-applicable parent labels, therefore simplifying the setup process.
  • Better Usability: End users will see a clearer, more structured labeling interface, reduce confusion, and assist with adoption of your information Protection posture.
  • More Flexibility: Labels can be grouped for better organization or remain independent, allowing you to adapt the structure to fit your organization’s needs.

How to prepare:

  1. Migration pathway – There is a supported migration of existing Parent/Sub Labels to Label Groups however, we  we strongly recommend that you test the migration using a test tenant because this process is irreversible. 
  2. Review Your Labels – Assess your current labeling structure and identify areas where grouping might help improve organization.
  3. Train Your Team – Make sure administrators understand how labels will be grouped moving forward.
  4. Update Documentation – Adjust internal guidelines and policies to reflect these upcoming changes.

Next Steps:

KiZAN has a team of data security consultants ready to assist your team with planning and preparing to make this transition a smooth one for your organization.  Don’t wait to start these discussions, get started today.  For more information Click here to connect with our team