Admin Guide: Setting Up Shared Channels in Teams - Part 1

by HubSite 365 about REgarding 365

Pro UserTeams ChannelsTeams Channels

Microsoft Expert explores the newly launched Teams Shared Channels - showing its usefulness, limitations, and potential issues in this insightful review.

Understanding the Implementation and Implications of Microsoft Teams Shared Channels

The focus of the blog post by REgarding 365 is the public preview release of Microsoft Team Connect, often termed as Shared Teams Channels. This feature, labeled as a potential revolution in collaboration strategies, has been keenly awaited by many users.

Upon first use, an unexpected revelation was that an external collaboration does not permit the coupling of older guests with the Azure B2B external collaboration. Interestingly, eliminating the creation of an Office 365 group is a novel aspect of these shared channels that distinguishes them from private channels.

The absence of a group may curtail certain scenarios as shared channels lack an associated security group that could potentially allow access to other systems.

A potential set-back may arise if the owner of the Team and the Shared Channel are not the same person. Specifically, if the team owner transfers ownership to a non-member and removes themselves, the Team owner loses visibility of the Shared Channel. In contrast, the new channel owner and its members can operate freely, which highlights the possibility of losing important data unknowingly.

The scenario does not remain a bed of roses when the Team owner decides to archive the team. Many users may face the unpleasant surprise of finding their Shared Channels archived along with the Team. Also, the absence of notification can leave the users unaware of their archived workspace.

The blog not only explores the issue of dilemma, but also provides solution through IT admin team who might instruct the original team owner to unarchive the team, making it visible and workable for the Shared Channel owners.

Yet, it isn’t a permanent solution. A permanent bind to the original team and the Channel can leave users stuck. Losing tracks of the original Team can be a big question mark, and users may require a PowerShell script to locate the concerned Channel by the name.

Despite the possible limitations and challenges noted, these shared channels are still considered as excellent features. These tools cope up with several customer needs since a long time. However, an in-depth understanding and evaluation are advised before rolling them out completely.

The author also expresses concern that Microsoft chose to automatically switch on this feature, rather than leaving it to administrators to choose who should have access to this new functionality.

Teams Channels: A Deeper Dive

The idea behind these shared channels is to enhance collaboration via a shared workspace. Yet, it's clear from this discussion that proper implementation and control of these features are essential to prevent loss of data and access. The issue of a Shared Channel being permanently tied to the initial team is notably significant. This could lead to a surge in the number of active Teams Channels for the sole reason that they contain Shared Channels. Furthermore, not having a dedicated security group may limit interoperability with other systems, and thus reduce potential productivity advantages. The feature, still in public preview, holds a lot of potential. Nevertheless, further exploration and understanding seem necessary for effective deployment.

Find More Details Here.

Read the full article Teams Shared channels (PART 1) - The Admin Site

Teams Channels - Admin Guide: Setting Up Shared Channels in Teams - Part 1

Learn about Teams Shared channels (PART 1) - The Admin Site

Unearthing the possibilities of Microsoft Team Connect, commonly referred to as shared channels, calls for an insightful examination of this new aspect of collaboration. The intrigue peaks when you realize that the creation of shared channels does not generate an Office 365 group. Consequently, membership can be efficiently controlled through the Teams application, maintaining a sleek sight for admins with no clutter in Azure Active Directory.

However, this absence of an associated group poses a limitation in providing access through security groups in different systems. A scenario that underscores this absence can render the shared channel invisible to the original team owners. The primary owner, after delegating the channel's ownership to an external member and removing themselves from the channel, is unable to view it.

A sudden disappearing act by the shared channel can indeed trigger panic and confusion. This unforeseen circumstance beckons the attention of IT admins for swift troubleshooting. A temporary solution could involve the original team owner unarchiving the team, thus allowing the shared channel owner and members to regain visibility and resume their activities.

However, this remedy falls short of being a permanent solution. The existence of a shared channel remains embedded in the team where it was born, indicating that Teams could potentially have a longer lifecycle, given their Shared channels. This, in turn, could result in a sprawl.
Finding the root team of a shared channel, especially when the channel owner is clueless about it, could pose a challenge for the Teams admin who might need to execute a PowerShell script to seek out the elusive channel.

Consequently, Tony Redmond's contribution in Office 365 for IT Pro’s offers valuable insights for IT admins grappling with such scenarios. Despite being in its infancy, realizing the fullest potential of shared channels requires a closer look into its implications and a finer understanding of its operations.

Albeit this being my initial encounter with the shared channels, further probing and meticulous examination of the documentation is crucial to gain an exhaustive understanding. I encourage users to exercise caution and perform thorough checks on shared channels, comprehending both its merits and limitations before embarking on this new venture.

Despite shared channels being a commendable feature addressing longstanding customer requests, its emergent nature naturally comes with potential limits and issues. Thus, comprehension and adjustment according to your environmental needs become vital. I am eagerly looking forward to identifying situations where shared channels shine brightest.

Wrapping up, let's bear in mind that these are still early days with shared channels. There's always room for discussion, learning, and sharing. Being open and receptive to feedback is part of the learning curve. Let's be patient with the process and navigate this path of exploration together.

Keywords

Teams Shared Channels, Admin Site, Collaboration Tools, Microsoft Teams, Shared Channels Part 1, Business Collaboration, Team Management, Teams Admin, Channel Administration, Teams Shared Channels Guide