Setting Up a Microsoft Teams Shared Channel with a Customer
Getting a Teams shared channel working with a customer's organization takes a team owner on your side who creates the channel, plus a handful of admin settings enabled on both sides, up to and including the customer's own Microsoft Entra cross-tenant access configuration. Invites fail almost every time because one of those settings is missing, not because Teams is broken. Microsoft's own shared channels error reference documents four distinct failure messages, and every one of them traces back to a specific setting on one side of the connection.
The mechanism behind shared channels with an external company is called B2B direct connect, and its defining property is that it's mutual. Per Microsoft's B2B direct connect overview, "Microsoft Entra ID blocks all inbound and outbound B2B direct connect capabilities by default for all external Microsoft Entra tenants," and both organizations have to separately turn it on for each other before either side's users can join a shared channel. Your admin can finish every setting correctly, and the invite will still fail if the customer's admin hasn't done their half.
What has to be true before you invite anyone
Four things need to be in place, and they're split across three separate admin consoles:
- A team owner on your side. Per Microsoft's shared channels documentation, only team owners can create a shared channel, and only the channel owner can add or remove its members afterward. A team member without owner rights can't start this.
- Microsoft 365 Groups guest sharing is turned on for your tenant. In the Microsoft 365 admin center, under Org settings > Microsoft 365 Groups, group owners need to be allowed to add people outside the organization. This is a tenant-wide setting that has nothing to do with Teams specifically, and it's separate from the Teams policy below, so fixing one doesn't fix the other.
- Your organization's Teams policy allows it. In the Teams admin center, the policy assigned to the channel owner needs
Invite external users to shared channelsturned on. If it's off, the owner sees the invite fail even when the Groups setting above is already correct. - Cross-tenant access configured on both tenants. Your Microsoft Entra admin has to add the customer's organization and allow B2B direct connect outbound to them. The customer's Entra admin has to do the mirror image: add your organization and allow B2B direct connect inbound from you. Neither side can do this unilaterally, and it's an Entra admin task, not something a team owner can complete from inside Teams.
Guest access, by contrast, isn't involved at all here. A shared channel participant from another company authenticates with their own tenant's credentials over B2B direct connect; per the shared channels documentation, guests, including guests who've since been converted to members, can't be added to a shared channel. If someone on the customer's side already has a guest account in your directory, that account is the wrong path for this.
Creating the channel and getting the customer in
Once the admin prerequisites above are confirmed, the actual creation is quick:
- From the team the channel will hang off, create a new channel and set its type to Shared instead of Standard or Private.
- Add the customer's contact using their full email address for their own organization, not a guest account you may already have for them.
- Select Share, and they receive access from their own tenant's Teams client, no separate sign-in and no account created in your directory.
That's the whole flow when the prerequisites are met. Nearly every support thread about a shared channel "not working" is a report of one of the following four errors, and each one names exactly which setting or detail is missing.
The four errors, and what each one means
Microsoft's error reference lists these verbatim, and they map cleanly to the four requirements above:
- "Due to admin policy, you can't add external people to the channel. For more info, talk to your admin." This is the Microsoft 365 Groups guest-sharing setting, not a Teams setting. It has to allow group owners to add people outside the organization, in the Microsoft 365 admin center under Org settings > Microsoft 365 Groups.
- "Due to admin policy, you can't add external people to the channel" (same wording, different cause). This one is the Teams channel policy from the checklist above:
Invite external users to shared channelsis off for the team owner's assigned policy. - "You can't share this channel with people from this org." This is the cross-tenant mismatch. Either your outbound B2B direct connect settings for that organization aren't configured, or the customer's inbound settings for your organization aren't. Since it's mutual, seeing this error doesn't tell you which side is missing, only that at least one is.
- "We couldn't find any matches. Make sure the email address is correct, or talk to your admin." Teams can't resolve the address against the external tenant at all. Per the shared channels documentation, this often means the person's sign-in name (their UPN) doesn't match their email address, and you need to search using their UPN instead.
The third error is the one that eats the most time, because it looks identical whether your side or theirs is unfinished. The fastest way through it is to ask the customer's IT admin directly whether they've added your domain under their inbound cross-tenant access settings, rather than re-checking your own configuration a second time.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionTamsin Achterberg waits on someone else's admin
Wexcombe Rail builds trackside signal monitoring hardware, and Tamsin Achterberg runs customer support for the accounts using it. When Calder Transit Authority signed a support contract for its commuter line, Tamsin's manager wanted a shared channel set up so Calder's operations team could report signal faults directly instead of emailing a shared inbox that nobody watched consistently.
Tamsin had her org's side ready in a day. Her Teams admin confirmed the channel policy, and she created the shared channel off Wexcombe's support team. Adding Calder's operations lead failed immediately with "You can't share this channel with people from this org."
"I checked our outbound settings three times before I even opened a ticket," Tamsin told her manager. "It never occurred to me the block was on their end, not ours."
It took an email to Calder's IT department, not a Teams support ticket, to resolve it. Calder's Entra admin had never added Wexcombe's tenant to their inbound cross-tenant access settings, because nobody at Calder had done a B2B direct connect setup before. Once their admin allowed inbound access for Wexcombe's domain, the invite that had been failing all week went through on the first retry, no changes needed on Tamsin's side at all.
An open channel doesn't triage what lands in it
A correctly configured shared channel makes the conversation possible, and that's all it does. It doesn't solve what happens to what gets said inside it. Calder's operations team now reports signal faults directly in the channel, but each report still has to be noticed, checked against faults other transit customers have already reported, and handed to Wexcombe's engineering team as a ticket. None of that is a setting anywhere in Teams admin or Entra ID.
That's the gap Modem is built for. Modem reads the Microsoft Teams channels you connect as messages land, whether the customer joined through a shared channel or an older guest-access setup, groups a fault reported three different ways across multiple client channels into one counted topic, and opens the engineering ticket with the requester and the original message attached. Getting the channel open is still on you and the customer's Entra admin; what a message in it turns into afterward is what Modem picks up. We built Modem for that second half specifically, so read this as a vendor describing its own product against the triage gap above, not as a neutral comparison against whatever already turns your channel messages into tickets today.
If shared channels versus guest access is still an open question for a given customer relationship, our comparison of the two covers when each fits. Once channels are live, buried feature requests are usually the next problem, and this guide covers that directly.
Before you open a ticket
If an invite is failing, check in this order: confirm you're a team owner, confirm Microsoft 365 Groups guest sharing is on for your tenant, confirm your Teams policy allows inviting external users, then ask the customer's admin directly whether their inbound cross-tenant access settings list your domain. That last question resolves more of these than anything you can check on your own side, because the error message that shows up doesn't say which tenant is the one still missing a setting.
