Forum Discussion
Unable to share externally on Shared Channels
I have the same issue and can't seem to find a work around. Agree this is a huge loss or productivity and a major limiation on an expensive subscription product. Any resolutions?
Hi . After much confusion and lots of research, I now get where this is coming from and have it working well across multiple tenants. I wrote a short blog on the subject a while back which may help: Private and Shared Channels in Teams | LinkedIn.
You basically need to ensure external sharing is turned on for the Teams' SharePoint site BEFORE creating any shared channels (if you created shared channels whilst external sharing was turned off you'll need to re-create the shared channels unfortunately).
If external sharing is turned on, you then 'simply' need to configure Azure AD B2B Direct Connect in any tenants whose users need to access a shared channel. This takes 3 minutes and can be done by tenant admins - I usually just jump on a call with the other tenant admins and we set it up together using the following instructions:
Collaborate with external participants in a shared channel | Microsoft Docs
I get why it's built this way, as opposed to external or Guest access where everything is within your own control. With shared channels they effectively sit within both tenants so for security reasons both tenants have to unlock the door.
I hope this helps and you can get the benefits of shared channels soon as they really can transform how organisations can more easily collaborate.
Sorry, just for clarifying. This command
Set-PnPTenantSite -Url $SiteURL -SharingCapability ExternalUserSharingOnly
does not work if you does not setup previosly a B2B connection?
We want at least give access to the shared channel siteAX_Rookie exactly. This is just a show stopper as this slows down the process really badly. I have to get the Consult to trust our domain, which takes a few weeks for them to implement after going through their IT approvals, and I need to get our IT to approve their domain, which again takes weeks due to our internal approval processes in place.
- Totally agree. I had to first of all figure out that this is even possible (with this workaround), which as we all have found, is a ton of Googling. Then I have to help my two client companies to understand it, explain to both of their IT leaders, and then walk them through making the changes. Completely ridiculous...when the label is a "shared" channel, and you need to do this level of detective work.
Hi OzOscroft , so in order to allow external users to access a shared channel is always needed to setup a B2B connection? If yes, this is a huge lost of functionallity. Private channels allow it. How it is posssible shared channels that supposedly ara a step foward in terms of collaboration don't allow sharing with externals the same way they allow with private channels. Can't believe it
