Microsoft Teams Creates Separate SharePoint Sites for Private and Shared Channels

Microsoft Teams creates a separate SharePoint site for every private and shared channel, fragmenting storage and access boundaries that a parent-site audit misses.

Administrators who inventory only the team’s parent site overlook the distinct sites that hold channel files, permissions and external-collaboration records.

Each team receives a parent SharePoint site at creation, used by all standard channels including the default General channel, according to Microsoft Learn documentation. When a private or shared channel is added, Teams automatically provisions an additional, dedicated SharePoint site for that channel’s files. Only the channel’s owners and members can access its site; membership in the parent team does not grant entry.

Standard channels are open to all team members and share the parent site. Private channels restrict visibility to invited members and store files in their own site. Shared channels extend collaboration beyond the team — even across organizations — and also maintain a separate site.

Microsoft notes that “you can’t convert a standard channel to a private channel and vice versa” and that shared channels “can’t be converted into a standard or private channel and vice versa,” Microsoft Support states.

Guest access differs by channel type. Private channels can include guests who are already members of the parent team. Shared channels cannot add Microsoft Entra guest accounts as channel members; instead, external collaboration relies on B2B direct connect and cross-tenant settings, the SharePoint Smart Solutions analysis reports. A guest-account-only inventory therefore misses shared-channel participants.

Channel-site lifecycle is managed by Teams. Deleting a private channel’s SharePoint site directly can trigger automatic restoration by a background job while the channel remains active. Deleted and restored channels follow their own retention rules. “A SharePoint delete operation is not a reliable channel cleanup workflow,” the SharePoint Smart Solutions article warns.

Storage sprawl is an ownership problem, not merely a folder problem. The analysis recommends a repeatable register capturing team, channel, site URL, owner, storage consumption, external participants, retention status and approved action. Reviews should align with project closures as well as periodic schedules, recording the decision to retain inactive sites when compliance requires it.

Migration tools such as Smart Copy replicate files and version history between tenants but do not migrate chats, channel conversations, membership, tabs, apps or external-collaboration configuration. A copied channel library does not recreate the channel itself. Provision the target structure first, confirm owner-approved access, and test a small copy before proceeding, the analysis advises.

Photo of author

Technology Desk

Technology Desk at Archyde.

Hong Kong CC 24/0 Chasing 351 vs Diasqua in HKGPL 10th Match