First, identify the Copilot surface
“Copilot” covers several products. This guide concerns business agents built with Microsoft 365 Copilot extensibility and Copilot Studio. GitHub Copilot in VS Code has a separate product guide. Do not assume an MCP feature in one automatically appears in the others.
| Microsoft term | Meaning |
|---|---|
| MCP server-based plugin | A plugin for a Microsoft 365 declarative agent whose tools are supplied by a remote MCP server. |
| MCP connector | The Copilot Studio connection definition used to authenticate and reach an MCP server. |
| Tool | In Copilot Studio, the connected MCP server appears on the agent’s Tools tab and exposes its individual tools and resources. |
| Agent | The user-facing specialized Copilot experience that decides when to invoke the plugin or connected server. |
Two common implementation paths
Microsoft 365 Copilot
Package the remote server as a plugin
Use the Microsoft 365 Agents Toolkit and an agent/plugin manifest. The agent invokes tools discovered from the MCP server.
Copilot Studio
Add an MCP connection to an agent
Create or choose an MCP connector, configure authentication, then add the server to the agent as a tool and inspect its available components.
Dynamic tool discovery is a first-class feature
Microsoft 365 Copilot resolves tools from an MCP server at runtime by default. A developer can instead pin a fixed set in the plugin manifest. Runtime discovery means a compatible server can add or change tools without requiring the agent package to capture every definition again. This is progressive in deployment and catalog freshness; teams should still test how many tools enter the model’s working context on each target surface.
Authentication and governance
- Microsoft 365 agent plugins support configured authentication so Copilot can send credentials on behalf of the signed-in user.
- Copilot Studio supports several OAuth configuration paths, including dynamic discovery, dynamic registration, and manual settings.
- Environment policy, connector policy, agent publishing, user licensing, data-loss prevention rules, and source-system permission remain separate controls.
- A remote MCP server should expose only the tools required by the agent and enforce user/tenant authorization on every call.
- Interactive MCP app support and troubleshooting are documented for Microsoft 365 Copilot, but presentation behavior should be tested in the exact client where users will work.
Good fit
This path is strongest when the workflow belongs inside Microsoft 365, needs enterprise identity and governance, or will be built and managed through Copilot Studio. Expect more packaging and administration than adding a personal desktop MCP server; that is the tradeoff for organization-level deployment.