Mar 02 2021 09:55 AM
Mar 02 2021 09:55 AM
Microsoft Teams Connect, a new way of collaboration based on federated shared channels, is now in private preview and should be available later in 2021. The best thing about shared channels is that you don’t need to switch tenants to access a channel in another tenant. Azure B2B collaboration (guest accounts) is still important, but this is a brand new way of working that should be very popular.
Apr 15 2021 12:49 AM
Really excited about these new sharing possibilities!
One thing I don't understand though, is since the external users you share a channel with, don't need to be guests on your platform, how would the invitation process look and how would they access the Team if they don't use M365 on their end?
Apr 15 2021 01:35 AM
Apr 15 2021 02:58 AM
Apr 15 2021 07:23 AM
Apr 22 2021 11:26 PM
Apr 23 2021 01:34 AM
Apr 23 2021 02:17 AM
Apr 23 2021 04:48 AM
May 21 2021 10:47 AM - edited May 21 2021 10:53 AM
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...
May 24 2021 01:15 AM
May 26 2021 01:00 AM
May 26 2021 05:29 AM
May 26 2021 05:50 AM
May 26 2021 05:54 AM - edited May 26 2021 05:55 AM
in addition to my earlier post I discovered a way to add members and owners to a private channel when in the Admin Center. This makes it easier to grant access when needed!
So I (as an admin) now have a way to see if there are private channels and in case of need for support can also get access without the need for an user to grant it (which could have been difficult if no owners are left ;) )
Seek, ask and you will find an answer hahaha
Thanks @Tony Redmond for your help in easily discovering them via Powershell btw
May 26 2021 06:13 AM
Jun 01 2021 08:07 PM
Given the ability to share a channel to an external user, is there anything to prevent us from adding a power bi app into a tab on that channel and thus allowing external users to see the reports?
Currently I use the "app owns data/embedded" setup with a external website (time-consuming but works well).
Having externals authenticated from their own tenancy and invited into a Channel might I think open up a huge time-saver.
interested if anyone knows if my thoughts are on track or not?
Jun 02 2021 02:32 AM