Power Platform Community Forum Thread Details

We are testing a custom MCP integration with Microsoft Copilot Studio.

As the maker, we are able to:

create the connection successfully
complete OAuth authentication
use the MCP tools inside Copilot Studio

However, after publishing the agent, end users are unable to create their own connection properly.

When the published agent prompts users to create or pick a connection, the dialog appears blank and no connection options are shown. As a result, end users cannot authenticate with their own account even though the agent is configured for end-user credentials.

Questions:

Are custom MCP servers officially supported for published Copilot Studio agents using end-user credentials?
Is the blank “Create or pick a connection” dialog a known issue?
Are there additional requirements for enabling end users to create their own OAuth connections for MCP servers?

Would appreciate any guidance on whether this scenario is currently supported or if there are recommended workarounds.

Categories:

Model context protocol

This behavior is expected and is due to a current platform limitation, not a misconfiguration.

Custom MCP Servers in Copilot Studio are still in preview. While OAuth authentication works correctly for makers during design and testing, end-user OAuth connections for Custom MCP Servers are not fully supported yet in published agents.

What happens in this scenario is:

- The maker can successfully create and use the OAuth connection.

- After publishing, Copilot Studio attempts to prompt end users to “Create or pick a connection”.

- Because end-user OAuth connections for Custom MCP Servers are not currently supported, the connection picker dialog appears empty and the user cannot authenticate.

This is not related to Dataverse permissions, environment roles, or missing configuration. Re-publishing the agent or changing security settings does not resolve the issue.

Recommended workarounds at this time:

- Use a maker-managed OAuth connection (application/service credentials) so the agent runs with a single shared connection.

- If per-user OAuth is required, expose the API via a Custom Connector instead of a Custom MCP Server, as Custom Connectors fully support end-user OAuth connections in published agents.

Microsoft has indicated that MCP support is evolving, and broader end-user authentication scenarios are expected in future updates, but today this is a known limitation of Custom MCP Servers.

Hope this helps!
Paolo

✅ Did this solve your issue? → Accept as Solution
👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!

Want more tips on Power Platform & AI? Follow me here:

🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
📸 Instagram: https://www.instagram.com/beyond_the_platforms/
🌐 Website: https://www.beyondtheplatforms.com/