LeanIX MCP + Microsoft Copilot Studio

Hi,

Ive just managed to connect copilot just now actually.

Happy to connect on this?

Cheers,

Neil

Hi ​@neilcook, That’s great to hear - thanks for sharing!

If possible, could you point me to any configuration notes, or examples you followed to get it working? I’ve already gone through the official LeanIX and Copilot Studio documentation, but I’m still running into issues - so any practical insights or reference setups would be really helpful.

If you’re able to share details here, that would be great so others can benefit too. But feel free to send me a private message if you prefer. Thanks a lot!

Agree with ​@bakari (appreciate the thought).. if you could please share details (as much as you can at least) here, it would certainly benefits others trying to implement the same. ​@neilcook 

Same request here … Share the details would benefit us as well greatly ​@neilcook 

Thank you

Hello,

Our connexion with the MCP server is unstable in Copiliot, we need to come back on a regular basis to Copilot Studio to re-establish the connexion with the MCP server.

Are you facing the same issue ?

Thank you!

Kind regards,

I do have the MCP connection working in Copilot studio and have successfully published an agent so that others can use it. However, there does seem to be a problem with the API key approach. It seems that each user needs to provide this API key before the connection to MCP server is established. This is not practical, I certainly don’t want to share the API key, I don’t even want users of the Agent to have to establish the connection. I am going to continue to investigate to see what work arounds there may be, the responses from the agent are pretty impressive, so I certainly see a lot of value in getting this working.

Hi ​@Graham Howe, Copilot Studio does support running this with a shared credential. The key is making sure the setting is applied in the right place.

Here’s exactly where to check it https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-connectors#use-connectors-with-maker-provided-credentials :

1. Go to your agent in Copilot Studio
2. Open Tools and select your MCP connection
3. Go to the Overview tab
4. Scroll to Details → Additional details
5. Set:
   • Ask the end user before running → No
   • Credentials to use → Maker-provided credentials
6. Save and republish the agent

By default Copilot Studio uses end-user credentials, which is why you’re seeing the API key prompt in the first place. When you switch to maker-provided credentials, the agent should call the MCP server using your stored key, without asking users to authenticate.

I tried both authentication methods, in my case with MCP Inspector. 

1. Technical user: Using Bearer token from technical user in LeanIX in the header. Works, but I prefer to have the user context with OAuth.
2. User based Outh: Just leaving the header empty. Using the right instance in the URL e.g., instead https://mcp.leanix.net/services/mcp-server/v1/mcp, https://de-1.leanix.net/services/mcp-server/v1/mcp. This skips the selection of the correct instance, even when LeanIX remembers your last selection users will not know what to enter.

I have successfully connected Copilot Studio to the MCP server using a technical user token. But I am unable to connect things up using OAuth2. I have tried both tps://mcp.leanix.net/services/mcp-server/v1/mcp!--scriptorendfragment--> (which prompts for our instance name) https://rei.leanix.net/services/mcp-server/v1/mcp. But both seem to be ignoring our Entra ID SSO configuration (with the result being an error saying the Shibboleth.sso configuration, which we no longer use, is disabled). Our SSO configuration is workspace-specific, but the MCP OAuth connection prompt is not allowing us to specify the workspace. Has anyone found a way to make this work (or does this require a bug report)?!--scriptorstartfragment-->