Nov 05 2019 03:58 AM
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-up, I'll go into how to create and manage private channels in a Teams deployment and discuss some of the issues you should consider when using this new feature.
Nov 05 2019 06:22 AM
@Tony Redmond, looking forward to private channels in our tenant. It has been a big request among our users.
Nov 07 2019 02:30 AM
Hello @Tony Redmond
Very interesting, but could you tell me how it would be possible to migrate our public channels that are already created to PRIVATE please? PowerShell?
Nov 07 2019 02:35 AM
@Sofianeda1st No out of the box way to export channel content and you can't convert a standard channel to private I'm afraid
Nov 13 2019 04:49 AM
Nov 13 2019 12:05 PM
Nov 13 2019 12:06 PM
@Forrest Hoffman There is a mechanism to ensure that a private channel always has an owner. It's imperfect and flawed but should be improved over time. See https://www.petri.com/managing-teams-private-channels for details.
Nov 13 2019 12:17 PM
Nov 15 2019 08:18 AM
Nov 15 2019 08:52 AM
@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.
Nov 15 2019 08:59 AM
Nov 15 2019 09:05 AM
@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.