
Surface the right SOP, runbook, or policy during live calls — across every SharePoint site your team supports. Permissions stay intact through Microsoft Graph.
Built by an MSP operator who ran Microsoft 365 for hundreds of client environments across 28 years.
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.
xop.ai respects SharePoint permissions using Microsoft Graph's delegated access model. Engineers only see content their Entra ID account is authorized to access — no AI-powered permission escalation, no data leakage across clients.
Many MSPs maintain per-client SharePoint sites for documentation or host shared content in their own tenant. xop.ai handles both patterns — engineers search across their allowed content; clients using the branded chatbot only see their own content.
What actually changes when AI-powered search sits on top of SharePoint.
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.
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 end-user's authorized SharePoint content only, finds the HR policy, and returns the exact answer — scoped to what the employee is allowed to see.
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 document surfaces with the permission context they have. Ramp time cut by half, senior engineer no longer blocked.
xop.ai uses the Microsoft Graph API with delegated permissions. Admins install the Microsoft 365 app in the tenant and grant permissions for Sites.Read.All scoped to the integration's service principal. Individual engineer and end-user queries are then scoped to that user's access at retrieval time.
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 for client-scoped end-user chatbot retrieval. Information barriers between tenants are fully enforced.
Yes. Every retrieval is done with the requesting user's delegated Microsoft Graph token. If an engineer cannot access a SharePoint site, xop.ai cannot return documents from that site when they query. Sensitivity labels and information barriers are respected.
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.
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.
Get a live demo with your own Microsoft 365 tenant. Watch natural-language search surface the right SharePoint documents in under two seconds — with permissions fully enforced.
Schedule a Demo