Hi @Richard Cho
This might of your interest : https://jira.atlassian.com/browse/ECO-1693
Seems a current limitation between how M365 Copilot Custom Federated Connectors and Atlassian Rovo MCP handle authentication:
- The Problem: M365 Custom Federated Connectors require standard OAuth 2.0 with a static enterprise App Registration (Client ID/Secret, static token endpoints). Atlassian’s Remote MCP server uses OAuth 2.1 Dynamic Client Registration, which breaks the federated connector setup flow at authentication.
- Why Agents Work: Copilot Studio Agents support Dynamic Discovery auth for MCP endpoints [https://mcp.atlassian.com/v1/mcp] which is why the Agent route works though as you noted, it requires manual mentioning instead of dynamic, passive retrieval across global Copilot prompts.
Workarounds today:
- Middleware Proxy: Deploy a small wrapper (e.g., Azure API Management or Azure Function) to translate static OAuth 2.0 requests from M365 into Atlassian’s dynamic authentication flow.
- Official Gallery Connector: Wait for Microsoft and Atlassian to release a pre-built connector in the Microsoft 365 Connectors Gallery, which bypasses custom app registration.
You can track feature suggestions for native M365 federated connector support directly on above jira and/or submit feedback on the Microsoft 365 Copilot Feedback Portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.