Skip to main content

Overview

Once Microsoft SharePoint is connected, the Dema Agent can read the documents and lists your team keeps in SharePoint, and file its own output back into them. The agent acts only when you ask it to, and Dema asks you to confirm sensitive changes first. It signs in as whoever authorized the connection, so it sees the same sites and files that person sees.
The Microsoft Agent 365 integrations are in preview, and so are the Work IQ MCP servers behind them. Tools can change without notice. Your workspace might need preview integrations enabled before these show up.
File operations work on files up to 5 MB.

What you can ask for


Before you connect

Every Agent 365 integration needs the same prerequisites, plus a tenant setup an admin does once per Microsoft 365 tenant. Start there, then come back:

Microsoft Agent 365 integrations

Prerequisites, one-time tenant setup, and shared troubleshooting

Connect Microsoft SharePoint

1

Build your MCP URL

SharePoint is served by mcp_SharePointRemoteServer. Replace {tenant_id} with your Entra tenant ID:
MCP URL
Replace the whole {tenant_id} placeholder, braces included. Dema rejects a URL that still has braces in it. A tenant ID is a GUID, like 8f7a1b2c-3d4e-4f56-a7b8-9c0d1e2f3a4b.
2

Connect in Dema

In Dema, go to Agents → Settings → Integrations, find Microsoft SharePoint, and click Connect. Paste the MCP URL you built, then click Add.
3

Sign in and approve

Sign in with a Microsoft work or school account that belongs to the same tenant as the URL, and approve the permission Dema asks for.
You are returned to Dema with the integration marked as Active.
4

Check it works

Ask the agent something only SharePoint can answer, for example: “List the files in the Marketing site’s Documents library.” If it comes back with real file names, the connection works.

Scopes Dema requests

Dema requests these against your tenant’s own MCP server, so the grant covers that server and not your Microsoft 365 account as a whole.

Troubleshooting

Invalid MCP URLs, AADSTS codes, admin approval, and 403 responses work the same way for every Agent 365 integration. Microsoft Agent 365 integrations → Troubleshooting covers them.
File operations are capped at 5 MB. The agent cannot read or upload anything larger. Share a link to the file instead, or work from a smaller extract.
The agent sees only what the authorizing account can open. Grant that account access to the site or library, or reconnect with one that already has it. Name searches need the exact site or library name, so try the site URL if the name does not match.
An Entra admin has to register or consent the Work IQ SharePoint MCP server (mcp_SharePointRemoteServer) in your tenant before anyone can grant the permission.
Still stuck? Contact support with the error message, including the Entra AADSTS code if you have one.