Grok’s SharePoint connector searches across sites automatically, which is more than most assistants manage. The catch is that your permissions are not the ceiling. Grok answers out of a background index, so what it can find is whatever an admin chose to index, narrowed again by what you personally can open. Two gates, not one. That is the part xAI’s own capability wording understates, and it is where the SharePoint question on Grok stops resembling the same question on ChatGPT or Claude. Carly holds your Gmail and Outlook mailboxes, both sets of calendars and your drives in the same place.

One orientation note. “Grok” now names three products: the consumer assistant at grok.com and in the mobile apps, Grok Bot for Slack and GitHub, and the Grok API. This page is about the first one. xAI’s own FAQ says Grok Bot “is not the same as Grok on grok.com or the Grok mobile apps,” and its file behaviour is a separate story.

Two gates decide which sites Grok can see

xAI’s capability list opens with “search documents across all SharePoint sites you have access to.” Read on its own, that sounds like your Microsoft permissions are the boundary. They are the second boundary.

The first is the index. Under its permissions section, xAI states that “Grok runs a background sync that indexes SharePoint content so it can be searched quickly,” using a set of scopes chosen by whichever access mode the admin picked. Then the safety net: “indexed content is access-checked against the querying user on every request, so regardless of which sync mode is in use, team members still only see results they are individually authorized to view in SharePoint.”

Both sentences are true and together they say something neither says alone. Grok surfaces a document only if the sync indexed it and your account can open it. A site you can open in a browser this second is invisible to Grok if the index never covered it, and nothing in the interface distinguishes an empty site from an unindexed one.

That is the honest headline for the sites axis. On ChatGPT and Claude, several sites inside one tenant are mostly a permissions question: if your account can open the site, the connector can generally read it. On Grok an administrative decision sits above your permissions and can be narrower than they are.

Note the contradiction in passing. xAI’s general connector line says data is accessed in real time and not stored, and this page says Grok “only indexes SharePoint content when needed to answer your questions.” Both sit awkwardly beside the background sync. All of it is current documentation, we are not picking a side, and the practical move is to treat SharePoint as indexed rather than read live.

The access mode the admin picks is the whole site story

Grok is the only assistant in this category that asks an administrator to choose how SharePoint is reached. The two documented modes narrow the site set differently.

Delegated permissions, which xAI marks recommended, scope Grok by Sites.Read.All and by the connecting account. The recommendation is deliberately narrow: “create a dedicated user account with access limited to specific SharePoint sites, then connect using that account. Because delegated permissions are bounded by the connecting account’s own access, this limits Grok to only the sites that account can see.” So the indexing identity is built restricted, widening what it can open is what widens Grok’s reach, and no Azure portal work is needed.

Application-level permissions use Sites.Selected and an explicit allow list. After consent the console shows a site picker, and xAI is blunt: “only sites added here will be reachable through the connector.” The fix for most missing-site complaints is the next clause: “sites can be added or removed later from the connector settings.”

Neither mode asks anything of you at query time. There is no per-site toggle in the chat and no way to point Grok somewhere it was not indexed.

One tenant field, and a list of site IDs

Sites and tenants get different answers, and the product’s own configuration shows why.

Setup asks a team admin for “the organization’s Microsoft Entra (Azure AD) tenant identifier,” accepted as “either a domain like xai.onmicrosoft.com or a GUID.” One field. Alongside it, “a Microsoft 365 administrator must approve Grok’s access to SharePoint. This is a one-time authorization for the entire organization.” Across all of xAI’s documentation the word tenant appears exactly twice, here and on the OneDrive page, singular both times.

The code that runs grok.com in your browser matches that shape: a single tenant identifier, an auth mode, and an array of allowed site IDs. Many sites are a first-class list; a second tenant is a scalar with one slot. That is not documentation and is no promise about behaviour, but it explains why the two questions feel so different in practice.

The verdict, precisely: xAI does not document a second SharePoint connection either way, and nowhere states that one is refused. That is silence, not a refusal. The tenant field is structural rather than a matter of policy wording, so plan for one tenant. Consultants, agencies and anyone holding a guest account in a client’s Microsoft 365 hit this, and they hit it on every rival too, as our best AI assistants for multiple Microsoft accounts comparison covers.

Four documented verbs, and write replaces read

xAI’s capability list for SharePoint is four bullets, and the fourth is gated twice.

Action	Documented?	Tier
Search documents across all accessible sites	Yes, cross-site search is named explicitly	Read
Read files by downloading content from any accessible library	Yes	Read
Browse folders and list drives	Yes	Read
Upload artifacts Grok generated	Yes, opt-in	Write
Overwrite an existing file	Only in the scope warning, not the capability list	Write
Create or edit SharePoint lists or pages	Not documented	Not documented
Delete, rename or move a file	Not documented	Not documented
Share a document with someone	Not documented	Not documented

The read scopes are Sites.Read.All, Files.Read.All, User.Read and offline_access, with Files.Read.All justified as “required for cross-site document search.” That line is the clearest confirmation that search really does span sites rather than one library at a time.

Write is not a checkbox on the same connection. xAI describes a separate Microsoft Entra application with its own consent flow, reached with an Enable Write Access button in the console, granting Files.ReadWrite.All and “independent of the read-only consent.” Then a second gate that catches teams by surprise: “write access is not enabled by default for team members, even when the admin has approved the write application.” Each person opts in individually from the connectors page.

One unusual detail to plan around: the write scope is substitutive, not additive. xAI’s warning reads, “when write capabilities are enabled for your organization, the connector requests Files.ReadWrite.All instead of the read-only scopes above.” Turning writes on changes what every connection asks for rather than adding to it, which is a different conversation with a security reviewer than a narrow extra permission would be.

Nothing fires when a document changes

Grok closed part of the event gap in July 2026. Scheduled automations are open to everyone and email triggers come with SuperGrok, matching on sender, recipient, or subject. The limit is that the inbox is the only thing it watches, so anything that happens in another app still has to be noticed by a person first.

For SharePoint specifically that leaves nothing. There is no site, library, folder or file trigger in any xAI document, and no page at all for automations beyond the July 2026 announcement. A contract landing in a shared library starts nothing, a document being edited starts nothing, and a daily scheduled search of a site is the nearest substitute. More detail in Grok Automations.

The launch post promises verbs the documentation never exposes

If a guide told you Grok edits SharePoint pages, it was reading xAI’s May 6 2026 launch announcement rather than the connector documentation. The announcement says Grok “can search, read, and synthesize the latest files, lists, and pages across your organization,” and that “with write permissions enabled, Grok can also create, edit, and update documents, lists, and pages,” crediting advanced document editing to Grok 4.3.

The connector documentation exposes no list verb, no page verb, and no create, edit or update. Its write bullet covers uploading artifacts Grok generated. The announcement also never mentions the plan gate, and it predates the Teams and Salesforce connectors entirely. Third-party roundups tend to inherit it.

The plan gate is itself contradicted inside xAI’s documentation, worth knowing before you hunt for a missing menu item. The connectors index says “connectors are available to all Grok users.” The SharePoint page opens with “available on Grok Business and Enterprise plans only,” and only OneDrive carries the same banner. Both are current. If SharePoint is absent on a consumer plan, the gate is the likelier explanation. Our Grok connectors overview tours the whole set, and Grok for Microsoft 365 covers the Office side.

Three SharePoint connectors exist in the app, and xAI documents one

This section is an observation, not advice, and the distinction matters.

The code behind grok.com carries three separate SharePoint connector types rather than one. Alongside the documented connector there is a read/write variant, hidden from the normal list and given its own write-access screen, which lines up with the separate write application the documentation describes. The third is labelled SharePoint Direct, with consent copy identical to the documented connector’s, and it asks for no tenant identifier and no access mode.

Nothing about SharePoint Direct appears in any xAI document. We could not confirm it is reachable, which plan it belongs to, or whether it is switched on for anyone, so do not plan on it. It is worth flagging only because it hints that the tenant-and-console requirement may not be permanent. The same code carries a team setting labelled Self-serve, described as letting members add connectors for the team themselves, off by default and equally undocumented. If it applies to SharePoint, the blanket “a team admin must add the connector” rule has an exception nobody has written down.

1. Sort your case

What you have	Native path in Grok
A Grok Business or Enterprise plan	Yes, once an admin provisions it
A consumer or SuperGrok plan	Gated per the SharePoint page
A consumer Microsoft account	No path, work or school sign-in only
Several sites in one tenant, delegated mode	Yes, as far as the indexing account reaches
Several sites in one tenant, application mode	Yes, for sites on the allow list only
Keyword search spanning those sites	Yes, cross-site search is documented
A second tenant’s sites	No slot, setup takes one tenant ID
Uploading a file Grok produced	Yes, after org consent and your own opt-in
Editing a list or a page	Not documented, despite the launch post
Acting when a document lands	No file trigger of any kind

2. Have a team admin provision the connector

1. Sign in at console.x.ai and select the team.
2. Open Grok Business then Connectors and choose + Add Connector, then SharePoint.
3. Pick an access mode: delegated, which xAI recommends, or application-level.
4. Enter the Azure AD Tenant ID, either a domain such as contoso.onmicrosoft.com or a GUID.
5. Handle consent: Approve as admin, Copy link for your IT admin, or Skip for later.
6. In application mode, add every site Grok should reach to the allow list.
7. Optionally click Enable Write Access and complete the second consent flow.

xAI notes that skipping consent has a consequence rather than just a delay: “team members will not be able to authenticate until consent is granted.” Adding or removing connectors needs Team Read-Write permission.

3. Connect your own Microsoft account

1. Go to grok.com/connectors, or Settings then Connectors on iOS and Android.
2. Find SharePoint and click Connect.
3. Sign in with your Microsoft work or school account.
4. Review the requested permissions and click Accept.
5. If the admin enabled writes, opt in separately from the connectors page.

If SharePoint is not in the list, check plan first, then whether an admin provisioned it, then whether the Microsoft 365 consent was ever approved.

4. Add OneDrive only once you know what it adds

Anyone wanting both Microsoft storage connectors should know the dependency runs the opposite way to most expectations. xAI’s OneDrive page sends search here: “for full-text search across your OneDrive files, connect the SharePoint connector as well,” because OneDrive for Business files live on SharePoint infrastructure and are indexed by SharePoint document search.

OneDrive contributes browsing and upload; SharePoint does the searching for both. The pair means two connectors, both Business and Enterprise only, both needing their own Microsoft 365 admin consent, and still one tenant between them. Our multiple OneDrive accounts in Grok page has the drive-side detail, and OneDrive versus SharePoint covers why the two overlap.

5. Connect each Microsoft tenant to Carly

1. Sign in at carlyassistant.com.
2. Open carlyassistant.com/integrations.
3. Find SharePoint and click Connect.
4. Authorize the first Microsoft identity and confirm the account name.
5. Repeat for every other identity, using a private window if Microsoft preselects the last login.
6. Verify each connection appears in the list before you rely on it.

Each tenant approves independently, so one administrator declining does not affect the others.

6. Add Carly to Grok

1. Go to grok.com/connectors.
2. Click New Connector, then select Custom.
3. Enter https://carlyassistant.com/mcp/.
4. Complete the authentication step.
5. Sign in to the Carly account holding the connections above.

Grok discovers the tools Carly exposes and offers them in conversation alongside its built-in connectors. On Grok Business and Enterprise a team admin provisions connectors in the cloud console first.

7. Test one site, then two tenants

One site per prompt until routing is reliable:

In the Contracts library on our Volvo tenant, list the five most recently modified documents and say which site each came from. Do not change anything.

Then the question that needs two real connections:

Search the Contracts library on our Volvo tenant and the client delivery site on the Ikea tenant for documents mentioning “change order” in the last 90 days, showing the source site and tenant on every row.

Then reuse a routing instruction so writes never guess:

Treat the Contracts and Marketing sites as Internal and the client delivery site as Client. State the target site and tenant before filing, updating or uploading anything, and never write to a site I have not named.

Grok versus Carly on SharePoint

Need	Grok	Carly
Search across several sites at once	Yes, cross-site search is documented	Yes
Reach a site without an admin indexing it first	No, the index is the ceiling	Yes
Available without a Business or Enterprise plan	No, per the SharePoint page	Yes
Set up without a tenant ID and org-wide consent	No	Yes
Hold two Microsoft tenants at once	No slot for a second tenant ID	Yes
Upload a generated document	Yes, after org consent and personal opt-in	Yes
Edit a list or a page	Not documented	Ask about the API path
Act when a document lands or changes	No file trigger	Yes

Grok earns real credit on the top row, and it is not a small one. Cross-site full-text search, named as such in the documentation and backed by a stated scope, is something most assistants in this category quietly do not do, and the per-request access check is careful design. xAI also publishes its scopes openly, documents both access modes rather than hiding the choice, and deletes indexed data when a member disconnects. One person, one tenant, a Business plan and a helpful admin is a configuration where this works well.

Carly is built for the parts the console forecloses. It authorizes per identity, so your own tenant and a client’s sit side by side as separate connections, with no tenant identifier, no console step and no organization-wide consent between you and documents you can already open. No indexing decision sits above your permissions either, so a site you can reach is a site the agent can reach. It also acts when the document appears rather than when a clock ticks, so a contract landing in a library can trigger the summary, the filing and the notification with nobody opening a chat window. For anything outside the native connector set, the API path is available and worth a conversation.

Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with SharePoint and OneDrive.

Quick fixes

Problem	Fix
SharePoint is missing from grok.com/connectors	Check the plan first; the SharePoint page says Business and Enterprise only
A guide says connectors are open to everyone	That is xAI’s connectors index, which the SharePoint page contradicts
A site you can open in a browser returns nothing	The index is the first gate; in application mode ask an admin to add it to the allow list
Search works on some sites and not others	Delegated mode is bounded by the indexing account, which is built narrow by design
An @outlook.com sign-in is rejected	Expected, the connector takes work or school accounts only
Grok will not upload a file	Org write consent and your own opt-in are separate steps, and opt-in is off by default
Grok will not edit a list or a page	Those verbs are in the May 2026 announcement, not in the capability list
A second tenant has nowhere to go	Setup takes one tenant ID; put shared content in a site the connected account can reach
Nothing happens when a document is added	There is no file trigger; a scheduled search is the closest substitute

Frequently asked questions

Can Grok search across multiple SharePoint sites?

Yes, and xAI documents it directly: search documents across all SharePoint sites you have access to, with Files.Read.All described as required for cross-site document search. The limit is that Grok answers from a background index, so the sites an admin chose to index are the real ceiling, narrowed again by your own SharePoint permissions.

Can I connect two SharePoint tenants to Grok?

xAI does not document a second connection either way, so this is silence rather than a stated refusal. Setup takes one Azure AD tenant identifier and one organization-wide consent, so plan for a single tenant and put cross-tenant content in a site your connected account can reach.

Why can Grok not find a site I have access to?

Most likely it was never indexed. In application-level mode only sites on the admin’s allow list are reachable, and xAI says sites can be added or removed later from the connector settings. In delegated mode the indexing account is deliberately scoped to specific sites, so widening that account’s access is the fix.

Does Grok need a Business plan for SharePoint?

The SharePoint page states it is available on Grok Business and Enterprise plans only, one of just two connectors carrying that banner. xAI’s connectors index says connectors are available to all Grok users, so the two pages disagree. A team admin also has to provision it in the console before anyone can connect.

Can Grok create or edit a SharePoint list or page?

Neither is documented. xAI’s May 2026 launch announcement says Grok can create, edit and update documents, lists and pages with write permissions enabled, but the connector documentation’s write bullet covers uploading artifacts Grok generated and nothing else. Test before relying on the announcement.

Will a Grok automation run when a document is uploaded?

No. Automations fire on a schedule for everyone and on an inbound email match on SuperGrok. No xAI document describes a SharePoint, file or library trigger, so a scheduled search is the closest substitute.

---

Related: Multiple OneDrive accounts in Grok · Multiple Outlook accounts in Grok · Multiple SharePoint sites in ChatGPT · Best AI assistants for SharePoint · Carly’s SharePoint integration

Related Articles

How-To

How to Connect Multiple Google Calendars to Grok

Aug 15, 2026

How-To

How to Connect Multiple Google Drive Accounts to Grok

Aug 17, 2026

How-To

How to Connect Multiple Notion Workspaces to Grok

Aug 17, 2026