Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Custom (org-created) federated MCP connector appears in Copilot Chat Sources but not in Copilot in PowerPoint
We built a custom federated connector (MCP) in the Microsoft 365 admin center under Copilot > Connectors > Created by your org, using OAuth 2.0 authentication via an OAuth client registration in the Teams Developer Portal (PKCE enabled, client_secret_post). The connector is in the green Ready state, and it works in Microsoft 365 Copilot Chat: it appears under ⋯ > Settings > Sources, I was able to Connect and authenticate successfully against our identity provider, and the source is active for my user. However, the same connector does not appear in the Sources picker for Copilot in PowerPoint, signed in as the same user. We are asking because your documentation appears inconsistent on this point: the Federated connectors overview lists "Copilot in Word, Excel, PowerPoint, and Outlook" under Supported Copilot experiences, but the "How to connect and use federated Copilot connectors" section on the same page states that users discover data sources "in the Sources menu in the Researcher agent, in deep research mode in Microsoft 365 Copilot chat, and in Copilot Chat where available", which does not mention the Office apps.
Can you confirm whether custom, org-created federated connectors are surfaced in the Sources picker for Copilot in PowerPoint today? If they are, what configuration are we missing? If support is limited to gallery-published connectors or is still rolling out, what is the expected availability timeline for org-created connectors in the Office app surfaces?