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...

Data Lifecycle Management: Separate Copilot retention policies from Teams chats

on

In a previous post I mentioned how Microsoft is adding the capability to use Purview Data Loss Prevention on Copilot to block certain information from surfacing for the user.

Now, Microsoft is adding Copilot to it's retention policy controls, and starting mid-February, public preview tenants can start exploringthis new feature.

Admins will be able to create separate retention policies for Microsoft Teams chats and Microsoft 365 Copilot interactions, and allows for a more tailored data management. The feature will of course require that the targeted users have Microsoft 365 Copilot license. 

According to the message center, the public preview will be during February, and we can hope for a general release sometime in March. The feature will be available by default, but policies will have to be set up.