Discrepancy in External Sharing: "Anyone" links unavailable in Shared Channel sites despite Admin Center configuration and recent functionality.

Question

"I am experiencing a functional discrepancy regarding external file sharing within Teams Shared Channels.

While our global SharePoint Admin settings are set to allow 'Anyone' links, and this setting is also enabled for the specific underlying SharePoint site associated with our Shared Channel, the 'Anyone' option has recently become missing from the sharing dialog.

Curiously, this feature was functional for us just a few weeks ago. We need to distribute documents to approximately 35,000 external recipients and cannot manually input individual email addresses.

Could you please clarify:

1. Why does the SharePoint Admin Center still permit the 'Anyone' toggle for Shared Channel sites if the Teams governance layer explicitly blocks it?
2. Why was this functionality active recently but has since been revoked?
3. Is there a specific Microsoft Entra B2B or Cross-Tenant Access policy that recently overrode these site-level settings in early 2026?
4. What is the recommended 'authenticated-lite' method for sharing a single document with a mass audience (30,000+) from a Shared Channel environment?" More Context: We have a team created and we have channels within such teams, the general channels are set to allow sharing of files just within our organization, the shared channel is set to allow sending to anyone (which was working perfectly untill recently), the private chanell are private to specified people. Recently, we've had the shared to "anyone" option disappeared within the teams shared channel without any notice. The same when we check in the specific sharepoint too. NB: We want to be able to perform these sharing functions within a dedicated channel within a team. We would not like to recreate a separate sharepoint for this. Currently exploring private channels and set the sharing permission to anyone, but we can not change an existing shared channel to private. I am also wondering how to prevent recreating links and preserve already shared documents.

Answer 1

Microsoft's recent January 2026 implementation of a service side update to implement a backend Teams governance enforcement change to remove client's ability to control and allow (or not) anonymous (“Anyone”) sharing of files and folders from Shared Channels is problematic. This should not be a choice Microsoft makes for its clients but a client choice on how they choose to configure their Teams instance.

Shared channels are created to allow for sharing with individuals (and teams) that are not a member of the specific Microsoft team where the channel is create. The whole idea of a shared channel is to share with others and not allowing anyone links for sharing of files and folders with external parties that do not have to be members of the given Team is an essential business need.

Our organization personally has 100s of shared channels where we collaborate have allowed external members (auditors, lawyers, external partners/stakeholders) access to select files or folders. This needs to continue to be allowed. It is not realistic to make the varying organizations and individual emails addresses guests in our entra environment or specifically name every person on the other side who may need access to a file or folder - they need the ability to access the file or share the link with colleagues on their side. Similarly, suggesting that we should use a communications side completely undermines the point of uses Teams channels and document shares for collaboration with internal and external audiences.

I could understand this setting change for a private channel but it makes no sense for Shared Channels when intent is to be able to share with other audiences. I'm hopeful Microsoft will roll back the change asap.

Answer 2

Dear Abraham Yawson,

Thank you for posting your question on the Microsoft Q&A forum.

Regarding your concerns, you can refer to the information below:

1/ Why does SharePoint Admin Center still allow “Anyone” for Shared Channel sites?

The SharePoint Admin Center reflects site-level sharing capability, but Teams Shared Channels enforce stricter access rules at the Teams service layer. As a result, the “Anyone” toggle remains visible in SharePoint, even though Teams explicitly blocks anonymous sharing for Shared Channel content.

2/ Why did this work recently but is now revoked?

Microsoft implemented a backend Teams governance enforcement change that removed anonymous (“Anyone”) sharing from Shared Channels. This was a service-side update, not a tenant configuration change.

3/ Did Entra B2B or Cross-Tenant Access policies override this in early 2026?

No. Entra B2B and Cross-Tenant Access policies govern authenticated external users, not anonymous links. The restriction is enforced by the Teams Shared Channel architecture itself, independent of Entra or SharePoint site-level sharing policies.

4/ What is the recommended “authenticated-lite” method for mass sharing from a Shared Channel?

As Teams Shared Channels are no longer suitable for large-scale external distribution, you can consider using a SharePoint Communication Site with “Anyone” links for mass sharing, while keeping Teams for collaboration.

Additional clarification:

• Anonymous (“Anyone”) sharing is no longer supported in Microsoft Teams Shared Channels because Shared Channels are intended for identity-based, auditable collaboration across tenants, not anonymous content distribution. Allowing “Anyone” links would bypass compliance, auditing, and conditional access controls, so Microsoft blocks them at the Teams layer.
• Shared Channels cannot be converted to Private Channels as they use different membership models and SharePoint site templates.
• Existing anonymous links may remain functional if no changes are made; however, any modification to files or permissions will revoke anonymous access within the Shared Channel.

For your reference: https://learn.microsoft.com/en-us/microsoftteams/shared-channels

I hope the information above is helpful. If you have any further questions, please feel free to reach out.

---

If this answer resolves your issue, please click “Accept Answer” and consider upvoting it. If you have additional questions regarding this response, kindly click “Comment.”

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.