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

Teams native federation being rolled out

on
This feature was announced earlier this year, but have taken some time to get implemented. This feature will give users a richer experience when chatting with users outside of the home tenant with federated functionality.

However, not all users are eligible for this feature. The official documentation has been updated with a description of how it is expected to work: Microsoft Docs

The short story is: Both users must be in a tenant set in "Teams Only" mode, and have these same settings themselves. You know this is the case when you can use features like @mentions, rich text and emojis in the chat.

According to the road-map, this feature should be well on the way to your tenants and land no later than "early December": 52394