How to Connect Multiple Slack Workspaces to Copilot
Microsoft builds no Slack connector for Copilot at all, so Carly is where a Slack workspace and an assistant actually meet. Slack appears nowhere in the Microsoft-built connectors gallery, which carries around 70 connectors; its Collaboration category holds Miro, Trello, Zoom, Notion and Linear. Slack exists only in the partner gallery, from RheinInsights and from ServiceNow, and neither is on Microsoft’s “Certified for Microsoft 365 Copilot” list. So “two workspaces” is not the first problem. Getting one workspace in front of Copilot at all is. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
What one chat can do afterwards
- Summarize what two client workspaces each decided about the same date.
- Say which workspace every answer came from.
- Reach private channels you are a member of, with no admin project.
- Post the revised timeline into the workspace you name.
- Log the same change in your own internal channel.
- Act within seconds of a message, rather than after the next crawl.
Nothing is merged. Each workspace stays separately authorized, and Carly keeps them individually addressable.
The admin wall, and what is behind it
Microsoft’s connector prerequisites are explicit: “you must be an AI administrator in the Microsoft 365 admin center”, and you also need admin access on the Slack side. That is the named role, not Global admin, and it is not you unless it is your job.
Licensing adds a second gate. Plain Microsoft 365 gets connector content into Microsoft Search but not into Copilot grounding. Grounding needs the Microsoft 365 Copilot add-on or E7. A Copilot Studio licence and Copilot pay-as-you-go are listed as agents only, with no Copilot grounding. The self-serve sync connectors currently in preview support exactly two sources, Confluence Cloud and Jira Cloud, and Microsoft states that self-serve sync connectors are Microsoft-published connectors only. Slack is neither.
The two partner rows are also not the same product. RheinInsights indexes public and private channels, messages, threads and attached files, with support for Slack’s permission model; it is self-hosted software with no published price. ServiceNow indexes messages, threads and shared files from all public channels only, which matters if the conversations you care about happen in private ones. Neither vendor documents direct message coverage, and neither publishes whether one licence covers a second workspace.
Consumer Copilot has none of this. Its connector list is OneDrive, Outlook.com, Google Drive, Gmail, Google Calendar and Google Contacts, with no Slack option and no way to add one.
Two opposite things people mean by this
Copilot reading your Slack is the connector story above. Content has to be crawled and indexed into Microsoft Graph before Copilot can ground an answer in it, and the crawl is scheduled: Microsoft’s deployment guidance sets refresh recurrence as daily, weekly, biweekly or monthly, with a repeat interval between 15 minutes and 12 hours. A message posted in a client workspace may not be searchable for hours.
A Copilot Studio agent answering inside Slack is the opposite direction, and Microsoft is blunt about the cost. Its documentation for connecting an agent to Azure Bot Service channels states that doing so “requires considerable developer expertise”, and the walkthrough uses Slack as its worked example: an Azure Bot Service subscription, the .NET 10 SDK, and a custom relay bot. None of that lets Copilot read a single Slack message.
A third thing looks like a bridge and is not. The Power Platform Slack connector inside Copilot Studio exposes Create a channel, Join a public channel, List public channels, Post message (V2), and Set do not disturb. No search, no read, no channel history. Its Power Automate trigger list is one entry, “When a file is created”, at a documented polling floor of 120 seconds. There is no new-message trigger anywhere in it.
1. Sort your workspaces
| Your case | Native path in Copilot |
|---|---|
| Many channels in one connected workspace | Yes, once an admin deploys a partner connector |
| Public channels, ServiceNow connector | Yes, once an admin deploys it |
| Private channels | Only via the RheinInsights connector |
| A client’s workspace you are a guest in | Not natively |
| Any workspace, no admin rights | No |
| Consumer Copilot, any workspace | No |
2. Connect each Slack workspace to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Slack and click Connect.
- Authorize the first workspace.
- Repeat for every additional workspace, including a client workspace you are only a guest in.
- Confirm each workspace is listed before you rely on routing.
No AI administrator, no partner licence, no Graph indexing job. The authorization happens on your side of each workspace.
3. Choose how Copilot reaches Carly
Copilot has no box where an ordinary user pastes a connector URL, on either SKU. Consumer Copilot ships a fixed connector list and its support page never mentions MCP. Microsoft 365 Copilot 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 workspaces you connected at step 2 are usable immediately, and cross-workspace routing is the point of them. 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 workspace read-only
One workspace per prompt until routing is reliable. A fictional consultant, Rosa Hallam, splits her week between her own workspace and two client ones:
In the Databricks workspace, summarize what was decided in #launch-planning yesterday. Read only.
In my own workspace, list every message this week where someone asked me for a deadline. Do not reply to anything.
Then the question that spans both:
Compare what the Adobe workspace and the Databricks workspace each agreed about the November launch date, and say which workspace each answer came from.
5. Reuse this routing prompt
Treat my own Slack as Internal and the client workspaces as Adobe and Databricks. Always state the target workspace before posting, replying, or filing anything. Never post to a workspace I have not named.
Then name the target per action:
Post the revised timeline to #launch-planning in the Databricks workspace and log the change in #accounts in my Internal workspace.
Native Copilot versus Carly
| Need | Microsoft 365 Copilot | Carly |
|---|---|---|
| Search many channels in one workspace | Yes, once a partner connector is deployed | Yes |
| Reach private channels | Only with the RheinInsights connector | Yes |
| Set it up without an AI administrator | No | Yes |
| Hold several workspaces at once | Undocumented, one connection each | Yes |
| Answer within seconds of a message | No, crawl runs every 15 minutes to 12 hours | Yes |
| Act when a message arrives | No | Yes |
Once a partner connector is in place, Slack content sits alongside SharePoint, Outlook and Teams in one tenant index with permissions enforced from the source, which is worth having if you run IT for a large organization. It is also an administrator project with a licence attached, which is the wrong shape for a consultant with three workspaces. Carly authorizes per workspace on your own side, holds several at once, and fires on the message arriving rather than waiting for the next crawl: a client posts a scope change in a channel, and it is read, summarized against the right account, dated on a calendar and passed to you, without a prompt.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Slack.
Quick fixes
| Problem | Fix |
|---|---|
| Slack is missing from the Copilot connectors gallery | It is not there; Slack is in the partner gallery only |
| A private channel never appears in results | The ServiceNow connector covers public channels only |
| Yesterday’s message is not searchable | The crawl interval runs between 15 minutes and 12 hours |
| Connector results show in Search but not Copilot | Grounding needs the Microsoft 365 Copilot add-on or E7 |
| Your Copilot has no connectors tab | Consumer Copilot has none; connectors are a work-tenant feature |
| 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 read Slack messages?
Only if an administrator deploys a partner connector from RheinInsights or ServiceNow, which indexes Slack content into Microsoft Graph. Microsoft builds no Slack connector itself, and neither partner connector is on the Certified for Microsoft 365 Copilot list.
Can I connect two Slack workspaces to Copilot?
Microsoft documents no limit on connection count, and setup is per data-source URL, so two connections is the implied model rather than a documented feature. Neither partner vendor publishes whether one licence covers a second workspace.
Can I set this up without being an admin?
No. Microsoft’s prerequisites require you to be an AI administrator in the Microsoft 365 admin center, plus admin access on the Slack side. The self-serve sync connectors in preview cover only Confluence Cloud and Jira Cloud.
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 respond when someone posts in Slack?
No. Copilot connectors crawl on a schedule set between 15 minutes and 12 hours, so nothing starts because a message arrived. Even Power Automate’s Microsoft-published Slack connector has only a file-created trigger, with no new-message trigger.
Related: Multiple Slack workspaces in ChatGPT · Best AI assistants for Slack · Copilot plugins · Multiple Gmail accounts in Copilot · Slack
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."
