All documentation
On this page

Set-up documentation

Connect your mailbox to Microsoft Copilot Studio

Copilot Studio offers three OAuth modes and this server qualifies for the simplest. Generative orchestration has to be on first, and it is off by default.

Time About 5 minutes
Where Tools, Add a tool, New tool, Model Context Protocol
It needs URL only, then sign in

Two things to settle first

Neither is about this server, and both will stop you before the steps do.

  • Prerequisite

    Generative orchestration must be on

    Microsoft's own documentation is explicit: you must turn on generative orchestration to use MCP. In the classic authoring experience it is off by default, so on an existing agent this is a change somebody has to make deliberately.

  • Governance

    Your tenant DLP policies apply to this

    MCP connectivity in Copilot Studio runs on Power Platform connectors, so the data loss prevention policies that govern connectors in your tenant govern this server too. If your administrator has a policy that separates business and non-business connectors, a mailbox server will land in it. Better to know before you build the agent than after.

Add the tool

  1. Turn on generative orchestration

    On the agent that will use the mailbox. Nothing below works without it, and the MCP option is simply absent rather than disabled.

  2. Tools, Add a tool, New tool, Model Context Protocol

    Four clicks from the agent's Tools page.

  3. Fill in the server details

    Server URL The same for every account
    https://mcp.mailbox-mcp.com/db/mcp/YOUR-MAILBOX-KEY

    The server name and description are yours. Write the description for the model rather than for a person: it is one of the things the orchestrator reads when deciding whether this tool is relevant to a question.

  4. Choose OAuth 2.0, then Dynamic discovery

    Then Create and Next. There is nothing else to fill in, and the next section explains why that is the right choice rather than the lazy one.

Pick Dynamic discovery

Copilot Studio offers three OAuth sub-types and they are not interchangeable. Microsoft describes the first as "the simplest method", for a server that supports dynamic client registration with discovery. This server does exactly that, so it is the one to pick.

Option What it wants
Dynamic discovery Nothing. The server publishes where its endpoints are and registers the client itself. Choose this one.
Dynamic An authorization URL and a token URL template, typed by hand.
Manual A client id, a client secret, an authorization URL, a token URL template, a refresh URL and scopes.

The second and third exist for servers that cannot do the first. Choosing one of them here means typing values by hand that the server would otherwise have handed over correctly, and every one of them is a chance to make a typo that produces an authentication failure with no useful message.

What Copilot Studio does not take

Two things worth knowing, both from Microsoft's own pages.

Tools and resources are supported. Prompts are not. That does not affect this server, which offers tools, but it is worth knowing if you are comparing MCP servers for a Copilot Studio agent: a server whose value is in its prompts will lose most of it here.

Streamable HTTP only. Copilot Studio stopped supporting SSE for MCP after August 2025, on the grounds that the transport is deprecated. This server speaks Streamable HTTP, so that is a fact about other servers rather than about this one.

Check that it worked

Test the agent in the authoring canvas before publishing it anywhere.

Try this first

What is in the shared inbox from this week that nobody has answered?

If the orchestrator does not reach for the tool, the server description is usually why: make it say what the tool is for, in the words somebody would use to ask. Nothing is marked read by asking.

Pricing is per mailbox per year, whichever client reaches it. The free tier is 5 calls a day, which is enough to test an agent but not to run one.

Where to go next

Security is the page your administrator will want, and the tool reference is the one to read before an agent runs unattended: it names every tool and marks the read-only ones.

What we could not confirm
  • Which licensing tier MCP support needs, and whether it carries a preview label. Neither page read states either.

Read 30 August 2026 Every value on this page came off Microsoft Learn: extend an agent with MCP on that day. If it has changed since, tell us and we will read it again.