Forum Discussion
TonyRedmond
Nov 05, 2019MVP
Introducing Teams Private Channels
Microsoft launched private channels for Teams at the Ignite conference. This article describes the architecture and structure of private channels and discusses their intended usage. In a follow-u...
Ian Mears
Nov 15, 2019Copper Contributor
After doing a lot of reading it looks like it isn’t private channels that’s caused the change to classification display but more likely the new sensitivity labels for groups. Not had any announcement in the tenant but I assume that as it’s now in preview it’s just there for everyone and teams has been updated to cater for it, regardless of whether it’s enabled or not.
TonyRedmond
Nov 15, 2019MVP
Ian Mears Sensitivity labels support in Teams starts in preview on November 20. https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-teams-groups-sites
When labels are used, they replace the text-only classification labels defined in the Azure AD policy for Office 365 Groups. As such, they have no effect on private channels except that the classification is one of the properties synchronized from the parent team to the private channel.
- Ian MearsNov 15, 2019Copper ContributorThat’s interesting because we are seeing a change already. The old classification is no longer displaying in any Team and we haven’t enabled sensitivity labels.
- TonyRedmondNov 15, 2019MVP
Ian Mears Yep. Software is deployed at different speeds across Office 365. I see sensitivity labels in Teams in the EMEA datacenter region, but there's some bits still to drop because although I can see the labels, I can't apply them to Teams yet.