How to Connect Multiple Google Drive Accounts to Copilot
Copilot holds one Google account per connector and cannot write to Drive at all, so Carly is where two Drives actually meet. Consumer Copilot at copilot.com authorizes a single Google sign-in and Microsoft documents no way to add a second. Microsoft 365 Copilot, the paid work SKU, never signs into your Drive: it reaches Drive only through an admin-deployed connector against a whole Workspace domain.
What one chat can do afterwards
- Search a personal Drive and a Workspace Drive in the same question.
- Say which account each version of a document lives in.
- Rename a file to your convention and file it in the right folder.
- Save an attachment to the Drive that owns the engagement.
- Act when a document lands, rather than when you remember to ask.
- Reach a client Drive you were granted access to, with no admin project.
Nothing is copied into a shared index. Each Google account stays separately authorized, and Carly keeps them individually addressable.
Consumer Copilot: one Connect per service
The documented path is short. In Copilot, select your Profile and then Connectors. Select Connect next to the service you want, then authorize Copilot against your personal Microsoft or Google account. In a conversation you toggle connectors with the + icon and Use connectors.
There is one Connect control per service and Microsoft documents no way to add a second Google account behind it. Nothing states that a second account is forbidden, which is worth being precise about, but nothing describes adding one either. There is also an account-match rule that catches people out: if you sign in to Copilot with a personal Microsoft account, it must match the account you use for OneDrive or Outlook.
What the connector does is retrieval. Every documented example is a lookup: find my budget spreadsheet, show me all PDFs, show me the files I worked on last week. Microsoft states that Copilot does not store, modify, or expand your access. Nothing in the Google Drive connector writes to Drive.
Microsoft 365 Copilot: a service account, not a sign-in
On the work side the setup runs through the admin centre: Copilot → Connectors → Gallery → Google Drive, then a Google Workspace domain, an admin email, and a service-account JSON key.
The prerequisites are the real gate. Microsoft states that to configure and deploy Copilot connectors you must be an AI administrator in the Microsoft 365 admin center, and that for prebuilt synced connectors such as Google Drive you need admin access to the external service, meaning Google Workspace Super Admin. Every scope requested is read-only: drive.readonly plus directory and audit read scopes. Microsoft describes Copilot connectors as read-only by default, unable to write back to external systems.
A consultant working across two clients would need to be Super Admin in both Workspace domains and AI administrator in the Microsoft tenant. Nobody working for two clients holds all three.
One default is worth changing before the first crawl rather than after: the deployment default makes all files accessible to anyone in Google Drive visible to all Microsoft 365 users in the tenant. Microsoft’s recommended setting restricts visibility to people who already have access. Permission changes also sync on full crawls only, so a revoked file can keep surfacing until the next full crawl finishes.
1. Sort your accounts
| Your situation | Native path in Copilot |
|---|---|
| One personal Gmail Drive | Consumer connector, read-only |
| Personal Drive plus a work Workspace Drive | No documented way to add the second |
| Your company’s whole Workspace domain | Admin project, if you are AI admin and Super Admin |
| Two Workspace domains, two clients | Only if you are Super Admin in both |
| A client Drive shared with your personal account | Neither product |
2. Connect each Google account to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Google Drive and click Connect.
- Authorize the first Google account.
- Repeat for every additional account, personal or Workspace.
- Choose Use another account if Google preselects the previous login.
- Verify each account after authorization.
No service-account key, no admin project, and no Super Admin role in anyone’s domain. Authorization happens per identity, on your side. If Workspace shows an administrator review message, ask the Workspace administrator to approve it and repeat the authorization.
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 accounts you connected at step 2 are usable immediately, and cross-Drive filing 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 filing or renaming. 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 account read-only
One account per prompt until routing is reliable:
In my personal Drive, find the current insurance renewal PDF and give me the expiry date. Do not change anything.
In my work Drive, list every file added to the Ford campaign folder in the last two weeks. Read only.
Then the question that needed both at once:
Find every version of the Databricks proposal across both my Drives, tell me which is newest, and say which account each copy lives in.
5. Reuse this routing prompt
Treat my Gmail Drive as Personal and my Workspace Drive as Work. Always say which account a file lives in before filing, renaming, or moving it. Never write to an account I have not named.
Then name the target per action:
Rename the signed Cisco contract in Work to our convention, file it under Clients/Cisco, and put a copy of the summary in Personal.
Native Copilot versus Carly
| Need | Copilot | Carly |
|---|---|---|
| Search one personal Google Drive | Yes, consumer connector | Yes |
| Index a whole Workspace domain | Yes, admin-deployed | Per identity instead |
| Respect existing Drive permissions | Yes | Yes |
| Hold two Google accounts at once | No documented way | Yes |
| Rename, move, or file a Drive document | No, read-only | Yes |
| Act when a file lands in a folder | No | Yes |
Copilot’s admin connector is the better tool for exactly one job: indexing an entire Google Workspace domain into a Microsoft tenant so everyone’s search improves at once. Carly is for the reader with two logins and no admin rights anywhere. It connects Drive per identity, several accounts at once, personal and Workspace together, with no service-account key. It writes as well as reads, and it fires on the event rather than waiting for a prompt: a file lands in the client folder, it gets read, renamed to your convention, filed, and summarized to you.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Google Drive.
Quick fixes
| Problem | Fix |
|---|---|
| The second Google account has nowhere to go | There is one Connect per service; Microsoft documents no way to add another |
| Copilot cannot see a file you can open | Confirm it is the same Google account you authorized, not a second one |
| A shared drive is missing from search results | Check the inclusion rules; private drives need a Google Group named |
| A revoked permission still returns results | Permission changes sync on full crawls only, so wait for the next full crawl |
| Comments on a document never appear | Comments and replies in Drive files are not indexed |
| No connector box anywhere in Copilot | Expected on both SKUs; the MCP surface is admin and maker gated |
Frequently asked questions
Can Copilot connect to two Google Drive accounts?
Microsoft documents no way to add a second one. Consumer Copilot shows a single Connect control per service, and the work product does not use a Google sign-in at all.
Does Microsoft 365 Copilot support Google Drive?
Yes, but as an administrator project rather than a user connection. An AI administrator deploys a synced connector against a Google Workspace domain using a service-account key, which also requires Google Workspace Super Admin on the Google side.
Can Copilot move or rename a file in Google Drive?
No. The consumer connector is search and retrieval, and Microsoft describes Copilot connectors as read-only by default and unable to write back to external systems.
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 do anything when a file lands in Drive?
No, there are no event triggers in either product. Consumer Copilot Tasks can run on a schedule, but Microsoft states that Tasks are user initiated and will not start without you specifically asking to start a Task, and a schedule is not a trigger.
Related: Copilot and Google Drive · Multiple OneDrive accounts in Copilot · Best AI assistants for Google Drive · Google Drive
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."
