.xlsx workbooks and Word .docx documents natively: cell values and document text are parsed in-process, with no download, OCR or external extraction service. It can be consumed two ways: as a remote MCP server that Agent Creator agents call as tools, or as a Builder app whose instructions you call directly from DSUL. The MCP surface groups every operation into nine entity tools (sites, drives, items, search, permissions, lists, directory, workbook, documents), each driven by an action argument, and runs in the tenant app-instance context (it resolves the installing workspace’s own credentials). Authentication is per-user and supports several modes:
- Per-user OAuth2 (central client) (
oauthCentral, recommended): one Microsoft Entra OAuth Application is registered once by the platform maintainer; every end user signs in with their own Microsoft account. Nothing to register per tenant: each workspace just installs the app and clicks Connect. - Per-user OAuth2 (tenant client) (
oauth): paste your own Entra application (client) ID/secret in the connector config app. Each user signs in with their own account against your client (PKCE authorization-code flow). - Application (client credentials) (
clientCredentials): an Entra app with application Graph permissions and admin consent, acting without an interactive sign-in. Best for back-office / service automations and content indexing. - Direct access token (
accessToken): a caller-managed Microsoft Graph access token, used as-is with no exchange.
Sites & files
.xlsx workbooks and Word .docx documents natively (cell values, full text)Lists, search & permissions
Flexible per-user auth
Who is this for?
This connector is used by three different roles. Jump to the section that matches yours; each one is self-contained.Agent builder
Platform admin
Workspace builder
Prerequisites (Microsoft side)
- A Microsoft 365 / SharePoint Online tenant, and an Azure / Microsoft Entra ID tenant where you can register an application (or a maintainer who already did).
- An app registration in Microsoft Entra ID (Azure portal → App registrations), with a client secret created under Certificates & secrets.
- Microsoft Graph delegated permissions granted on the app (for the per-user OAuth modes), covering the resources you intend to use:
- Sites & files:
Sites.Read.All(orSites.ReadWrite.Allfor create/update/move),Files.Read.All(orFiles.ReadWrite.All) - Directory (access-aware RAG):
User.Read,GroupMember.Read.All(optional) - Sign-in / identity:
openid,profile,offline_access
- Sites & files:
- For the application (client-credentials) mode instead, grant the equivalent application permissions (e.g.
Sites.Read.All,Files.Read.All) and have a Global Administrator grant admin consent.
Platform admin (Governance): one-time platform setup
Platform admin (Governance): one-time platform setup
1. Configure the connector
Register the OAuth Application in Microsoft Entra ID
https://api.studio.prisme.ai/v2/workspaces/7oQvI6Q/webhooks/oauthCallback on production).Add the Microsoft Graph delegated permissions listed in Prerequisites, create a client secret under Certificates & secrets, and note the Application (client) ID, the secret value, and the Directory (tenant) ID (or use common / organizations for multi-tenant).Enter the credentials through the configuration app
sharepoint-next workspace and launch its Configuration app: <studio>/apps/sharepoint-next (e.g. https://studio.prisme.ai/apps/sharepoint-next), also linked as Configuration app on the installed instance. Switch to the maintainer view and follow the in-app instructions to paste the Client ID, Client Secret, Tenant and (optionally) scopes; the app stores them in the core workspace’s secrets for you. Do not edit Studio’s raw Secrets by hand. These credentials stay in the sharepoint-next workspace and are never exposed to tenants or end users; token exchange is proxied through the core centralTokenExchange webhook so the client secret never leaves the core workspace.Tell workspaces to use the central client
oauthCentral in the connector configuration app (no client id/secret to enter on their side). Their users then just click Connect.2. Declare the capability in AI Governance
Generic connectors (broad tool surfaces meant to be shared across many agents, like SharePoint) are best exposed as a named capability in AI Governance. Agent builders then enable that capability on their agents instead of pasting a raw MCP endpoint.Open AI Governance > Capabilities
Point it at the MCP endpoint
agent_id in the scope is what lets the connector identify and authorize the calling agent.Make it available to agent builders
Smoke-test
oauthCentral, trigger any tool. The user is prompted to connect once (Microsoft sign-in); subsequent calls reuse the stored token transparently and refresh it automatically.- Agent builder (Agent Creator)
- Workspace builder (DSUL)
Agent builder
Goal: let an agent you build in Agent Creator browse SharePoint sites, read and manage files, query lists, and check permissions through MCP tools.agent_id that Agent Creator injects through the capability Scope, and that agent must appear in the connector’s authorized-agents allowlist (managed in the configuration app). The Microsoft Graph access token itself is resolved server-side from the configured auth mode.There are two ways to wire it up. Pick based on how much isolation you need.Option A: Enable the shared capability from the catalog
The fastest path: a Platform admin has already published a SharePoint capability (see the Platform admin setup accordion above, §2), so you just pick it from the catalog. A workspace owner can publish it in one click with the config app’s Add to catalog button.Open your agent in Agent Creator
Add the SharePoint capability
context_id,agent_id,user_id) are already wired by the admin: nothing to paste, and the shared instance accepts every agent, so there is no allowlist step on your side.Connect a Microsoft account (OAuth modes)
connect_url. Application (clientCredentials) and accessToken modes need no per-user sign-in.Option B: Run it from your own workspace (recommended)
For production agents, install the connector in your own workspace and point the agent at that workspace’s MCP endpoint.Install and configure the connector in your workspace
Allowlist your agent
Add the MCP capability to your agent
agent_id is what lets the connector identify and authorize your agent; without it, every call is rejected with an explicit “agent could not be identified” message. This Scope is separate from the Microsoft Graph OAuth scopes.Connect a Microsoft account (OAuth modes)
Brief the agent in its system prompt
Whichever option you pick, wiring the capability is not enough: the agent must know the MCP exists and when to use it. Copy-pasteable starter:agent_id.Sites.Read.All, Files.Read.All); writes are only possible if you widen the Scopes field in the configuration app to Sites.ReadWrite.All / Files.ReadWrite.All. To keep the connector read-only, simply leave the default read scopes:403 Forbidden. The scope is set at the workspace level (a workspace editor can widen it); for a hard guarantee, use an Entra app limited to read permissions.Available Tools
Each tool takes anaction argument selecting the concrete operation, plus the per-action parameters.Output Formats
Every tool accepts anoutputFormat argument that controls the MCP response shape:verbose(default): a human-readable text view, optimized for LLM consumption.structured: concise machine-readable JSON instructuredContent.both: the structured payload, with its JSON also rendered as text.
Tool Details
sites
drives
items
items: reading a file’s content
get and listChildren return each file’s @microsoft.graph.downloadUrl, a ~1-hour pre-signed link. Fetch that URL out-of-band to read the bytes; the MCP response never embeds file content inline.lists
permissions
workbook
Read & write the cells of an Excel.xlsx file natively via the Microsoft Graph Excel API: no download, no OCR.addWorksheet, createTable and executeFunction evaluate / mutate the workbook server-side. executeFunction returns { value }, the evaluated result of the Excel function.documents
Read the content of a Word.docx file natively: the file is downloaded and its OOXML parsed in-process (no external extraction service, no OCR).Error Handling
Common Issues
“This agent is not authorized to use this connector”: The calling agent is not in the allowlist. Open the configuration app → Authorized agents → tick this agent (or enable Allow all agents) and Save. “The calling agent could not be identified”: The MCP capability Scope does not declareagent_id, so Agent Creator never injects the agent identity. Set the Scope to context_id,agent_id,user_id on the capability, then allow the agent in the config app.
“Microsoft Graph is not connected for this user”: No per-user OAuth token. Open the configuration app (OAuth mode) and click Connect, or use the agent’s connect flow.
“Microsoft Graph token refresh failed … must reconnect”: The stored refresh token was revoked or expired (Microsoft Entra invalidated it, or it aged past its limit). The connection is dropped automatically; the user must reconnect from the config app.
“Microsoft Graph not authenticated” / “OAuth is not configured”: Neither a tenant OAuth client nor the central platform client is available. Set the client ID/secret/tenant in the config app, or ask the platform maintainer to provision the central Entra OAuth client.
client_credentials exchange failed: In application mode, check the Application (client) ID / secret, the tenant id, and that a Global Administrator granted admin consent for the application Graph permissions.
“Site not found”: The site id format is hostname,siteCollectionId,siteId. Use sites search (or Graph Explorer) to find the correct id.
Microsoft Entra redirect URI rejected: Entra rejects a colon in the redirect URI path. Register the redirect URI with the workspace’s raw id (/workspaces/<workspace-id>/webhooks/oauthCallback), not the slug: form; copy the exact value from the config app.