What it does

A channel inside a team that only a named subset of the team's members can see. It gets its own SharePoint site, its own owners, and its own membership list that sits underneath the parent team's.

Key facts

• Private channels now count towards the overall limit of 1,000 channels per team (deleted channels included). The old cap of 30 private channels per team is gone, though tenants in special cloud environments were getting the enhanced behaviour later than commercial.
• A private channel can hold up to 5,000 members.
• Channel meetings are now supported in private channels — previously they weren't, which was one of the most common complaints.
• By default any team owner or member can create a private channel. Guests can't. Creation is controlled at the org level by the Create private channels setting in Teams policies (AllowPrivateChannelCreation on Set-CsTeamsChannelsPolicy) and at the team level by the owner in the team's Settings tab.
• The creator becomes the private channel owner, and only private channel owners can add or remove people directly.
• If the last owner leaves the organisation or is removed from the team's Microsoft 365 group, a member of the private channel is automatically promoted to owner. You can't remove the last owner of a private channel through the Teams client.
• Each private channel has its own SharePoint site (template TEAMCHANNEL#0 or TEAMCHANNEL#1). Parent team members and admins don't get access to it unless they're also channel members.
• If someone deletes the channel site outside Teams, a background job restores it within four hours as long as the channel is still active.
• Deleted private channels can be restored within 30 days.
• Compliance copies of private channel messages now go to the group mailbox rather than each member's mailbox. Get-TenantPrivateChannelMigrationStatus tells you whether the tenant has fully moved to that model.
• Not supported: connectors, and tabs for Stream, Planner, Tasks by Planner and To Do, and Forms. Private channel notifications don't appear in missed activity emails. A private channel can't be converted to another channel type.

When to use / skip

Use a private channel when a small group inside an existing team needs a space the rest of the team genuinely shouldn't see — the leadership sub-group in a project team, HR casework inside a department team, commercial discussions inside a bid team. The test is whether the sensitive bit really belongs to the team's context. If it does, a private channel keeps it next to the work it relates to.

Skip it when the "private" group is most of the team, or when the membership barely overlaps with the parent. At that point you're running a second team badly — create a separate team and stop paying the complexity tax. And if the people who need access sit outside the parent team or outside the organisation, look at a shared channel instead; that's what they're for.

The lifting of the 30-channel cap and the arrival of meetings removes two of the old reasons to avoid private channels. It doesn't remove the separate-site problem, which is still where most of the operational pain lives.

Configuration decisions

• Whether team members can create private channels or only owners — decide per team via team settings, and at org level via the channels policy.
• Whether a different channels policy applies to frontline or guest-heavy populations.
• Who owns each private channel: name at least two owners so you're not relying on automatic promotion.
• Whether the parent team's sensitivity label and SharePoint sharing settings are strict enough, since the channel site inherits much of its posture from the team.
• How retention and eDiscovery cover private channel content now that compliance copies land in the group mailbox (hand that conversation to the compliance workstream rather than designing it here).
• Naming convention so private channel sites are recognisable in SharePoint admin (the site name is derived from the team and channel names).

Gotchas

• Team owners do not automatically see private channels or their files. Clients find this out the first time a manager asks why they can't see their own team's content.
• SharePoint admins managing sites outside Teams will hit permission changes they can't make — channel site permissions are driven from the channel and are effectively read-only in SharePoint.
• Newly created private channels no longer get a default folder in their document library. Any provisioning script or migration that expected the folder to exist needs checking.
• Planner, Forms and Stream tabs are the usual "why can't I add this?" ticket. Set expectations before people try to rebuild their project tracker inside one.
• Missed activity emails skip private channels, so people who live in email miss things.
• Moving a conversation from a standard channel to private isn't a thing. You'll be copying content and re-creating tabs.

Consultant notes

• Put a short "when to use a private channel vs a new team" rule in the governance pack. Without one you'll find teams with fifteen private channels and two members each.
• Check Get-TenantPrivateChannelMigrationStatus before any compliance or migration discussion so you know which messaging model the tenant is on.
• For tenant-to-tenant migrations, inventory private channels separately — they're separate sites and most tools treat them as such.
• Tell owners that deleting a channel isn't final for 30 days, and that counts against the 1,000 limit until it's purged.
• The channels policy now carries a set of newer "next generation" channel parameters; read the current cmdlet reference before scripting policy changes rather than copying old examples.

---

Revisit once the expanded private channel limits and meetings land in the government clouds, and when the next-generation channel parameters in the channels policy settle down