Teams Shared Channels: Owners and Access Removal

A shared Teams channel can bring a partner into a focused workspace without adding them to the whole team. It also needs an owner who knows why the channel exists, which organisation hosts it and when access should end.

Create that record before inviting the first external participant.

Use the correct identity route

Microsoft’s shared-channel guidance distinguishes external participants using B2B direct connect from guest accounts in your directory. A conventional guest-account inventory therefore does not provide a complete list of shared-channel participants.

Microsoft Entra B2B direct connect requires the relevant cross-tenant configuration at both organisations. The host’s inbound settings and the partner’s outbound settings must allow the intended collaboration.

Confirm the partner tenant and the identities to use. Avoid solving an invitation problem by creating another account without understanding which collaboration model the channel expects.

Keep identity-policy ownership separate from channel ownership. The person running the project may decide who needs access, while the identity team controls whether the partner relationship is allowed at all.

Name two channel owners

Record a primary owner and an alternate within the host organisation. Give both enough context to approve membership changes and handle the project’s closure.

Microsoft allows more than one channel owner and describes what happens if the last owner leaves. Automatic promotion depends on a suitable remaining internal member; an administrator may otherwise need to assign an owner.

Do not rely on that recovery behaviour as the operating model. A newly promoted person may know nothing about the data-sharing agreement or the partner’s support contacts.

Keep these details with the channel:

Review this record when the project owner changes, not only at the next annual access review.

Include the SharePoint site

Shared channels have a separate SharePoint site. Microsoft’s SharePoint permissions guidance says channel-site membership is managed through Teams.

Record that site’s location with the channel. A support investigation is easier when the operator can connect the channel name to the correct document library, rather than inspecting the parent team’s site.

Do not add someone to the parent team merely to troubleshoot access to a shared-channel file. Establish which membership and file permission are involved first.

Check the actual document as the intended participant. A channel can be visible while a file fails because its separate access or protection requirements have not been satisfied.

Test membership removal and file access

Microsoft documents that separately granted SharePoint access to a file, folder or notebook can remain after a user is removed from the channel or team.

Include an access-removal exercise using harmless test material. Test an ordinary channel member and any separate file-access route deliberately created for the exercise. After removing the intended access, confirm what the user can still open.

Inspect existing tabs and notebooks as well. Adding a link or notebook to a channel does not establish that its original permissions have become identical to channel membership.

The result should distinguish channel participation from file access. If the person can no longer see the channel but can still open a separately shared document, record and resolve the remaining grant rather than calling the test complete.

Coordinate the partner’s departure

Agree how the partner will notify you when its employee leaves or changes role. Decide who removes channel access and how the host verifies completion.

For a finished project, review what needs retaining, where continuing work belongs and who will own it. Close or archive the space through the appropriate Teams process, taking account of the documented effect on sharing.

Avoid using deletion as an informal substitute for a retention decision. The data owner should know what will remain available and to whom.

Add shared channels to the existing Teams and SharePoint access review as a separate access path. The useful review has a current owner, a justified participant list and evidence that removing someone produces the intended result across both conversation and files.

References

• Microsoft — Shared channels in Microsoft Teams. Accessed 17 October 2026.
• Microsoft — B2B direct connect overview. Accessed 17 October 2026.
• Microsoft — Sharing and permissions in modern SharePoint. Accessed 17 October 2026.