In October 2025, Microsoft launched Copilot connectors to Windows Insiders, introducing an innovative feature that allows users to interact with various personal services, such as OneDrive, Outlook, Gmail, Google Calendar, and Google Contacts, using natural language queries. These connectors enrich Copilot’s contextual understanding by seamlessly integrating multiple services, including third-party platforms.
Once activated, Copilot can autonomously retrieve context from linked accounts to provide answers to inquiries, locate files, access emails, or reference calendar events without the need to switch between applications manually. One specific connector, the Google Contacts connector, enables Copilot to access saved contact information like phone numbers and email addresses directly from a user’s Google account.

Initially, the rollout of the Google Contacts connector took longer than expected, but it is now generally available for all users accessing Copilot on the web and Android app. While some users have also reported access in the standalone Copilot Windows application, this feature has yet to reach all devices.
Having gained access to the Google Contacts connector on both my Copilot Android app and web version, my curiosity prompted me to test its functionality. To add an element of comparison, I also evaluated its performance against Google’s Gemini.
Linking Google Contacts to Microsoft Copilot
Activating the Google Contacts connector in Copilot can be achieved through three different methods, starting with the most straightforward approach:
- Open a chat in Copilot on the web and ask it to browse Google Contacts for a specific contact’s phone number.

Copilot will indicate that it requires consent to access your Google Contacts. Clicking the “Connect” button will present a prompt explaining the advantages of the integration. You can connect any Google account, not just the one you’re currently logged into. Proceed by clicking “Continue to Google Contacts.”

After initiating this process, you’ll encounter the familiar “Sign in with Google”interface. If you have previously enabled other Google connectors (like Drive, Gmail, and Calendar), a prompt will indicate that Copilot requires “additional access” to your Google account.

The permission window outlines the data that Copilot will access, including the ability to view and download your contacts to Microsoft’s Cloud. After granting the necessary permissions, return to the Copilot chat interface.
Alternatively, the second method involves enabling the Google Contacts connector using the connector icon located near the text field in Copilot. This option works similarly, guiding you through account sign-in and permission granting.

The third option allows users to enable the Google Contacts connector via Copilot settings. Simply click on your profile, navigate to Settings, select Connectors, and toggle the Google Contacts option to enable it.


To utilize each Google connector, you must sign in individually. As of now, only the Copilot web version has gained access to Google Contacts, while the standalone Copilot app is gradually rolling out this feature.
Testing the Google Contacts Connector in Microsoft Copilot
According to Microsoft’s official guidance, the functionality of connectors is limited to retrieving contact information, such as asking, “What is John’s email address?”
However, users cannot create or edit contacts directly through Copilot, nor can you send text messages to Google Contacts. A distinct feature, Phone Connection, introduced in the previous year allowed setting alarms, sending messages, and viewing notifications, but it was less reliable during testing.

Despite this, Copilot successfully retrieved phone numbers via Phone Connection. In contrast, querying for contact information using Copilot’s Google Contacts connector behaves differently. Initially, an inquiry for Mayank’s number failed, revealing that the contact’s information could not be located.

Subsequent attempts yielded more mixed results; while some queries successfully returned information, others did not. Notably, it seems setting a contact’s email address in their details influences whether Copilot can retrieve their phone number. For instance, after adding an email to Mayank’s contact info, Copilot successfully provided both his phone number and email address.

This peculiar behavior may stem from privacy considerations, limiting access to critical information based on how complete a contact’s details are in Google Contacts.
Copilot Connectors Versus Google Gemini
Microsoft’s Copilot enhances user interaction through connectors, while Google’s Gemini leverages Connect Apps to provide similar functionalities. Through user experience on various platforms, it appears that Copilot is somewhat behind in comparison with Gemini. Nonetheless, Microsoft’s early entry into AI development for an “Agentic OS”has yielded benefits, although public perception of their AI endeavors is mixed.
While Gemini is a more sophisticated AI, particularly in handling more complex queries, it struggles with basic tasks, such as fetching a contact’s phone number or initiating emails, which Copilot accomplishes with ease.
For reference, my Gemini PRO subscription has Connected Apps functionality activated for Google Workspace, including Gmail and Google Drive.

In contrast, since my Copilot is based on a free tier, I explored whether Gemini could swiftly retrieve Mayank’s phone number, expecting it to leverage its direct connection to Google Contacts.

Surprisingly, Gemini was unable to access his phone number, which may be attributed to the lack of explicit support for Google Contacts within their Workspace documentation. I anticipated that Gemini would straightforwardly present Mayank’s details, prompting actions such as sending a text.
While Copilot’s abilities are limited to retrieving information and drafting emails (with direct links to Outlook), it offers considerable ease of use compared to Gemini.

As expected, given Gemini’s connection to Gmail, it should excel in tasks like drafting emails; however, it also failed to generate a direct link complete with subject and body information, missing out on potential efficiency.

Only after I sent an email to Mayank through Gmail was Gemini finally able to recognize his email address, but it still could not fetch his phone number or provide a straightforward method to initiate contact via email.
In contrast, Copilot excels in utilizing its connectors to find necessary details, like phone numbers and email addresses, and can even draft an email with a link that directly opens Outlook with all necessary information populated. This capability exemplifies the utility that AI aims to provide.
While it is essential to critique Microsoft’s approach, which may appear overwhelming in branding, it is crucial to acknowledge how Copilot effectively utilizes data to construct meaningful interactions. This positions Copilot advantageously over Gemini, particularly regarding data-rich functionalities.
Concerns around privacy are valid; users wary of large corporations accessing their data have alternative options and can deactivate connectors with a simple toggle.

Leave a Reply