Fix repeated MCP connection prompts in Copilot Studio
Diesen Beitrag auf Deutsch lesen
A Copilot Studio MCP tool may repeatedly request a connection when its credential setting uses end-user credentials; switching to maker-provided credentials resolved the reported issue.
TL;DR
In Copilot Studio, an MCP tool continued showing “Let’s get you connected first” despite an active connection because “Credentials to use” was set to “End user credentials.” Switching the tool to “Maker-provided credentials” stopped the connection prompt and made the test agent work, while API key authentication and additional connections did not resolve it.
Original by Alex Shlega, on It Ain't Boring. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: test the MCP tool’s “Credentials to use” setting when an agent repeatedly sends users to Connection Manager despite an active connection.
- Security/Compliance: review whether maker-provided credentials are appropriate for the connector and usage scenario, because that setting means the agent no longer requires each user to connect; the source does not define the resulting access boundaries.
This post is licensed under CC BY 4.0 by the author.