By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Cookie Policy for more information.
Your AI is only as smart as the content it can reach. We are obsessed with turning scattered information into smooth, people-first experiences. If your best ideas are trapped in Google Drive while Microsoft 365 Copilot waits in another lane, your teams feel the friction - and so does your bottom line.
That stops today. Here's a clear, generous, and action-oriented guide that walks you step by step through building a Copilot Connector that plugs Google Drive (or any external repository) straight into the Microsoft Graph. No fluff, just practical moves you can apply right away:
Pick the perfect approach We compare Graph Connectors and Copilot Agents so you choose the right fit from day one.
Secure the pathway Set up the Azure AD app registration and permissions without compromising compliance.
Map the metadata Teach Copilot who can see what, so every answer respects your security model.
Deploy, index, test Follow our proven checklist to light up the connector and verify it’s humming before rollout.
Unlock real-world scenarios See how unified search, chat, and summaries elevate the employee experience - exactly what 2toLead is known for.
Grab your admin creds and a cup of coffee. Let’s bridge those silos, amplify Copilot, and give your people the seamless, intelligent workplace they deserve.
The Solution
Microsoft 365 Copilot, combined with Microsoft Copilot Connectors and Copilot Agents, offers a seamless way to integrate Google Drive content into the Microsoft 365 ecosystem. This integration enhances productivity by providing unified access to all relevant data. By breaking down data silos and leveraging AI-driven tools, businesses can unlock new levels of efficiency and collaboration.
Prerequisite Steps
1 - You will need the Google Workspace Super Admin Role
The Google Drive connector requires a service account key generated by a Google Cloud Platform console project. You can use an existing project you own or go to the Manage resources page in the Google Cloud Platform console and click Create Project.
Note the project ID (which is directly below the project name) as you'll need it when enabling APIs in step 3.
3 - Enable the required APIs
Go to the following links and enable the Admin SDK and Google Drive APIs.
Remember to replace [PROJECT_ID] with your project ID.
Go to the Service Accounts page in the Google Cloud Platform console and click the project you created.
Click Create Service Account.
Enter the service account name, ID, and description (optional), then click Create and Continue.
Skip Grant this service account access to project and Grant users access to this service account. Click Done.
Back on the Service Accounts page for your project, you should now be able to see the service account that was created. Click the three dots below Actions and click Manage Keys.
Click Add Key > Create New Key. In the panel that appears, select the key type JSON then click Create.
A private JSON key is saved to your computer. You will need this to set up the connector.
5 - Add the OAuth scopes to your service account
Go to Google Workspace Admin console and click Security > Access and data control > API controls in main menu.
Click MANAGE DOMAIN WIDE DELEGATION in section Domain wide delegation:
Click Add new to add required scopes to the service account
How to obtain Client ID? Go to Google Cloud console, click service account in main menu, copy the "OAuth 2 Client ID" of the service account.
Click on Add Connection and select the Google Drive connector.
2 - Configure Google Drive Connector
Display Name: Google Drive
A display name is used to identify each reference in Copilot, helping users easily recognize the associated file or item.
Display name also signifies trusted content.
Google Apps Domain: your-company.com
To sign up for Google Workspace, you need an internet domain name, like your-company.com.
Authentication Type: Google Service Account
Google Apps administrator account email: user@your-company.com
Enter the email of a Google Apps administrator account in the user@company.com format.
Service Account Key: <PASTE THE ENTIRE JSON SERVICE ACCOUNT KEY FILE>
Copy and paste the content of private key file that you created in the prerequisite steps.
Select Authorize
Roll out to a limited audience (optional)
Deploy this connection to a limited user base if you want to validate it in Copilot and other search surfaces before expanding the rollout to a broader audience.
3 - Select Custom Setup
Under the User tab > Access Permissions > select Only people with access to this data.
Access permissions determine which users in your organization can access each item in Copilot or Search surfaces.
Choose whether indexed data is visible to everyone in the organization or only to users who have access to them in the data source. (recommended)
Under the Crawl tab configure how often incremental crawls and full crawls occur.
By default, incremental crawl is set for every 15 minutes, and full crawl is set for every day. If needed, you can adjust these schedules to fit your data refresh needs.
Full Crawl vs. Incremental Crawl
Full Crawl
Synchronizes all data at scheduled intervals.
Crawls the entire data source.
Updates the index with all items.
Reflects any deletions from the data source in the index.
Updates the permissions.
Incremental Crawl
Updates only the changed or new data.
Only updates items that changed since the last crawl.
Doesn't handle deletions, so items removed from the data source remain in the index.
Incremental crawls do not currently support processing of updates to permissions.
4 - Click Create
Setup Copilot Agent
1 - Navigate to Microsoft Copilot Studio and create a new agent to be used within Microsoft 365 Copilot.
Go to copilotstudio.microsoft.com > On the left navigation rail, select Agents then select Copilot for Microsoft 365.
Select the Agents tab then select the + Add Agent button.
In the top right corner select Skip to configure.
2 - Name the agent and select where it will be stored.
Enter a name for your agent.
Select the ellipsis then select Edit advanced settings.
Use the solution dropdown to select the Power Platform solution where your agent will be stored, then select Save.
3 - Fill in Description, Instructions and Starter Prompts.
Description: Use your own words to describe what your agent should help with, including your audience and end goal.
Instructions: Direct the behavior of the agent, including its tasks and how it completes them.
Strater Prompts: Suggest ways of starting conversations.
Knowledge: Do not configure a knowledge source just yet. To add the Google Drive Graph Connector as knowledge you must first create the agent. You will notice the option to select the connector is greyed out until you create the agent.
4 - Create the Agent
Click Create in the top right corner.
5 - Add a knowledge source
Select + Add Knowledge
Select the Advanced filter then select Google Drive
Select Google Drive then select Add
6 - Publish the agent
In the top right corner select Publish.
In the pop-out window, fill in a short description, long description and developer name, then select Publish.
Select Show to everyone in my org to submit for admin approval to appear under Built by your org section. Then select Done.
7 - Ask an admin to approve the Google Drive Agent.
Go to the Microsoft 365 Admin center > Settings > Integrated Apps > Requested Apps > Google Drive Agent > Publish.
8 - Use Google Drive Agent in MS Word
Example: Summarize a resume
In MS Word, open Copilot > Select the 3 lines > Select Get Agents
In the pop-out window, Select Built for your org > Google Drive Agent > Add.
Select a starter prompt > Insert document name > submit prompt and wait for response > Select insert if you want to use the response in your new document.
Why It Matters
Integrating Google Drive content into Microsoft 365 Copilot isn’t just a technical win. It’s a strategic shift in how your organization accesses knowledge, collaborates, and makes decisions. It’s about connecting your people to the knowledge they need—wherever it lives.
Make Copilot Truly Cross-Platform
Unify Knowledge
Copilot is only as good as the data it can reach. Break down app barriers—Copilot becomes a single pane of intelligence. You’re not just indexing files—you’re unlocking intelligence.
Boost ROI
You’ve already invested in Google Drive. You’ve already licensed Microsoft 365 and Copilot. Maximize value from both Google and Microsoft investments.
Reduce Friction
Your teams work where they’re comfortable, without compromise. Employees shouldn’t need to know where a file lives to get work done.
Future-Proof Ops
Get ahead of AI-powered workflows spanning multiple data sources. Maintain Governance: With Graph Connectors and Copilot Agents, you preserve security and compliance. Permissions stay intact, sensitive content remain protected and admins retain control and visibility. You gain access without giving up control.
Are you bridging the gap between your collaboration tools and your AI assistants?
Let’s talk about how to surface high-value content—wherever it lives—to power smarter decisions with Copilot.
Explore Other Insights Around SharePoint & Copilot Features:
