Jul 13 2022 08:10 AM
We are unable to share files and folders on shared channels with external users. We get the following message when trying share with an external email address:
“Your org doesn't allow sharing with these people. To continue sharing, remove the highlighted recipients.”
We are able to share externally on Standard and Private channels.
Guest Access is On in the Teams admin console:
In the SharePoint admin console > Policies > Sharing > External Sharing, both SharePoint and OneDrive are set to “New and existing guests”.
In the SharePoint admin console > Sites > Active Sites, the team site in question has External Sharing set to “This site can be shared with new and existing guests”. On the General channel we are able to share with external users.
However, on the shared channel sites, External Sharing defaulted to “This site can't be shared externally”. There is no edit button. As a workaround, I leveraged PNP PowerShell to enable external sharing with the following command:
Set-PnPTenantSite -Url $SiteURL -SharingCapability ExternalUserSharingOnly
The SharePoint admin console now indicates that I can share externally on the shared channel site. External Sharing shows “This site can be shared with new and existing guests”.
However, I still receive the aforementioned error when trying to share externally. What am I missing? How do I enable external sharing on shared channel sites? Why is this not consistent with SharePoint, OneDrive, and Teams standard/private channels?
Jul 31 2022 04:57 PM
As I am off soon will reach out to some of my community friends to pick up
@adam deltinger @Chris Webb @Juan Carlos González Martín - you guys got any idea as I know you have worked with Shared Channels prior
Best, Chris
Jul 31 2022 09:13 PM
Jul 31 2022 11:07 PM
Hi Ryan,
All you have tried here seems to be right and I would recommend to wait some time untill the changes in the SPO site are propagated in the backend. Anyway, if you click on the view 2 channel sites in the main site card, you should be able also to check the settings for any channel site linked to that main site and make changes there.
Another important thing here: Is B2B Direct Connect configured behind the scenes for the shared channel? I think the problem you are experiencing could be related to the fact that Shared Channels relies on B2B Direct Connect even for sharing the SPO site being used....I have just tested this on a demo tenant and I can share documentation with users belonging to tenants configured in B2B Direct Connect, but I cannot if they belong to tenants not configured.
Aug 01 2022 11:29 PM
External access is set to allow "All external domains". External sharing works fine on standard and private team sites, as well as general SharePoint sites and OneDrive.
Aug 01 2022 11:39 PM
Aug 02 2022 02:23 PM
Aug 02 2022 04:46 PM
@ryanmillar, you should check Azure Active Directory > External Identities | Cross-tenant access settings to enable conection between tenants, it is no only Teams Admin Portal setting. (Collaborate with external participants in a shared channel | Microsoft Docs)
Aug 02 2022 06:37 PM
Aug 03 2022 03:15 AM
The B2B settings should have propagated by now, but still no luck. Here are the updated settings as well as others I had now shown before:
Cross-tenant access settings:
External collaboration settings:
Global Teams policy
Trying to share from SharePoint on a shared channel's site is unchanged. I still get the following message for external email addresses:
Your organization's policies don't allow you to share with these users. Go to External Sharing in the Office 365 admin center to enable it.
If I click on "Share with people" on a shared channel and enter an external email address, I get "We didn't find any matches". The same occurs if I enter the email address of an existing guest account.
However, I can add an external user to the Team.
When I sign into Teams as the external user, I can see the team and the General channel, but not the Shared channel, which is shared with the team.
Are there any other settings I could be missing?
Thanks,
Ryan
Aug 16 2022 04:09 AM
Aug 16 2022 04:28 AM
Aug 18 2022 07:11 PM
Aug 26 2022 02:03 AM
@ryanmillar This could be resolved when you set it to "All External Domains" in the external user access settings. In general, external user access settings must be turned on for external collaboration in Microsoft Teams. Basically, there are two prerequisites for establishing MS Teams' external collaboration between organizations.
Step 1 - Verifying External User Access Configuration
Step 2 – Enabling Microsoft Teams Public Preview
You shall make sure to verify the external user access configuration and then attempt to share files and folders on shared channels with external users.
Aug 26 2022 02:22 AM
Sep 15 2022 12:17 PM
I have exactly the same issue as @ryanmillar , and I have multiple clients who need this for various use cases. My external users don't have access to a Teams admin panel, and won't have a clue what B2B settings are. They want to click on a link, and come to the Team.
I have moved thousands of users to Teams in the past year...and our expectation was that Teams was intended to eventually become fully functional cross-org.
As I understand it now, we can
I need to be able to
Sep 29 2022 05:14 PM
Nov 26 2022 04:06 PM
Nov 30 2022 01:17 AM
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.