The Shared Channels Licensing Problem Nobody Explains Clearly
Microsoft Teams Shared Channels — officially called Teams Connect — launched with a straightforward promise: let external users collaborate in a channel without needing a guest account in your tenant. No guest account means no Entra ID guest object, no cross-tenant sign-in friction, and no need to manage an external identity inside your directory.
What Microsoft's documentation does not explain clearly is what licences those external participants actually need, who pays for what, and how the compliance and governance requirements change depending on your organisation's M365 plan. After two years of Teams Connect at scale, we consistently find that enterprises have either over-licensed external participants "just in case" or created genuine compliance gaps because they assumed the feature was free for both sides.
This guide covers the licensing mechanics precisely: what is included in your existing M365 plan, what requires additional licences, the comparison between guest access and shared channels for external collaboration, and how to structure both the commercial and governance model for a large external-facing Teams deployment.
What Teams Connect Actually Is — and What It Is Not
Shared Channels in Teams are channels that can be shared across organisational boundaries without guests. When a user in Organisation A is added to a shared channel owned by Organisation B, they access that channel from within their own Teams client, using their own Organisation A identity. They do not appear in Organisation B's Entra ID as a guest. They do not consume a B2B guest licence entitlement from Organisation B.
This is architecturally different from standard Teams guest access, where the external user is invited into your tenant as a B2B guest, appears in your Entra directory, and consumes guest-related entitlements (Entra ID P1 conditional access policies, access reviews, and so on).
The Cross-Tenant Access Policy Dependency
Teams Connect requires Entra External Identities Cross-Tenant Access Settings to be configured on both tenants. This is not a licence requirement — it is a configuration requirement — but it carries a practical implication. Your IT team must either manage cross-tenant access policy broadly (allowing all Microsoft tenants) or specifically (allow-listing individual external tenants). Most enterprises choose a mix: a default deny policy with per-partner allow-lists. This creates an ongoing administrative overhead that is worth accounting for when evaluating shared channels at scale.
Teams Connect does not create guest objects. Standard Teams guest access does. This changes which Entra ID licence features apply, which access review cadences are required, and what your true-up looks like at renewal. The two models are not interchangeable from a licensing or compliance perspective.
Licensing Requirements: Who Needs What
The fundamental rule for shared channels is that the hosting organisation must have appropriate M365 licensing for the channel itself, and each external participant must be licensed by their own organisation to access the features they use within that channel.
Hosting Organisation Requirements
To create and host a shared channel, your organisation needs:
- Microsoft Teams licence for the channel owner (included in M365 E1/E3/E5, Teams Essentials, Teams Enterprise)
- Entra ID P1 for cross-tenant access policy management (included in M365 E3/E5 and available as a standalone add-on)
- Teams Premium if you require advanced meeting features in shared channel meetings (optional)
The critical point: Entra ID P1 is required for granular cross-tenant access control. If you are on M365 E1 without Entra P1, you can use Teams Connect, but you can only manage cross-tenant access at the tenant level, not at the application or user level. For most enterprises, per-partner control is operationally necessary, which means E3 (which includes Entra P1) or an Entra P1 add-on onto E1 is required.
External Participant Requirements
External participants — the users from the partner organisation joining your shared channel — must be licensed by their own organisation. The specific requirements are:
| Feature Used in Shared Channel | Minimum Licence at External Org | Notes |
|---|---|---|
| Chat and file sharing | Microsoft Teams (any plan) | Included in M365 E1 and above, Teams Essentials |
| File co-authoring via SharePoint | SharePoint Plan 1 or M365 E3 | Teams Essentials alone does not include SharePoint |
| Meeting participation in shared channel | Microsoft Teams (any Teams plan) | Standard meeting attendance requires any Teams licence |
| Teams Premium meeting features | Teams Premium at external org | Watermarks, sensitivity labels, advanced recordings require Teams Premium on both sides |
| Loop components in shared channel | M365 E3 or M365 Apps licence | Loop requires M365 Apps entitlement — not included in Teams Essentials |
| Purview compliance policies applied to channel content | Purview licence at external org | You cannot apply your compliance policies to external users' data |
The SharePoint co-authoring gap is the most common licensing problem we encounter. An organisation implements shared channels to share documents with a consortium of partners, some of whom are on Teams Essentials or Teams Free. Those external users can see files in the channel but cannot co-author them because they lack a SharePoint licence. The workaround — sharing via a direct link rather than channel — defeats the purpose of the integration and creates a separate governance problem.
Guest Access vs Shared Channels: The Commercial Comparison
The choice between Teams guest access and Teams Connect shared channels is not purely technical — it has direct commercial implications for both sides of the relationship. Here is how they compare across the dimensions that matter to a licensing decision:
| Dimension | Teams Guest Access | Teams Connect (Shared Channels) |
|---|---|---|
| External user Entra object | Yes — guest created in host tenant | No — no guest object created |
| Entra P1 requirement (host) | Required for Conditional Access on guests | Required for cross-tenant access policy |
| Access Reviews (P2) | Required for periodic guest review | Not applicable — no guest objects |
| MFA enforcement on external | Host can enforce via Conditional Access | External org enforces MFA for their own users |
| External user experience | Joins host tenant's Teams environment | Stays in own Teams client and identity |
| Data residency | Content stored in host tenant | Content stored in host tenant (SharePoint) |
| Compliance boundary | Host tenant policies apply to guests | External org policies apply to their own users |
| Scale manageability | Complex at high guest volumes (100+ guests) | Better at scale — per-partner tenant allow-lists |
| Maximum external participants | No hard limit (practical limits apply) | 50 per shared channel |
The 50-participant limit on shared channels is a hard architectural constraint, not a configuration option. For large consortium or industry-body collaboration scenarios, this limit is often the deciding factor. Guest access supports larger external populations at the cost of greater identity management overhead and Entra P2 requirement for access reviews.
The Compliance Boundary Implication
One of the most commercially significant differences is the compliance boundary. With guest access, your Purview compliance policies — retention, DLP, sensitivity labels, communication compliance — can be applied to content that guests create in your channels. With shared channels, external participants are governed by their own organisation's compliance policies for content they generate. Your policies do not extend to them.
For regulated industries — financial services, healthcare, legal — this is not a minor technical footnote. It is a risk management question that must be answered before deploying shared channels with external parties who are handling regulated data. The answer may well be that guest access is the correct model for regulated scenarios and shared channels for lower-risk operational collaboration.
Building a Governance Model for External Collaboration
Whether you use guest access, shared channels, or a combination of both, the absence of a formal external collaboration governance model is itself a licensing risk. Teams guest populations and shared channel relationships grow organically, and without active management they create both over-licensing (guest accounts for leavers, unused shared channels still provisioned) and under-licensing (users accessing features not covered by their own organisation's plan).
Guest Access Governance Cadence
For organisations using Teams guest access:
- Monthly: Run a guest account report from Entra ID showing last sign-in date. Flag accounts with no sign-in in 60+ days for review
- Quarterly: If you have Entra P2, run Access Reviews for all active guest accounts. If on P1, conduct a manual review using the guest report
- Annually: Audit guest account count against your Entra P1/P2 licence volume. Excess guest objects should be resolved before your EA true-up date
Shared Channels Governance Cadence
For Teams Connect deployments:
- Monthly: Review active cross-tenant access policy allow-list entries. Remove entries for partnerships that have ended
- Quarterly: Audit shared channel membership — who from external tenants still has active access, and whether business relationships still justify that access
- At partner offboarding: Explicitly remove cross-tenant access trust for the departing partner and archive shared channels
Shared channels do not create guest objects, but if a cross-tenant access policy grants access to any tenant (rather than named tenants), you may inadvertently enable access from tenants whose users you did not intend to include. This is both a security risk and a compliance audit finding waiting to happen. Always configure cross-tenant access with explicit allow-lists.
Teams Premium and Shared Channels
Teams Premium is the paid add-on that extends base Teams with advanced meeting features including intelligent meeting recap, watermarks, sensitivity label enforcement in meetings, and advanced webinar capabilities. When shared channel meetings involve Teams Premium features, the licensing question becomes more complex.
The Microsoft position is that Teams Premium features in a shared channel meeting require Teams Premium to be licensed on both the host and external participant sides for the full feature set to function. In practice, this means:
- Watermarks in shared channel meetings: requires Teams Premium at the host org only — host can enforce watermarks regardless of external licence status
- Sensitivity labels in meetings: requires Teams Premium at the host org; external participants will see the meeting sensitivity classification but cannot apply their own labels
- Intelligent meeting recap: requires Teams Premium at the individual participant's org — external participants without Teams Premium will not receive AI-generated summaries
- Custom meeting templates: requires Teams Premium at host org for template enforcement
The commercial implication: you cannot guarantee external participants will receive the full Teams Premium experience you have paid for. If your use case requires external participants to have AI meeting summaries — for instance, in a client advisory or professional services context — you should either confirm their Teams Premium status before relying on the feature or accept that the experience will be inconsistent.
Optimising Your External Collaboration Licensing Stack
Most enterprises doing this for the first time have a mixed estate: some external partners configured as guests, some via shared channels, and a growing Teams Premium deployment. Here is how to rationalise the commercial picture.
Step 1: Audit Current External Access Configuration
Run a cross-tenant access policy audit and a guest account report simultaneously. Identify which external relationships use guest access versus shared channels, and for each shared channel, confirm what licence tier the external users hold at their own organisation (this requires asking them directly or running a limited assessment).
Step 2: Classify External Relationships by Risk and Collaboration Depth
Not all external collaboration is equivalent. A manufacturing firm with 50 strategic suppliers and 500 occasional contractors needs different structures for each population. Use this framework:
| Relationship Type | Recommended Model | Rationale |
|---|---|---|
| Strategic long-term partner (regulated data) | Guest access + Entra P2 access reviews | Compliance policies extend to guests; access review cadence reduces risk |
| Strategic long-term partner (non-regulated) | Shared channels (Teams Connect) | Better user experience; no guest directory overhead; simpler offboarding |
| Large consortium or industry group | Shared channels if ≤50 external; Guest if larger | 50-participant limit on shared channels drives the decision |
| Short-term project (6 months or less) | Guest access with explicit expiry date | Access review at project close is simpler for transient relationships |
| Customers / clients (large volume) | Entra External ID B2B (not standard Teams guest) | Standard guest at scale is unmanageable; External ID provides lifecycle management |
Step 3: Resolve Licence Gaps Before True-Up
If your shared channel audit reveals external participants accessing SharePoint-based collaboration features without a SharePoint licence at their organisation, that is their licensing problem — not yours. However, if those partners are accessing your SharePoint content in ways that require them to have licences they do not hold, document the position. Microsoft's audit guidance is that unlicensed access to M365 services creates an under-licensing position for the organisation that should have provided the licence, which in most cases is the external user's own employer.
For guest access, any guest object in your Entra tenant that consumes Entra P1 features (Conditional Access, SSO app assignments) requires you to have a corresponding Entra P1 licence. The standard rule is five guest licences included per paid Entra ID P1 user licence. Beyond that ratio, additional Entra P1 licences are required for the external users. If your guest population exceeds 5× your licensed user count for Entra P1, you have a true-up exposure that needs to be resolved.
Negotiating External Collaboration Licences in Your EA
Most organisations negotiate their internal user seat counts carefully but give little thought to the licence provisions that govern external collaboration at scale. Two EA provisions are worth including if you operate a large external-facing Teams environment:
External User Volume Provisions
If your business model involves large numbers of external collaborators — professional services firms with client-facing Teams deployments, manufacturers with supplier networks, consortiums — negotiate an explicit provision in your EA or an addendum that covers the expected external user volume and the applicable licence model. Without this provision, you are relying on Microsoft's Product Terms interpretation, which can change with Product Terms updates.
Entra ID Guest Ratio Clarification
The 5:1 guest-to-licensed-user ratio for included Entra P1 guest entitlements is the published guideline, but it is not always enforced consistently. Get the applicable ratio confirmed in writing as part of your EA negotiation, particularly if you are deploying guest access at a 3:1 or 4:1 ratio and want certainty that you are not accumulating a hidden liability.
Also negotiate your true-up methodology for external users specifically. The standard EA true-up counts licensed users as of the anniversary date. If your guest population fluctuates significantly across the year (project-based peaks, seasonal collaboration), negotiate a mechanism to report peak versus average rather than point-in-time counts.
Frequently Asked Questions
Can Teams Connect shared channels be used without an M365 licence?
The hosting organisation needs a Teams licence and Entra ID P1 for cross-tenant access management. External participants need at minimum a Teams licence from their own organisation. Teams free or Microsoft personal accounts cannot participate in Teams Connect shared channels — a business Teams licence is required on both sides.
Do shared channel participants consume guest licences?
No. Shared channel participants do not create guest objects in the host tenant and do not consume guest-related Entra licence entitlements from the host organisation. They are governed by their own organisation's licences. This is one of the primary commercial advantages of Teams Connect over standard guest access for large external collaboration deployments.
Is there a charge for creating shared channels?
No separate per-channel charge. Shared channels are included in Teams licensing as a platform capability. The relevant licence costs are at the user level (the Teams licence itself, Entra P1 for cross-tenant policy management, and optionally Teams Premium for advanced features) rather than at the channel level.
What happens to a shared channel if the external partner relationship ends?
Removing the cross-tenant access trust for the external tenant removes external users' access to all shared channels linked to that trust. The channel content remains in the host organisation's SharePoint. The channel itself persists and can be reassigned to internal-only access or archived. This is cleaner than the guest access offboarding process, which requires individually removing guest accounts from all groups, Teams, and SharePoint sites they were added to.