Private vs shared channels in Microsoft Teams

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.

Why not just create a separate team?

The temptation to solve "some people need restricted access" by spinning up a whole new team is understandable, but it multiplies the things that need governing — a new Microsoft 365 Group, a new SharePoint site, a new set of owners to maintain, and a parallel structure that's easy to lose track of alongside the parent team it logically belongs with. A private or shared channel keeps the restricted conversation discoverable in context (still listed under the parent team, just with narrower membership) while still isolating the SharePoint storage and permissions behind it — the right default whenever the restricted group's work is a subset or extension of the parent team's purpose, reserving a genuinely separate team for work that doesn't conceptually belong under any existing team at all.

Frequently asked questions

Can a private channel's SharePoint site be accessed directly, bypassing Teams? Yes — like any Teams channel, a private channel's SharePoint site has its own URL and can be reached directly by anyone with permission, which matters for admins running SharePoint-level reports (including SharePoint Advanced Management's oversharing reports) since private and shared channel sites show up there as sites in their own right, not nested inside the parent team's site.

What happens to a private or shared channel if the parent team is deleted? The channel and its SharePoint site are deleted along with the parent team (subject to the same recycle-bin recovery window as the team itself) — a shared channel's external members lose access at that point too, since the channel's existence is still tied to the parent team even though its membership extended beyond it.

Can a shared channel's external partner see who else is in the parent team? No — a fundamental design point of shared channels is that external or cross-team members only ever see the shared channel's own membership, never the parent team's roster, files, or other channels. This is what makes shared channels usable for genuinely sensitive partner relationships in a way that simply adding the partner as a guest to the whole team never could be.