Skip to content
All insights

AI4 min read

Gemini Enterprise on Microsoft 365: Fix Identity Before You Connect Anything

Team gathered with laptops in a meeting room

You don't have to leave Microsoft 365 to use Google's AI. You do have to fix identity first.

This month we connected Gemini Enterprise to Outlook and SharePoint for a company that runs on Microsoft 365. No email migration. No moving files. People now ask questions across their own mail and documents, and only see answers from what they could already open.

The connectors took minutes. Four identity decisions took the real thinking. Here is each one, where the built-in connectors stop, and the checklist we now run before connecting anything.

Your team asks Gemini Enterprise a question. A connector reaches Outlook and SharePoint, where mail and files stay. Underneath, identity decides what each person can see in every answer.
Gemini Enterprise reaches Microsoft 365 through connectors. Identity decides what each person sees.

Two ways to connect

Gemini Enterprise reaches Outlook and SharePoint in one of two ways:

  • Federated search asks Microsoft 365 live, when someone asks a question. Content isn't copied, and results follow each person's own permissions.
  • Data ingestion indexes content for deeper search and better reading of complex files. For Microsoft 365, Google requires Microsoft Entra ID with Workforce Identity Federation for this mode.

Either way, the connector is the easy part. Whether the right people see the right answers comes down to identity.

Connecting Outlook and SharePoint took minutes. Four identity decisions took the real thinking: one identity provider, a break-glass admin, automatic user and group sync, and read before act.
Connecting took minutes. The four identity decisions were the project.

The four identity decisions

1. One identity provider per app

Mixing Microsoft Entra ID and Okta broke a connector until we picked one.

Gemini Enterprise takes one identity provider type per location (global, US or EU). If you ingest Microsoft 365 data, Google requires Entra ID with Workforce Identity Federation, and document access is controlled with Entra ID groups, even when another provider handles sign-in. Switching later is costly: users lose their chat history, and ingested data stores may need rebuilding.

Decide once, write it down, and set it up before the first connector.

2. A break-glass admin

When every sign-in runs through one identity provider, a problem there can lock everyone out, including the admins who would fix it. Google's guidance is to keep emergency-access accounts in Cloud Identity or Google Workspace, outside single sign-on and protected with a security key, so at least one administrator can always reach your organization.

Keep it to one or two named accounts, store the credentials offline, and test the sign-in before you need it.

3. Automatic user and group sync

Access should follow people when they join, change teams or leave, without anyone remembering to update it. That means syncing users and groups from your identity provider automatically (SCIM), not by hand.

With Entra ID, Google notes SCIM is needed to read large numbers of groups, and sign-in tokens drop group IDs once a user is in more than 150 groups (SAML) or 200 (OIDC), which shows up as access errors. Map people by lowercase email address, not by Entra object ID, which Google warns causes sign-in errors and duplicate licenses.

Leavers matter most. Offboarding in the identity provider removes access, and Google provides a way to delete a departed user's identity so it can't be reused.

4. Read before act

The Outlook connector does more than search. It can send mail, reply, forward and create calendar events. Search needs only read permissions (Mail.Read, Calendars.Read, Contacts.Read). Sending needs Mail.Send, which lets the app send mail as your users.

Actions are switched on and off per data store. This customer turned off sending email from Gemini for phase one. Start read-only, and add actions once the team trusts the answers.

Bringing Gemini Enterprise to your team?

Start with a free AI readiness review. We find the first workflow worth automating, then connect it with the right permissions.

Free AI readiness review

Tell us where to reach you. One of our engineers will get back to you within one business day.

Where the built-in connectors stop

The Microsoft connectors cover the common case well. Know the edges before you promise anything:

  • Exchange Online only. Hybrid, on-premises mailboxes can fail to connect.
  • One tenant per data store. A data store can't span Microsoft tenants.
  • Federated SharePoint search is shallow. Around 20 results per query, no search inside attachments, and weaker reading of scanned or complex PDFs. Ingestion handles those better.
  • Ingestion needs matching emails. Each person's Google and Microsoft email addresses must match, or their results go missing.
  • Three locations. Data stores run in the global, US or EU location only.

Past those edges, a custom connector or agent is the next step.

Example: a SharePoint Finance site shared with everyone except external users. Gemini follows permissions, so any employee who asks about salary bands gets an answer from that site. Fix the sharing before you connect.
An illustrative example: Gemini follows permissions, so a site shared with everyone gives answers to everyone.

The 5-question checklist

Run this before you connect anything:

  1. Which identity provider signs people in? One per app, chosen before setup.
  2. Who is your break-glass admin? Outside single sign-on, with a tested sign-in.
  3. Do users and groups sync automatically? Including leavers, on the day they leave.
  4. Which SharePoint sites are over-shared? The one most teams skip. Gemini never widens access, but it makes existing access easy to use: a site shared with "Everyone except external users" becomes an answer for everyone. Review sharing on sensitive sites first.
  5. Which actions are on for phase one? Start read-only, and switch on sending later.

How D3V helps

We set up Gemini Enterprise for teams on Google Workspace and on Microsoft 365, identity first: the provider, emergency access, group sync, a sharing review and the connectors, then one real workflow. D3V is a Google Cloud Premier Partner, and we start with a free AI readiness review.

Sources (Google Cloud documentation): Configure identity provider; Best practices for using Workforce Identity Federation; Microsoft Outlook connector; Microsoft SharePoint connector.