Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The federated Microsoft 365 Copilot Connector program allows partners to submit a remote Model Context Protocol (MCP) server to Microsoft for inclusion in the connectors gallery for Microsoft 365 Copilot tenants.
After Microsoft approves your MCP server and adds it to the gallery as a federated connector, tenant admins can review and approve the connector for their organization. After an admin approves it, Microsoft 365 Copilot connects to your remote MCP server through a public HTTPS endpoint and surfaces your content in Copilot experiences, such as the Copilot app and the Researcher agent.
This article explains submission prerequisites, requirements, required artifacts, and what to expect during review and onboarding of a federated connector. For legal terms, see Microsoft Product Terms.
Note
Microsoft enables only tools that perform search and fetch operations. Each tool must include the readOnlyHint annotation to be enabled in the connectors gallery in the Microsoft 365 admin center.
Prerequisites
Before you submit your connector, make sure that you meet the following prerequisites:
- You have an active engagement with a Microsoft business development representative.
- Your organization has signed a legal agreement that permits Microsoft to use your MCP server and its tools within Microsoft 365 Copilot.
Gallery requirements
All submitted federated connectors must meet the following requirements:
- Security and privacy: Meets Microsoft security and privacy standards.
- Tool metadata: Each tool has a clear title and includes the required
readOnlyHintannotation. - Authentication: Authenticated scenarios use OAuth 2.0.
- Documentation quality: Setup, usage, and support guidance are clear and complete.
Microsoft reviews all submissions for quality, usefulness, and safety before listing. Building an MCP server doesn't guarantee that it will be included in the gallery.
Submitter responsibilities
When you submit a federated connector, you agree to:
- Maintain connector functionality and security over time.
- Respond promptly to security issues.
- Provide accurate metadata, assets, and documentation.
- Support Microsoft validation and ring-based rollout activities.
Required metadata and assets
Provide the following artifacts with your submission.
| Field | Requirement |
|---|---|
| MCP server URL | Public HTTPS endpoint for your MCP server. For example: https://mcp.contoso.com/mcp. |
| Connector display name | User-facing connector name. |
| Short description | Public description, 80 characters or fewer. |
| Synonyms | Up to 10 comma-separated keywords users might search for. Avoid generic or competitor names. |
| Logo (color.png) | 192 x 192 pixel full-color PNG. |
| Logo (outline.png) | 32 x 32 pixel white-on-transparent PNG. |
| OAuth credentials | OAuth reference ID for your Microsoft registration. For setup information, see OAuth 2.0. |
| Tool list | Complete list of tools with human-readable names and confirmation that each tool includes the readOnlyHint annotation. |
| Documentation and support | Links to product documentation, privacy policy, and support channel. |
| Test credentials | Test account details and step-by-step setup instructions for reviewers. |
| Sample prompts | At least three prompts with expected responses that demonstrate connector capabilities. |
Review and onboarding process
Microsoft accepts submissions on a rolling basis. Review time varies based on submission volume and completeness of provided artifacts.
After you submit a federated connector:
- Microsoft validates the submitted metadata, assets, and technical requirements.
- Microsoft integrates the connector and coordinates validation through your Microsoft business development representative.
- Microsoft proceeds with release discussions and ring-based rollout planning.
- After Microsoft approves the connector and publishes it in the gallery, each customer organization's admin must approve the partner federated connector before it's enabled for that organization.
Microsoft doesn't provide notifications for every intermediate status change. For status questions, contact your Microsoft representative.
Submit your connector
To submit your connector, complete the Federated Copilot connector submission form.
For any questions related to submitting your remote MCP server, send us an email.