Is it still not supported for a GCC and Commercial tenant to use a shared channel in teams?

Hi @Christine Neuhaus, 

Good day to you.

Thank you for reaching out, and I truly appreciate you sharing the details of your situation. 

After reviewing your request carefully, the setup you described isn’t supported at this time. 

Microsoft Teams Shared Channels don’t support adding external users through the traditional Guest (B2B Collaboration) approach. To invite people outside your organization into a Shared Channel, you must use Microsoft Entra B2B Direct Connect. However, B2B Direct Connect currently doesn’t support “cross-cloud” scenarios, so it can’t be used for a Commercial & GCC setup like yours. 

Depending on what you’re trying to prioritize, here are a couple of practical alternatives you might consider: 

Option 1: Use a Team / Standard Channel with Guest access 

• The Commercial partner would create a Team (or Standard channel) in their tenant and invite your GCC users as Guests using cross-cloud B2B Collaboration.  
• Files will remain in the Commercial tenant’s SharePoint, and the setup is supported via Microsoft cloud settings and cross-tenant access settings for B2B collaboration. 

However, please note that the end-user experience will be “guest-style” (it may involve tenant switching depending on configuration), and it also introduces guest lifecycle management plus compliance considerations. 

Option 2: Share SharePoint site/folder/files directly 
If the main objective is simply to store and share content in the Commercial tenant’s SharePoint, the Commercial partner can share a SharePoint site, folder, or specific files directly to GCC users through cross-cloud B2B Collaboration (guest).  

This is a supported cross-cloud scenario for SharePoint sharing. 

For additional information, you can refer to these articles:   

• Cross-cloud settings (B2B Collaboration)  
• Microsoft Entra B2B in government and national clouds  
• Cross-tenant access settings - Microsoft Entra External ID | Microsoft Learn  

Submit Feedback to Microsoft 

As a forum moderator, I hope you understand that I don’t have the ability to modify or escalate product issues directly. However, I strongly recommend submitting your feedback through the Microsoft Teams · Community. This is the most effective way to ensure your voice reaches the product team and can be considered for future improvements.  

Once you've submitted your feedback, feel free to share the link here in the comments. I’ll be happy to upvote it to help bring more visibility.   

If you are unable to submit feedback from your side, please let me know and I will be happy to submit it on your behalf. 

Additionally, since many other users have expressed similar concerns but may not know where to submit feedback, if my response has helped you better understand the situation and guided you toward a possible next step, please mark it as the "Accepted Answer". Your action will help pin this post to the top, making it easier for others in the community who are experiencing the same issue to find your feedback and support it.    

I hope this information is helpful. Should you have any further questions or need additional assistance, please feel free to share them in the comment below. I'm always happy to help. 

Thank you again for your time and for raising this important usability concern. 

Wishing you all the best. 

If you have any extra questions about this answer, please click "Comment".  

Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.     

This scenario is still not supported.

Shared channels use Microsoft Entra B2B direct connect, and for government clouds there are architectural separation constraints between GCC (and especially GCC High/DoD) and commercial tenants. The documented behavior for GCC High and DoD explicitly notes differences and limitations in cross-tenant/B2B scenarios compared to commercial, and shared channels with external participants require compatible cross-tenant access in Microsoft Entra ID on both sides. In GCC environments, external collaboration is restricted to other compatible government tenants; commercial–GCC shared channels are not supported.

In practice, this means a commercial Microsoft 365 tenant cannot create a Teams shared channel and add users from a GCC tenant via B2B direct connect so that data resides only in the commercial tenant’s SharePoint. Collaboration between GCC and commercial organizations must use other supported methods (for example, guest access in standard channels or other approved external sharing patterns), not Teams shared channels.

References:

• Shared channels in Microsoft Teams
• IT Admins - Overview of external collaboration options in Microsoft 365
• Office 365 GCC High and DoD
• B2B direct connect overview