Close-up of a person's hands typing on a laptop at a wooden desk with a notebook and coffee nearby

Microsoft 365 Copilot + Google Drive: What the Integration Can (and Can't) Do in 2026

Partly — Microsoft ships an official Google Drive Copilot connector, but it’s strictly read-only. It indexes files stored in Google Drive into Microsoft 365 so Copilot, Copilot Search, and Microsoft Search can ground answers in that content — find the file, summarize it, cite it — while honoring the file’s existing Google Drive sharing rules. It does not write: Copilot can’t create, edit, move, or rename a file in Drive through it, and the service account it authenticates with uses read-only OAuth scopes (drive.readonly). You can use the same connector as a knowledge source in declarative agents built in Copilot Studio — but that’s still retrieval, not action. And everything happens inside a Copilot session you’re driving; nothing watches your Drive between chats.

Here’s what the connector actually does, how to turn it on, where the ceiling is, and what to use if you want Google Drive-adjacent work that runs on its own.

What Microsoft 365 Copilot can actually do with Google Drive

Through the Google Drive connector (the only official path, and it’s read-only):

  • Answer questions grounded in Drive files. “Summarize the contents of the Q4 Roadmap from Google Drive” or “Find the latest project plan in Google Drive” — answered from indexed Drive content, with the file cited, without leaving Copilot or Teams.
  • Search Drive from Microsoft 365. Indexed files surface across Copilot, Copilot Search, and Microsoft Search using natural-language queries — “list all Google Drive documents modified in the last week,” “show me files larger than 50 MB.”
  • Respect Google Drive permissions. The connector retains the ACLs defined in Google Drive and maps identity via Microsoft Entra ID (or regex-based mapping when emails differ from UPNs), so a user only sees Drive content they can already open in Google.
  • Answer about sharing and metadata. “Who last edited the Marketing Strategy file,” “what permissions are set on the Budget file,” “retrieve the link to the Team Resources folder” — the connector indexes owners, modified time, last-modifying user, web links, and similar properties.
  • Ground custom agents. Developers can use the connector as a knowledge source in declarative agents built with Copilot Studio, the Copilot Studio agent builder, or the Microsoft 365 Agents Toolkit — still for retrieval, not writing to Drive.

How to set it up

This is a two-side job: a Google Workspace admin prepares the source, and a Microsoft 365 tenant admin deploys the connector.

On the Google side, per Microsoft’s admin setup guide:

  1. Create a Google Cloud project and enable the Admin SDK API and Drive API.
  2. Create a Google Cloud service account and generate a JSON private key.
  3. Add read-only OAuth scopes via domain-wide delegation — drive.readonly, admin.directory.user.readonly, admin.directory.group.readonly, and admin.reports.audit.readonly (the last one is required for the reports-API incremental crawl; the legacy incremental crawl was deprecated May 15, 2026).
  4. Copy the service account’s OAuth 2.0 client ID.

On the Microsoft side, in the Microsoft 365 admin center:

  1. Go to Copilot → Connectors, open the Gallery, and select Google Drive.
  2. Authenticate with the Google Workspace domain, an admin email, and the JSON private key; configure the crawl schedule.
  3. Set the access model — Only people with access to this data source (recommended, enforces Drive ACLs) or Everyone — and run the full crawl.
  4. Test in Copilot with something read-only: “List all files in Google Drive shared with me this month.”

The limits that matter

  • It’s read-only, full stop. The connector indexes Drive for grounding and search; it authenticates with drive.readonly scope and cannot create, edit, move, rename, or delete a file in Drive. There is no official write-back path, and no separate “Drive agent” that acts back the way a CRM Sales agent does.
  • Comments and folder metadata aren’t indexed. Microsoft’s docs state comments and replies in Drive files aren’t indexed, and folder-level metadata isn’t indexed — so “what did the reviewer say in the comments” won’t ground.
  • Agents ground, they don’t write. Using the connector as a knowledge source in a Copilot Studio agent still only retrieves Drive content. The agent can answer from it; it can’t push a file back into Drive.
  • No triggers, ever. The connector never fires on a Drive event. Copilot answers when you prompt it — a new file can land in a shared folder, a contract can be updated, a doc can be shared with the wrong person over the weekend, and nothing moves on its own.
  • Admin-heavy and tenant-scoped. Standing it up means a Google Cloud project, a service account, domain-wide delegation, and a tenant crawl — and access is bounded by your Microsoft 365 Copilot licensing and each user’s Google Drive permissions. There’s no standing watch on your Drive.

If you want Google Drive-adjacent work that runs on its own: Carly

The moment you want something to happen around Google Drive without you in the chat — a new file in a shared folder summarized and emailed to the team, a signed contract filed and logged to your CRM, a weekly digest of what changed in a Drive folder built and sent, a task created when a doc is shared with you — you’ve crossed past what a grounding connector is for.

That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a session:

  • Fires on events and schedules, 24/7, in the cloud. When a file lands in a Drive folder or a doc is updated, Carly reacts — summarizes it, emails the right people, files it, updates a record — while your laptop is closed.
  • Actually reads and writes. Google Drive is a native Carly integration, so Carly can create, move, and update files and pull content into the next step — not just surface files in a chat.
  • Sends, not just drafts. Carly drafts and sends email across Gmail and Outlook, books meetings, manages tasks, updates your CRM, and records meetings — the follow-through that stops at the chat with Copilot.
  • Builds the workflow by interviewing you. Tell Carly “when a new PDF lands in the Contracts folder, summarize it, email me the key terms, and log it to HubSpot” in plain English; it interviews you and builds it — no Google Cloud project, no service account, no admin center.

Carly connects to 200+ tools across 40+ categories natively, plus any other tool via your own API key. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations.

Microsoft 365 Copilot vs Carly

Microsoft 365 Copilot (Google Drive)Carly
Answer questions grounded in Drive filesYes (connector, read-only)Yes
Search Drive files in Microsoft 365YesVia the integration
Create / edit / move files in DriveNoYes, natively
Index comments and folder metadataNoVia the integration
Acts on Google Drive triggers / eventsNoYes
Weekly “what changed in this folder” digestNoYes
Sends email as part of the flowNoYes (Gmail + Outlook)
Works while laptop is closedNo (session-bound)Yes (cloud, 24/7)
SetupGoogle Cloud project + service account + admin centerDescribe it in plain English
PricingMicrosoft 365 Copilot license per userAI agents from $35/mo

Copilot’s Google Drive connector is a grounding layer that pulls Drive content into your chats. Carly is a teammate that acts on Drive files as they land.

Frequently Asked Questions

Does Microsoft 365 Copilot work with Google Drive?

Yes, for reading. Microsoft ships an official Google Drive Copilot connector that indexes Drive files into Microsoft 365 so Copilot and Microsoft Search can find, summarize, and cite them using natural-language queries. It’s read-only — it grounds answers in your Drive content but doesn’t write anything back to Drive.

Can Microsoft 365 Copilot create or edit files in Google Drive?

No. The connector authenticates with read-only OAuth scopes (drive.readonly) and exists purely to index Drive content for grounding and search. There is no official write-back path and no separate Drive agent that acts on files — Copilot can answer about your Drive, but it can’t change anything in it.

How do I connect Copilot to Google Drive?

A Google Workspace admin creates a Google Cloud project, enables the Admin SDK and Drive APIs, creates a service account with a JSON key, and grants read-only OAuth scopes via domain-wide delegation. A Microsoft 365 tenant admin then adds the connector in the admin center under Copilot → Connectors → Google Drive, authenticates with the Google domain and JSON key, sets the access model, and runs the crawl.

Can Copilot react to a new Google Drive file automatically?

No. The connector never fires on a Drive event — Copilot only answers when you prompt it, so a new file in a shared folder or an updated contract triggers nothing on its own. For “when a file lands, summarize it and email the team” or “when a doc is shared with me, create a task,” you need a trigger-based assistant like Carly, which integrates natively with Google Drive and runs in the cloud around the clock.


More: Best AI document assistants · Best AI agents for productivity · Claude + Google Drive · ChatGPT + 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."

Gus Ibrahim, Founder & Director, IHR