Content reviewed: 12 October 2026

Microsoft Teams offers regular, private, and shared channels. Their names suggest that there are only three levels of visibility. However, with external collaboration, user identity, cross-organizational settings, and file permissions also change. If you choose the wrong channel type, sending the invitation repeatedly won't help.

Decide what the partner needs to access

A standard channel belongs to the whole team. An external person can be invited to the team as a guest if the rules of the organization allow it. A private channel narrows the circle of people within the team. A Shared Channel can connect people from different teams and supported external organizations without the external person becoming a member of the entire team.

A shared channel has its own membership. Other members of the parent team cannot see its content unless they are also members of the shared channel. It is not a universal replacement for guest access. Microsoft states in its shared channels documentation that a guest account in the hosting tenant cannot be added as a shared-channel member.

Comparison of scenarios and controls
NeedA suitable starting directionWhat to watch out for
The partner should cooperate with the whole teamGuest in the team; standard channelsThey will see content according to the rights of the whole team
Only a limited group of team members should have accessPrivate channelCheck membership and file access
People from multiple supported organizations should work in one channel without switching tenantsShared channel via B2B direct connectBoth organizations must establish mutual cooperation
The partner does not have a Microsoft 365 work/school accountConsider another external collaboration modelThe shared channel may not be available for him

The table is a design aid, not an automatic safety rule. Document sensitivity, organizational rules, and user experience can change the decision.

Why an existing guest is not enough

The external member of the shared channel connects via Microsoft Entra B2B direct connect. The person signs in through their home organization and does not need to switch to the host tenant when accessing the channel. Unlike normal B2B collaboration, it does not have a standard guest object in the target tenant. Microsoft describes this difference in B2B direct connect overview.

Changing a guest’s userType to Member does not make that identity eligible for a shared channel. When the partner also has a guest object, use ext:user@domain.com in Teams admin centre to find their home-organisation account. Use the UPN when it differs from email. A guest object does not establish direct connect readiness.

A shared channel cannot be converted to a standard channel or moved to another team. Decide its membership and location before moving real content.

What both organizations must allow

The setting is two-sided. In Microsoft Entra, cross-tenant access settings for B2B direct connect are configured for the partner: who can enter your channels and who from your organization can enter theirs. The other organization must authorize the corresponding party to the relationship. The service is disabled by default; the policy itself in Teams will not replace it. The Microsoft process for external participants lists both inbound and outbound configuration.

Alongside Entra, check the Teams policies Create shared channels, Invite external users to shared channels and Join external shared channels. Current Teams documentation requires guest access enabled even though this model does not use guest objects. Meetings, presence, SharePoint and Groups have related settings; check the feature that actually fails.

In the pilot, set the relationship first to a specific partner, with specific groups or users as needed. Broadly allowing all external organizations should be a conscious decision, not a hotfix for a failed invitation.

There is a cloud boundary: B2B direct connect is unsupported between tenants in different Microsoft clouds. Enabling cross-cloud B2B collaboration does not establish shared-channel direct connect support. Check both partners’ clouds before configuration.

Access direction and MFA trust

For each access attempt, identify the resource host and the user’s home organisation. Do not reverse inbound/outbound or confuse B2B collaboration settings with B2B direct connect. Check both directions when users need channels hosted by both organisations.

Who permits each direction
Channel access directionResource tenantUser’s home tenant
User B accesses a channel in AA permits inbound from BB permits outbound to A
User A accesses a channel in BB permits inbound from AA permits outbound to B

For a selected partner group, obtain its object ID from the partner’s admin. A same-named group in your directory is not a substitute. Check allowed applications too; the older Teams setup guide uses Office 365, including related services.

If the resource tenant requires MFA through Conditional Access, its inbound trust settings must accept MFA claims from the home organisation. The partner must actually complete MFA there. Allowing inbound/outbound access alone does not meet this requirement. Likewise, check trust for compliant-device or hybrid-joined claims when required.

Microsoft notes that an IP-based rule can restrict SharePoint files even when the channel works from that location. Record the exact time, tenant IDs, UPN, application and Conditional Access result in the resource tenant’s sign-in logs. Do not address a message/file difference by disabling protection broadly.

Ownership and the end of collaboration

A new channel member can see older conversations. Consider that history before inviting them. A parent-team owner can see the channel name and delete it, but without membership cannot see its content or members. Assign actual channel owners for operations; removing the last owner has special restrictions.

Access reviews can examine directly added members, including B2B direct connect users. The current overview states a limitation: other teams added to the shared channel are not detected by that review. Owners must check team-based sharing separately. Restoring a deleted channel also restores prior membership; recheck access after restoration.

Test the channel with both organizations

The manager is preparing a plan for cooperation with an external organization

Use the control procedure with two administrators and one tester from each side:

  1. Record the home tenant and UPN of each test user.
  2. Verify mutual inbound/outbound B2B direct connect authorization for correct organizations and Office 365 application.
  3. Check the Teams policy for both the channel owner and the external participant.
  4. Create a pilot shared channel with a clearly defined owner.
  5. Invite an external work account; do not select an existing guest object.
  6. Test messaging, file access and, if relevant, meetings. Each can fail for a different reason.
  7. Write down who will regularly check access and who will remove it after the collaboration ends.

If the participant search fails, do not start by changing all tenant rules. Compare the exact UPN and both sides of the direct connect. If the channel works but the file won't open, go to SharePoint, sensitivity labels, and conditional access. Microsoft has shared channels errors overview for this.

Check file permissions separately

Each shared channel creates its own SharePoint site. Site membership is tied to channel membership, and site rights are not managed separately directly in SharePoint. This is why the administrator is not supposed to "fix" the missing member by manually adding it to the site group. Verify Teams membership and associated policies. Microsoft describes the architecture and limitations in the documentation.

Direct permissions to files, folders or notebooks can survive removal from the channel. Microsoft describes this SharePoint sharing for people outside the channel but inside the organisation. It does not establish that a standard link can add any external person outside channel membership. Offboarding must check membership, direct permissions and existing notebooks retaining their own rights.

An external participant may be able to read channel messages yet fail to open a document protected by a sensitivity label and encryption. That does not, by itself, mean B2B direct connect is broken. Check the document permissions and file protection separately.

Licensing and costs

The current cross-tenant access overview requires Entra ID P1 in both tenants for B2B direct connect. P1 is also needed for trust settings and targeting individual users, groups or applications. Check both organisations’ existing entitlements; a successful invitation is not licence evidence. This tenant prerequisite is neither a count of paid P1 seats for external users nor proof that every invitation is billed under MAU. Separately check Teams rights in the home organisation and the security features used.

Do not confuse this question with Teams Premium or Teams Rooms. These products address other features and facilities as explained in Axeti's standalone guide. Purchasing a higher meeting organizer license will not set up mutual B2B direct connect for both tenants.

Frequently asked questions

Can an existing guest be added to a shared channel?

Not as a guest identity. The shared channel uses B2B direct connect for the external person and their work account in the home organization. The same person can have a guest account in the tenant, but you need to choose the right identity.

Is it enough to turn on shared channels in Teams?

Not enough for external collaboration. Both organizations must set up appropriate cross-tenant access, then review Teams policies and related rules.

Can an external participant see the whole team?

A shared channel has a separate membership; accessing a channel does not automatically open all other parent team channels. However, check file sharing and direct permissions separately.

Does removing from a channel remove all access to files?

Not always. Direct permissions can remain. Microsoft describes this SharePoint exception for people outside the channel but within the organisation; it is not a general way to share with any external person. Check membership and separate rights.

Does the external participant have to switch tenants?

B2B direct connect is designed to use a home account and allow access to a shared channel without the usual organization switch in Teams. Verify the exact behavior in a pilot with a specific partner.

Choose the collaboration model before inviting users

Write down whether the partner needs an entire team, a single channel, or just a few files. Then choose an identity model, set up both organizations, test communications and files, and determine the access owner. This will fix the cause of the problem instead of repeating the same invitation.