Forum Discussion
Microsoft Teams Connect aka Shared Channels Coming Later in 2021
Yes, however, not all "Admins" are profficient in PowerShell, nor should they have to be. I agree with DebbieHere and am concerned about the governance of this. Why not teach users to work and structure teams in Teams optimally, instead of running head over heals to solve something that could be easily solved with current solution? For example, if I am running a real estate department that are managing lots of properties and different suppliers managing these; i would create a team in Teams for my internal "Real estate department" and any internal work should be done there, and access only for internal resources. Then I would create a team in Teams for "Real Estate Suppliers" and create some common channels where e.g. policies, templates, routines, etc. could be shared and available. Then I would create a private channel for each supplier, where internal resources could have access to all private channels, but each supplier only their own and the common channels. This way I do not see any need for a shared channel in addition to this. If I need then to share a document from one of these channels, I can Open in SharePoint and share the specific document by using the "Share" function. Please let me know if I have missed some info here, right now I just see this is going to be a headache to administer access to...
- Hi TonyRedmond, yes, and after further investigation and thinking about it, I realized the benefits; as shared channels can make it easier for collaboration across different companies, which many times is the case. Shared channels solves the tenant switching issue, you can mount a channel in an existing team in your own tenant, no need for tenant switching. Perhaps I had a hint of getting "old and set" when putting on the hand-breaks on this one! 😉 Still, we should work on how to advice admins to keep track of all SPO-sites, from a governance perspective, I guess this will also improve over time.
