How to Connect Multiple SharePoint Sites to Grok
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.
1. Add your SharePoint sites to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find SharePoint, click Connect, and authorize the site.
- Click Connect again for the next one, and keep going for as many sites as you want.
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.
Each tenant approves independently, so one administrator declining does not affect the others.
Carly connects to thousands of apps, so while you are on that page you can add your inboxes, calendars, CRM, and anything else you want Grok to reach through the same connector.
2. Add Carly to Grok
- Go to grok.com/connectors.
- Click New Connector, then select Custom.
- Enter
https://carlyassistant.com/mcp/. - Complete the authentication step.
- 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.
Have a team admin provision the connector
- Sign in at console.x.ai and select the team.
- Open Grok Business then Connectors and choose + Add Connector, then SharePoint.
- Pick an access mode: delegated, which xAI recommends, or application-level.
- Enter the Azure AD Tenant ID, either a domain such as
contoso.onmicrosoft.comor a GUID. - Handle consent: Approve as admin, Copy link for your IT admin, or Skip for later.
- In application mode, add every site Grok should reach to the allow list.
- 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.
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.
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.
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.
Sites and tenants get different answers, and the product’s own configuration shows why.
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 |
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 happening in another app still has to be noticed by a person first. Carly notices instead, across thousands of apps.
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.
This section is an observation, not advice, and the distinction matters.
| 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 |
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
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."
