Discover tools dynamically
Copilot can resolve a plugin's current MCP tools at runtime, or use a pinned tool set in the manifest.
Documentation ↗MCP server / productivity/knowledge / source-linked
Microsoft 365 MCP
This entry is an integration pattern, not a ready-made mail or files server. Microsoft documents remote MCP plugins, dynamic tool discovery, OAuth/Entra authentication and MCP Apps widgets inside declarative agents. The actual data surface depends on the external server and manifest.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Microsoft 365 MCP is a Copilot extensibility framework: it lets a declarative agent consume a remote MCP server through a plugin or agent connector; it is not one Microsoft-hosted all-purpose MCP service.
Implementation source ↗
Microsoft 365 MCP is a Copilot extensibility framework: it lets a declarative agent consume a remote MCP server through a plugin or agent connector; it is not one Microsoft-hosted all-purpose MCP service.
Implementation source ↗
This entry is an integration pattern, not a ready-made mail or files server. Microsoft documents remote MCP plugins, dynamic tool discovery, OAuth/Entra authentication and MCP Apps widgets inside declarative agents. The actual data surface depends on the external server and manifest.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Remote MCP over HTTP; MCP Apps can return interactive UI
- Authentication
- OAuth 2.1 or Microsoft Entra SSO; anonymous only for development
Create or select a remote MCP server, register its OAuth client, build a declarative agent with Microsoft 365 Agents Toolkit, then publish/sideload the agent and authorize the plugin.
Setup reference ↗What it actually exposes.
Concrete capabilities with maintainer sources.
Perform permitted actions
A plugin can query, create, update and delete whatever the connected MCP server exposes, subject to user permissions and confirmations.
Documentation ↗Render interactive results
MCP Apps let tools return widgets such as visualizations, forms and task interfaces in Copilot.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed workflow: expose a governed work system
Suggested evaluation, not an observed test result.
- Define the external tool's read and write operations and required permissions.
- Register its OAuth client and create a declarative agent plugin.
- Sideload the agent, test confirmation prompts and review tenant policy before publishing.
What to inspect: A governed Copilot integration design, not a working server or security certification. Not tested here.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Plugins are supported as actions within declarative agents; the framework is not a general MCP client for every Microsoft 365 Copilot surface.
Boundary reference ↗Production deployment needs authentication, an external remote server and Microsoft 365 Agents Toolkit; anonymous auth is a development option only.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A governed Copilot integration design, not a working server or security certification. Not tested here.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Atlassian Rovo MCP | Editorial choice: you need a vendor-hosted Jira/Confluence connector. | Atlassian's data model and Rovo credit model apply. Documentation ↗ |
| Google Workspace CLI MCP | Editorial choice: local CLI automation is the primary requirement. | It is currently CLI-only, not an active MCP mode. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Does this page represent a Microsoft-hosted Gmail/Drive equivalent?
No. It describes how to plug an external MCP server into declarative agents and Copilot extensibility.
Documentation ↗
Can I launch anonymously?
Microsoft documents anonymous auth for development; production connections should use OAuth 2.1 or Entra SSO.
Documentation ↗
Source trail.
Maintainer documentation used in this record.