Unable to share externally on Shared Channels
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?Microsoft Teams: specifications and possibilities of the shared channels
Have you been waiting for the Microsoft Teams Shared Channels? They are now live! Most of us have struggled without it for years (sharing, scaling, and replicating). Before we try to understand what we can do with it, we need to focus on its features in the table below.Teams Public Preview Office Hours - Teams Connect Shared Channels
Welcome everyone! Please post all your Teams Connect shared channels questions and we will endeavor to answer them all as quickly as possible. Your trusty Microsoft Teams engineering team is here live for the next hour to respond and engage with you on any comments, concerns, problems, suggestions, questions, or confusions related to your Shared Channels experiences in Public Preview. What is Microsoft Teams Connect shared channels? With Microsoft Teams Connect we are making it easier to collaborate with anyone outside your organization. Teams Connect is designed to let you establish seamless, secure and trusted collaboration across multiple companies in a matter of minutes, where everyone can work as one extended team while staying in their own Teams environment without ever needing to switch tenants. Teams Connect shared channels enables you to collaborate with people internal and external to the organization from a shared workspace. When can we use Shared Channels? Shared Channels are currently live in Public Preview. Shared Channels are on the Roadmap to be Generally Available in July 2022. Microsoft Teams: Teams Connect shared How do we learn more and get started? Seamless external collaboration with Microsoft Teams Connect, shared channels - Events | Microsoft Docs Shared Channels for users Microsoft 365 admin center Thank you everyone for joining us today and I look forward to your posts!!! -Microsoft Teams Connect Engineering team
Teams Public Preview Office Hours - Teams Connect Shared Channels
Office Hours will take place on the Microsoft Teams Public Preview discussion page. Please join us there on May 31, 2022 between 9-10amPT. Shared channels is in public preview. We are excited to see the response from our Public preview community and thank you for your great feedback. We are organizing a live Q&A on Teams Connect shared channels here on the Tech Community. We will have product teams behind shared channels answering your questions on shared channels live. How do office hours work? Simply visit the Microsoft Teams Public Preview page on Tech Community and click Start a New Discussion to submit your question. Our team of Shared channels experts will post answers as quickly as possible. All the questions and answers are viewable by anyone, even after the event. How do I participate? Office hours are text-based; there is no audio or virtual meeting component. To post a question, you just need to be a member of the Tech Community. If you haven’t already signed up, click Sign In in the top right corner of this site to join the Tech Community today.The issue with channel sites (private and shared channels in Teams)
Hi, I'd like to know of your opinions, experiences, practices, decisions you've made concerning private and shared channels in teams. In my company, we are progressively migrating to Teams from Webex. Users have started creating private and shared channels. My own practice and recommendation to users has been to get a new team created when a different list of users need private access to conversations or documents, instead of a private or shared channel. My reasons are as follow: Rigidity: The SharePoint channel site created cannot follow its own direction if needs arise. It is locked with the parent site. Say we want to reorganize teams and work units, and we want to join a SharePoint channel site with a another hub − we can't, at least not easily. And now the rigidity of subsites is brought back! And anyway, the conversations are also locked with the parent team! It can't be made independent. Lack of control: Control is removed once again from us, the admins − Microsoft loves to allow users to do everything they want and foster chaotic environments. We have disabled group creation and sites creation for all but a few in order to manage the information environment, try to restrict the scattering of important documents, and make things clearer for users. But with private and shared channels, end users can now create new SharePoint sites. As the documents management specialist, I can't easily see where documents end up. And when I export the list of sites to Excel, the channel sites don't appear! So I can't really see which sites take a lot of storage space. Lack of features: Let's say the management team of a department created a private channel for management topics in the department team, and after several months of active use, they now decide they'd like to manage tasks in Planner − tasks that should be private to the management team. They can't, should have created a M365 group for that! Once again, it is rigid. Troubles for the admin: I want to apply a change to all SharePoint sites − so I type a PowerShell command that will apply to all sites. But it won't apply to all sites: not the channel sites. Also, ShareGate can't seem to get the access matrix of channel sites − it returns errors for them. However, when I turn to the Web for advice with this issue, I only find appreciation for private and shared channels, and none of my concerns addressed. Apparently, they allow to avoid the multiplication of teams. However, I'm not sure how multiplying channels is better than multiplying teams. With both teams and channels, users can hide or show them, and as a team always have a channel, they can disable notifications. Maybe I should just deal with and accept the rigidity, lack of M365 features and troubles for the admin. Maybe I should approach the control of the information architecture and documents differently. What is your view on that? Did you have any issues with channel sites, and if yes, how do you deal with them? Did you discourage or prevent the creation of private and shared channels? Have you reconsidered your decision? Do you see private and shared channels as a very useful feature, and if so, why? I'm interested in all experiences on this topic and I'm thankful for all answers.
