← AI PulseAug 18, 2026

Deep · news · Multi-source brief

Grok Connects to Microsoft SharePoint for Document Access

xAI has introduced a SharePoint connector for Grok, enabling users on Grok Business and Enterprise plans to search, read, and upload files across their organization's SharePoint sites and document libraries.

By Illumora Editorial

Source · Aug 18, 2026, 3:09 AM · On Illumora · Aug 18, 2026, 3:43 AM

Media from the primary source — shown here so you can stay on Illumora.

Synthesized from multiple allowlisted primaries on the same event. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — SharePoint Connector | SpaceXAI Docs
Save

xAI has released a SharePoint connector for Grok, available to users on Grok Business and Enterprise plans. This connector allows Grok to access files and documents within an organization's SharePoint sites and document libraries. Users can search for documents, read file contents, and browse folder structures directly from a conversation with Grok.

Before team members can utilize the SharePoint connector, a team administrator must add it through the console. This setup involves a one-time configuration process.

Key Points

  • The SharePoint connector is available on Grok Business and Enterprise plans.
  • It enables Grok to search, read, and upload files across SharePoint sites and document libraries.
  • A team admin must add the connector via the console, a one-time setup.
  • Admins select how Grok accesses SharePoint, choosing between delegated or application-level permissions.
  • A Microsoft 365 administrator must approve Grok's access to SharePoint.
  • Write access (uploading and creating files) requires a separate Microsoft Entra application and consent flow.
  • Grok only indexes SharePoint content when necessary to answer questions and does not use this data for model training.

Context

According to xAI, the SharePoint connector uses the Microsoft Graph API and requests specific OAuth scopes during sign-in. Permissions are delegated, meaning Grok can only access content the signed-in user already has access to. For quick searching, Grok runs a background sync that indexes SharePoint content. This sync operates using either delegated mode, running as a dedicated user account, or application mode, running as the Microsoft Entra application itself. Indexed content is access-checked against the querying user on every request, ensuring team members only see results they are authorized to view.

For OneDrive, a separate connector allows browsing, reading, and uploading files in personal cloud storage, also available on Grok Business and Enterprise plans. Similar to SharePoint, OneDrive access requires admin setup and individual user connection. xAI states that for full-text search across OneDrive files, connecting the SharePoint connector is recommended, as OneDrive for Business files are stored on SharePoint infrastructure. xAI also offers a Salesforce connector, which provides real-time access to Salesforce organizations, respecting existing user permissions and not storing records on xAI servers.

Why It Matters

This connector provides builders with a method to integrate Grok into existing Microsoft 365 environments, potentially enhancing document management and information retrieval workflows. The emphasis on granular permissions and data privacy, including explicit statements about no model training on user data, addresses key concerns for enterprise deployments.

What To Do

  • Review the SharePoint connector documentation for detailed setup instructions for team administrators.
  • Compare the delegated and application-level permission options to determine the most suitable access mode for your organization's security policies.
  • Note the separate consent process required to enable write access for file uploads.
  • Examine the OAuth scopes requested by the connector to understand the specific permissions Grok will utilize.

Keep Exploring

/atlas/**grok**-family /techniques/system-user-separation /studio?pack=foundation