MC1111778 - Microsoft Purview | Information Protection: Sensitivity label grouping modernization

Updated March 30, 2026: We have updated the timeline. Thank you for your patience. 

Coming soon to Microsoft Purview | Information Protection: To help improve label usability and configuration, the sensitivity labeling scheme will be simplified to only consist of labels and label groupings.

This move to a dynamic architecture will make it easier to move a child label into label groups, out of label groups, and between label groups without losing referential integrity, allowing customers to better scale and reorganize their labels across their entire data estate.

Tenants in scope for manual migration to the new label scheme will see a message on the Sensitivity labels page in the Purview portal, where the tenant admin can access a simple manual migration wizard to opt in to the migration, which should complete in less than a few minutes or even seconds, depending on the label configuration.

If you do not see this message, your tenant does not meet the criteria for manual migration (your tenant lacks applicable parent labels). This new label scheme will be rolled out to your tenant in the coming months. (and we will send a separate MC post in advance).

This message is associated with Microsoft 365 Roadmap ID 386900.

When this will happen:

Public Preview (Worldwide): We will begin rolling out earlyModern labels have been in Public Preview since July 20257th 2025. This post announces the rollout of modern label scheme to new tenants and expect to complete by late August 2025.tenants with applicable parents.

General Availability (Worldwide): We will communicatebegin rolling out early December 2025 and expect to be completed by early May 2026 (previously mid-March). As part of GA, customers with non-applicable parents will be auto migrated to the planmodern label scheme while migration for General Availability customers with applicable parents will continue to be opt-in a future post.for 12 months post-GA. We will auto-migrate customers with applicable parents to the modern label scheme once the 12-month extension ends. 

How this will affect your organization:

During migration, to ensure label scoping integrity, any applicable parent label will be converted to a child label under a new label group, and then both parent and child label will have the same display name as the original parent label. Non-applicable parent labels will automatically be converted to label groups.

A parent label is deemed applicable if it has a different scope from any of its children, has label actions, or is published separately from its children.

The manual migration wizard provides a preview of the migrated scheme so admins can better understand how their sensitivity label scheme will change after the migration.

After migration, admins are free to make changes to their migrated label scheme, including unpublishing applicable parent labels that were converted to children during migration.

Users will not notice any change in how labels are viewed or applied. This change will be on by default.

Example of a migrated label scheme:

What you need to do to prepare:

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your tenant’s label scheme to ensure it is up to date. You may want to notify your admins about this change and update any relevant documentation.

Optionally, before you migrate your production tenant, consider migrating a test tenant configured with a label scheme that is representative of your production tenant, to become familiar with the migration process and the modern label scheme.

Learn more: Learn about sensitivity labels | Microsoft Learn