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

Name vs. ip.addr. in the year 2008?

on
Here’s a problem I thought was history. In an environment with DHCP and DNS, I thought it was impossible to get things wrong. But obviously, I am the one who’s wrong.

I have been troubleshooting a Voicemail system with strange symptoms. Where among the strange log messages were: Could not locate %dbname% on server %hostname%. The database was running on the same server as the voicemail application, and name resolution was not an issue. Or so I thought. I tested name resolution through nslookup and tried to ping by using various names (hostname and fqdn). Everything seemed to be working. As a last desperate test, I changed the configuration in several places, to reflect the server’s ip-address instead of it’s hostname (inserted to the config by default during installation). Wonders of all wonders this solved my problems.