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

A couple of new Teams features an admin might want to know about

 A couple of policies have received new settings or defaults over the past couple of weeks, and here are some of those i think you might want to look into.

Message translation:
Message translation has now been set to default "on" in the global user policy. If your users have assigned custom policies, these might not have that setting turned on by default. If you want to allow your users this handy feature, Make sure to go through your policies according to this guide.

Allow more badges in the Praise app:
You can add a little flare to the praise app by adding more custom badges for your organization. But this requires the admin to add these badges in the Teams Admin portal. This feature should be rolling out by the end of September.

Meeting policy and meeting expiration:
Teams is introducing meeting expiration to their meeting policies. Which to my understanding will ensure all meetings created by a user will no longer be accessible to anyone. Previously, the meeting policy would only affect new meetings after the policy was implemented, but the new way it will work is to expire any previously created meeting by the affected user. Read more about how this works here.

**Updated 30/8/2020 with a correct link to the meeting expiration**