Private vs shared channels in Microsoft Teams
By Emil Björk · Microsoft ecosystem consultant, Gothenburg
When to reach for a private channel versus a shared channel — the membership model, storage, and external-access trade-offs.
Standard channels in Microsoft Teams are easy: they're visible to every member of the team. The interesting decisions start when you need restricted membership — that's where private channels and shared channels come in. They look similar but solve different problems.
Private channels
A private channel is for a subset of the parent team's members. Membership is a strict subset — you can't add anyone who isn't already in the team. Use cases:
- Leadership-only sub-channel inside a department team.
- HR business-partner channel inside a HR team.
- Sensitive project work inside a wider product team.
Each private channel provisions its own SharePoint site (not just a folder), with its own permissions and storage quota. That gives strong isolation but creates more sites to govern.
Shared channels
A shared channel allows you to add people who aren't members of the parent team — including users from other Microsoft 365 tenants (cross-tenant collaboration via Entra ID's external collaboration settings). Members of a shared channel don't see the rest of the team. Use cases:
- Ongoing collaboration with an external partner organisation.
- A cross-team working group that spans two or three product teams.
- A vendor or consultant relationship that needs persistent chat plus files.
Shared channels also get their own SharePoint site.
Decision matrix
| Need | Channel type | | --- | --- | | Confidential subgroup within the team | Private | | Cross-team or cross-tenant collaboration | Shared | | Open to all team members | Standard | | Guests need full team access | Standard with guest accounts |
Operational caveats
- Conversion isn't supported: a channel created as standard, private, or shared stays that type. Plan up front.
- App support is uneven: some Teams apps work in standard but not private or shared channels — check before you commit.
- Cross-tenant shared channels need both tenants to configure trust under Cross-Tenant Access Settings, and both ends need to enable shared channels for the partner.
- Quotas matter: each team has limits (200 standard, 30 private, 200 shared), and every private/shared channel inflates your SharePoint site count.
Used well, private and shared channels keep the right people focused on the right conversations without sprouting more whole teams.
Spot something wrong or want a topic covered? Send it through the contact form.