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

Best practice configurations dashboard in Teams

on
For me, this is a tale as old as time, at least as long as I have been working with real-time media. Large organizations typically have complex networks with switches, routers, and firewalls. These networks can be challenging to troubleshoot when issues arise.

There are various reasons for failures, and sometimes resolving one issue leads to the emergence of another. Microsoft aims to help administrators in understanding these issues better by collecting end-user diagnostics and presenting them in a new tool called the "Best Practice Configuration Dashboard."

In my opinion, this tool will not solve all your problems, and you will still need to identify where in the network the issues may lie. However, it will provide a better understanding of some of the most basic issues. The Dashboard currently offers insights into client versioning (suggesting updates), explains which ports are being blocked for end-users (causing failures or reduced quality and functionality), and detects if VPNs are in use, suggesting split tunneling where appropriate.

This feature is mentioned in Roadmap ID 421185 and is expected to roll out at the end of this month and onward.