Microsoft is making it easier for owners of Teams shared channels to request help if they run into a trust problem when adding a member from another domain. If Teams detects a problem with a missing trust, it flags the error to the channel owner and offers a link to a web page to seek additional support. Of course, the tenant might decline to trust the domain the channel owner wants to use, but that’s a different story.
Teams Shared Channels are a great way to collaborate across multiple Microsoft 365 tenants. From an administrative side, it’s nice to know about who’s connecting – who’s coming into your tenant to use a Teams shared channel and who’s leaving your tenant to share ideas in a Teams shared channel belonging to another tenant. This article explains how to retrieve that information from Azure AD shared user profiles.
This article explains how to populate the membership of a Teams shared channel using PowerShell. The idea is to create a shared channel that’s used for organization-wide communications, like a HR questions and answers channel. Alternatives like using a dynamic Azure AD group with a filter to find Teams users are also considered.
When a team owner or administrator archives a team, any shared or private channels in the team along with their SharePoint Online sites are archived and become read-only. This is fine if the team owner realizes the effect on these channels and their users, but problems might happen when team owners aren’t members of the channels and therefore don’t know of their existence. Unless of course they take the time to check using the Teams Admin Center or PowerShell, which is exactly what happens when archival occurs – or is it?
Teams shared channels are now in public preview, meaning that many organizations are trying them out to see how effective a means of collaboration these channels are. One of the administrative challenges of implementing shared channels for cross-tenant collaboration is knowing who uses the channels. An answer can be found in the Azure AD sign-in logs, but only after you go looking.
Teams Shared Channels will be available in public preview in March. Exciting as it is to get new functionality, shared channels come with their own challenges. For example, how do organizations deal with the fact that compliance processing occurs on the tenant which owns a shared channel? Backup is another challenge. Teams has always been complex to backup, but how will backup vendors handle the new channels?
On February 7, Microsoft announced the preview of Azure AD cross-tenant access, a new capability to allow users obtain credentials in their home tenant and use these credentials to access resources in other Microsoft 365 organizations. Microsoft Teams Connect (aka shared channels) is likely the first app to use cross-tenant access, with public preview of that feature expected in March 2022.
The latest version of the SharePoint Online PowerShell module reveals some new site properties to inform administrators if sites are connected to teams or even team channels (both private and shared). There’s also some changes coming to the SharePoint Online admin center, all of which are very useful in terms of tracking the sites used by Teams.
