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

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

Issue with enable-csuer when the user first name contain spaces

I have run into an issue with the set-csuser command in a few deployments. The error occurs when I try to use set-csuser with the "-sipaddresstype firstlastname" switch.


If I changed the -sipaddresstype from "firstlastname" to "emailaddress", I was able to use the script to enable the same user.

It turned out this user had two first names (with a space between) in the fname property in AD (fname="First Name"). If I removed one of them (fname="First"), or used a hyphen between them (fname="First-Name"), the script started working again.