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

An "important" lesson from day one at Lync 2013 Ignite

on
Lync 2013 comes with new features and new functionality. To support all of these new functions, there has been introduced a big set of new PowerShell cmdlets.
This didn't come as a surprise to me, as I have been playing around with the preview for a bit, and I have been reading Tom Arbuthnot's excellent post on the subject.
One of these "important" new cmdlets is the "Invoke-CsManagementServerFailover" command. Why?
Well, If you are anything like me, you type as little as possible, and you use the TAB as much as possible, you might to look out for this one. My "default" is to type "invoke-csma" + TAB. to get to the Invoke-"CsManagementStoreReplication" and then hit enter.

Unless I now hit enter twice, i will start the process of failing over the CMS.

I have no idea of how many times I'll fail over the CMS before I actually learn to hit tab twice, but I know I'll get there in the end.

So what was the important lesson here? It's not what you have to learn, but what you have to unlearn :)

For future reference, here's a list of all the cmdlets for Lync 2013