AI for SharePoint
Surface the right SOP, runbook, or policy during live calls — across every SharePoint site your team supports. Through a Microsoft Graph app registration you own, scoped to the sites you choose.
Built by an MSP operator who ran Microsoft 365 for hundreds of client environments across 28 years.
Native SharePoint Capabilities
Client SOPs and Runbooks in Natural Language
Many MSPs store SOPs, runbooks, and client-specific process docs in SharePoint — not IT Glue. xop.ai indexes those libraries and surfaces the right document during live calls, regardless of which site it lives on.
You Decide Exactly What xop.ai Can Read
Access is something you grant and control — not a black box. xop.ai connects through an application-level Microsoft Graph registration that lives in your own tenant: you create it, scope it to the exact SharePoint sites you choose, and can revoke it in one click. It reads those sites and nothing else.
Multi-Tenant SharePoint for MSPs Who Support Microsoft 365 Clients
Many MSPs maintain per-client SharePoint sites for documentation or host shared content in their own tenant. xop.ai handles both patterns — a connection scoped to your own tenant for internal runbooks, or a separate per-client connection scoped to that client's sites.
Three SharePoint Workflows, Rebuilt
What actually changes when AI-powered search sits on top of SharePoint.
Engineer takes a call about a client's backup policy
Engineer searches SharePoint, opens the backup SOP, realizes it's from 2021, searches again, can't find the current one. Calls the client back later with the answer.
xop.ai searches across the client's SharePoint policy library, returns the current backup SOP ranked above stale versions, and surfaces the exact clause the engineer needs — mid-call.
Client-facing chatbot answers an employee HR question
MSP chatbot tells the employee to "contact HR" because it can't search the company's SharePoint policies. Defeats the point of self-service.
xop.ai's branded chatbot searches the SharePoint sites connected for that client, finds the HR policy, and returns the exact answer with a link to the source.
Onboarding a new engineer to a complex client
New engineer spends a week hunting through SharePoint sites, can't find the half the docs, asks the senior engineer for links repeatedly.
New engineer asks xop.ai conversationally. Every relevant document surfaces with a link to the source. Ramp time cut by half, senior engineer no longer blocked.
What SharePoint MSPs Are Seeing
Frequently Asked Questions
How does xop.ai integrate with SharePoint?
xop.ai uses the Microsoft Graph API with an application-level (app-only) registration that you create in your Microsoft 365 tenant. You grant it read access (Sites.Read.All, or Sites.Selected for least privilege) and choose which SharePoint sites it searches. It runs server-to-server, with no signed-in user. For each connected site it searches every document library and all Site Pages.
Can xop.ai access my client's SharePoint tenants, or only our MSP's tenant?
Both models are supported. Most MSPs configure xop.ai in their own Microsoft 365 tenant for shared runbooks and SOPs. For MSPs managing client M365 environments, xop.ai can be added to each client's tenant with its own app registration. Because each tenant uses a separate registration scoped to its own sites, client environments stay isolated.
How does xop.ai control access to SharePoint content?
You stay in control of exactly what it can see. xop.ai connects with an app-level Microsoft Graph registration that lives in your own tenant and reads only the specific sites you scope it to — add or remove sites anytime, or revoke the whole connection in Entra. For tightest least-privilege, use Sites.Selected to grant access to only the sites you name. Note that today it reads the full content of the sites you connect rather than filtering by each end-user's individual SharePoint permissions, so scope it to sites whose content is appropriate for the team using it. Per-user permission enforcement for end-customer chatbots is on the roadmap.
Where does xop.ai store SharePoint content?
xop.ai maintains an embedding index for sub-second semantic retrieval. Full document content is fetched from SharePoint at the time of retrieval, not stored persistently. Details are in our security documentation — available on request.
Can xop.ai search SharePoint alongside IT Glue and Hudu?
Yes. xop.ai federates search across SharePoint, IT Glue, Hudu, and Confluence. Engineers ask a single question and get the best answer regardless of which system holds it. This cross-platform search is our core documentation differentiator.
See xop.ai + SharePoint In Action
Get a live demo with your own Microsoft 365 tenant. Watch natural-language search surface the right SharePoint documents in under two seconds — scoped to the sites you choose.
Schedule a Demo