Microsoft Purview Sensitivity Labels: Sensitivity label grouping modernization coming this fall (?)

on
There is a change coming to Microsoft Purview Information Protection that simplifies sensitivity label architecture. The goal is to make label management easier, more scalable, and less rigid for organizations. The new model will only include standalone labels and sublabels. Parent labels will be replaced by label groups, which act as organizational containers. These groups cannot be applied to content and have no actions or scope, but they retain color and priority for visual organization. Hopefully, this change will make it much easier to move labels around and make other changes in production: for example, converting a standalone label into a sublabel or moving sublabels between groups without breaking dependencies.  From my experience, this update solves one of the biggest challenges in large environments: rigid label hierarchies. The new dynamic model gives admins the agility they need to adapt quickly as compliance and business needs evolve. For admins, migration will be quic...

New Microsoft Loop workspace policy coming: Require Existing Microsoft 365 Group for New Loop workspaces

on

Microsoft is improving the security of Loop workspaces by giving admins the capability to connect new workspaces into existing Microsoft 365 Groups. This change will allow end-users to choose existing groups for managing new workspaces, providing a structured environment for collaboration. While this integration supports governance, it may challenge scenarios like automatic aggregation of Teams meeting content into a Loop workspace or creating short-term project workspaces. I recommend reading the following post on how aggregating teams meeting into loop workspaces works.

If organizations have separate workflows for creating and govern Microsoft 365 groups, now would be the time to look into them and see if they need to be updated to include Loop Workspaces (or allowing to add workspaces)

This update is currently planned to be complete by the end of April 2025 but keep an eye on Microsoft 365 Roadmap ID 422725 for changes.