Skip to main content

Overview

Once Microsoft Outlook (MCP) is connected, the Dema Agent can read your mail and send mail on your behalf without you leaving the conversation. 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 only that person’s mailbox.
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.
Don’t have Microsoft 365 Copilot licences or Agent 365 set up? The Microsoft Outlook integration connects any Microsoft 365 work mailbox through Microsoft Graph, with no tenant setup or MCP URL.
This integration covers mail only. Outlook Calendar runs on a separate Microsoft MCP server.

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 Outlook (MCP)

1

Build your MCP URL

Outlook mail is served by mcp_MailTools. 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 Outlook (MCP), 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 Outlook can answer, for example: “List the five most recent unread emails in my inbox.” If it comes back with real subject lines, the connection works.
Authorize with a dedicated agent mailbox instead of your personal inbox, and forward only what the agent needs. See Best practices in the integrations overview.

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.
The agent searches only the mailbox of the account that authorized the connection. It cannot read someone else’s mailbox, or a shared mailbox that account has no access to. Reconnect with an account that can open it.
This integration is mail only. Outlook Calendar runs on a separate Microsoft MCP server, which Dema does not support yet.
An Entra admin has to register or consent the Work IQ Mail MCP server (mcp_MailTools) 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.