How to Connect Multiple Teams Accounts to Copilot
Copilot has no concept of a second Teams organization, so connecting each Microsoft identity to Carly is the only way one assistant covers both. A Microsoft 365 Copilot licence is assigned by an administrator inside one tenant, and Copilot’s grounding is bounded by that tenant’s directory. Sign into a second organization in Teams and you are a different user in a different directory, where whether Copilot exists for you is that organization’s decision, not yours. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
What one chat can do afterwards
- Summarize two client organizations’ channels in the same question.
- Say which organization every answer came from.
- Reach a client tenant nobody has licensed you in.
- Post a reply into the organization you name.
- Log the same escalation in your own internal channel.
- Act when the mention lands, rather than when you next open Teams.
Nothing is merged. Each Microsoft identity stays separately authorized, and Carly keeps them individually addressable.
The tenant is the boundary, and that is the architecture
Copilot’s grounding is not a setting that can be widened. Microsoft describes the underlying isolation directly: “Logical isolation of customer content within each tenant for Microsoft 365 services is achieved through Microsoft Entra authorization and role-based access control.”
Copilot reasons over what your identity is authorized to see inside one directory. A second organization is a second directory, reached by a second identity and licensed by a second administrator. No configuration makes one Copilot session span both, because from Microsoft’s point of view those are two different users who happen to be the same person.
The most telling evidence is an absence. Microsoft built a feature specifically for working across tenants in Teams, called a multi-tenant organization, whose stated goals are to “define a boundary around the tenants belonging to your organization” and to “collaborate across your tenants in new Microsoft Teams.” That documentation mentions Copilot zero times. Microsoft’s Copilot requirements page returns the compliment: no mention of shared channels, cross-tenant access, or multiple tenants anywhere on it. It would not help you anyway, since it assumes “reciprocal provisioning of B2B collaboration member users” between tenants one company controls, typically after an acquisition. An agency working across four unrelated clients cannot create one.
Guest access and shared channels
Guest access puts you in the other tenant as a guest, reached by switching organizations in the Teams client. You are now inside their directory, where your own Copilot licence does not exist. Whether you get Copilot depends on whether that organization licensed it for guests, which is their configuration and not something you can arrange.
A shared channel works the other way round, bringing the external conversation to you without guest accounts: “you can invite people outside your organization to participate in a shared channel by using Microsoft Entra B2B direct connect,” and “guests, including those converted to members, can’t be added to a shared channel.”
That makes it the right thing to ask for, since it keeps you in the directory your licence lives in. It needs cross-tenant access settings configured in Entra ID on both sides, guest access enabled in Teams to issue the invitation, and a team owner to create it. Whether Copilot then grounds on that channel’s content is not documented by Microsoft either way, so test it against history you can check.
1. Sort your organizations
| Your case | Native path in Copilot |
|---|---|
| Your employer’s Teams, licence assigned | Yes |
| Your employer’s Teams, no licence | No, an administrator has to assign one |
| A client’s Teams you are a guest in | Only if they licensed Copilot for guests |
| A shared channel from another organization | Undocumented, test it |
| Two organizations in one question | Not a supported concept |
| A meeting nobody recorded | No, transcription or recording is required |
2. Connect each Teams account to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Microsoft Teams and click Connect.
- Authorize the first Microsoft identity.
- Repeat for every additional organization, including a client tenant you are only a guest in.
- Choose Use another account if Microsoft preselects the previous login.
- Verify each organization after authorization.
No licence assignment, and no administrator decision in someone else’s tenant.
3. Choose how Copilot reaches Carly
Copilot has no box where an ordinary user pastes a connector URL, on either SKU. Consumer Copilot at copilot.com ships a fixed connector list and its support page never mentions MCP. Microsoft 365 Copilot, the paid work SKU, accepts an MCP Base URL only from an administrator. That is Microsoft’s connector model rather than a gap on Carly’s side, and it leaves three honest routes.
You work with Carly directly. The organizations you connected at step 2 are usable immediately, and naming one in an instruction is the point. Most readers stop here.
A maker adds Carly in Copilot Studio. This is the Microsoft-side route that actually fits Carly, because it carries write actions. Tools → Add a tool → New tool → Model Context Protocol, then supply a server name, a description, and https://carlyassistant.com/mcp/ as the server URL, with auth set to None, API key, or OAuth 2.0. Only Streamable transport is supported; SSE was dropped in August 2025. It needs a work or school account and a paid licence, the trial cannot publish the agent, and it produces a separate agent rather than Copilot Chat.
An administrator adds a federated connector, which is a partial fit. Microsoft 365 admin center → Copilot → Connectors → Gallery → Create a new connector, then under Connect to MCP server select Add and fill in a display name and Base URL. It needs the Global Administrator or AI Administrator role plus a registered Entra SSO or OAuth 2.0 application, and Microsoft requires these connectors to be read-only, so an admin gets a read slice rather than posting. Federated connectors reached general availability in June 2026 and admin center management shipped in July 2026.
If none of those shapes fits your team, the API and bring-your-own-key path runs through the Carly team. Book a call to scope it.
4. Test each organization read-only
One organization per prompt until routing is reliable:
In the Databricks organization, summarize what was decided in the launch planning channel yesterday. Read only.
In my own organization, list every message this week where someone asked me for a date. Do not reply to anything.
Then the question that spans both:
Compare what the Adobe organization and the Databricks organization each agreed about the November launch, and say which organization each answer came from.
5. Reuse this routing prompt
Treat my employer’s Teams as Internal and the client organizations as Adobe and Databricks. Always state the target organization before posting, replying, or filing anything. Never post to an organization I have not named.
Then name the target per action:
Post the revised timeline to the launch planning channel in the Databricks organization and log the change in the accounts channel in Internal.
What Copilot already does inside one organization
Inside the tenant that licenses you, Copilot is grounded in your actual work rather than a connector’s narrow slice of it, and there is no OAuth screen to add. Two documented specifics are worth having. Availability: “Copilot in Teams is available on Windows, Mac, web, Android, and iOS.” Meetings: “To enable Copilot in Teams to reference meeting content after the meeting ends, enable transcription or meeting recording.” A meeting nobody recorded is a meeting Copilot cannot recap, whatever licence you hold. One more limit is stated plainly: “Microsoft 365 Copilot is only supported on primary mailboxes that are hosted on Exchange Online.”
Nothing in that surface watches a channel either. Copilot has schedule- and calendar-driven behaviours elsewhere, but nothing fires because a message arrived, an @mention landed, or a customer escalated. A meeting recap happens after a meeting you recorded, which is closer to a consequence than a trigger. For a reader whose goal is “tell me when something in Teams needs me,” that gap exists in every organization regardless of licence.
Copilot versus Carly on Teams
| Need | Microsoft 365 Copilot | Carly |
|---|---|---|
| Summarize and search one organization’s Teams | Yes | Yes |
| Recap a meeting nobody recorded | No, needs transcription or recording | n/a |
| Work without an administrator granting anything | No, licence is assigned | Yes |
| Hold two organizations at once | Not a supported concept | Yes |
| Name which organization an instruction means | No | Yes |
| Reach a client tenant you have no licence in | No | Yes |
| Act when a message arrives | No Teams trigger | Yes |
Carly authorizes per identity, so two organizations sit side by side as separate connections you can name in an instruction, and the second one does not require that client’s administrator to license anything for you. It also acts on the message rather than on a prompt or a recording: the mention lands, the escalation is caught, the reply goes out.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Microsoft Teams.
Quick fixes
| Problem | Fix |
|---|---|
| Copilot cannot recap yesterday’s meeting | Transcription or recording was not enabled. Copilot cannot reference meeting content afterwards without one |
| No Copilot in a client’s Teams | Their administrator has not licensed it for you. Not something you can configure from your side |
| Copilot appears in one org and not another | Expected. Licences are assigned per organization in that tenant’s admin center |
| You want one Copilot across two tenants | Not a supported concept. The tenant is the isolation boundary |
| Multi-tenant organization looks like the answer | It is for one company owning several tenants, not unrelated clients, and its documentation never mentions Copilot |
| A guest account did not bring Copilot with you | Guest access puts you in their directory, where your licence does not exist |
| No connector box anywhere in Copilot | Expected on both SKUs; the MCP surface is admin and maker gated |
Frequently asked questions
Can Microsoft 365 Copilot work across two Teams tenants?
No. Copilot is licensed per user inside one organization and grounded by that tenant’s Entra authorization, so two organizations are two identities with two separate licensing decisions. There is no setting that spans them.
Does Copilot follow me when I switch organizations in Teams?
No. Switching organizations puts you in that directory as a different user, and Copilot availability there is that organization’s configuration. Teams has handled multiple organizations for years; Copilot’s licensing model was not built to travel with you.
Will a multi-tenant organization setup fix it?
Probably not. It is designed for a single company that owns several Entra tenants, depends on reciprocal provisioning of users between them, and Microsoft’s documentation for it does not mention Copilot at all.
Can I paste a connector URL into Copilot myself?
Copilot exposes no paste-a-URL box to ordinary users on either SKU. An administrator can add an MCP Base URL in the Microsoft 365 admin center, though those connectors are read-only, and a maker can add one in Copilot Studio, which is the route that carries write actions.
Does Copilot work in a shared channel?
Undocumented. A shared channel is the right structure to ask for, because it uses Entra B2B direct connect rather than guest accounts and so keeps you in your own tenant. Whether Copilot grounds on that channel’s content is not something Microsoft states either way, so verify it against history you can check.
Related: Multiple Teams accounts in Grok · Multiple Outlook accounts in Copilot · Multiple SharePoint sites in Copilot · Copilot plugins · Best AI assistants for Microsoft Teams · Microsoft Teams integration
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
