Connect via MCP tool to Dataverse in other environment

(0) Share

Report

Posted on by Arild Aarnes

565 Super User 2026 Season 1

Hi people,

I'm trying to use the MCP tool in a Copilot Studio agent in Environment A to connect to Dataverse in environment B, but are having some problems getting an entry in the Allowed MCP Client list in environment B.

Here is what I have done/tried:

Made sure Allow MCP clients to interact with Dataverse MCP server is checked in environment B
Created an App registration in Entra ID following the instructions in Connecting Copilot Studio to a Dataverse MCP Endpoint Across Environments: A Practical Guide | The Custom Engine
Created a Custom Connector according to the same instructions (also tried with the Copilot Studio built in MCP Tool)
Created an App User for the app registration in environment B
Added security roles to the app user in environment B
Added and tested the custom connector in a Copilot Studio agent in environment A

The test failed, and I understand that it's supposed to do that until i allow it in the Allowed MCP client list in environment B. But here is the problem, an item for the client never shows up in the allowed MCP client list in environment B. It's my understanding that an entry should automatically show up there when my agent tries to access the MCP in environment B? It should show up with the ID of the Entra ID app registration.

Everything seems to work Ok, but the entry never shows up in the allowed list.

I did a test by changing the already existing entry for the "Microsoft Copilot Studio App" to my Entra ID app registration ID and everything is then working fine from the Copilot Studio Agent in environment A. So my main problem seems to be that the entry for my copilot Studio agent/Entra App Id does not appear in the allowed MCP client list automatically.

Anyone have any idea where I'm missing something?

Thanks.

Arild

Categories:

Model context protocol

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Suggested answer

Romain The Low-Code... 2,855 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

hello, i m not sure to understand what you are trying to do.

By default in copilot studio, you add the dataverse MCP tool and then it work on the current env. There no option from copilot studio to connect to a different environnement. At my knowledge, there are no supported tool to make cross env with the default tool.

to achieve what you wana do, you need to create you'r custom dataverse connector (i do that with custom declarative agent to target whatever env i want) but from studio, i don't think it's supported by design even if you create all app registration.

Was this reply helpful? Yes No
Arild Aarnes 565 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Romain The Low-Code Bearded Bear,

According to this article from the Power CAT team it's possible to connect to a dataverse MCP endpoint in i different environment Connecting Copilot Studio to a Dataverse MCP Endpoint Across Environments: A Practical Guide | The Custom Engine

And that's what I'm trying to do, create a Copilot Studio agent in environment A that connects to dataverse MCP in environment B. And it does work if I manually add the ID for the Entra Id app registration on the Allowed MCP client list. But my understanding is that I'm supposed to get an entry in that Allowed MCP Client list automatically on the first connection, and then you have to set the property Is enabled to yes to allow the connection.

Regards,

Arild

Was this reply helpful? Yes No
Romain The Low-Code... 2,855 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

oh ok :) and so by this tuto, it's a custom connector solution :) , yes it's totally supposed to work. i will folow since i m curious why it's not working for you ;) sorry i cannot help on this one :(

Was this reply helpful? Yes No
Verified answer

Arild Aarnes 565 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Ok, I figured this out, the problem was me :-)
I'm not sure where I got the idea that the entry in the Allowed MCP clients list should show up automatically, but that is apparently wrong.

I had some trouble creating an entry in the list manually but finally understood that I need to specify a prefix in the Unique Name column. Looks like it can be anything as long as I specify prefix in the format pre_

The Application Id will be the Application ID for the Entra ID App registration I created earlier.

That's it. So the main problem was me not understanding how to create the entry in the Allowed MCP Clients list properly :-)

Arild

Was this reply helpful? Yes No