Does Dataverse MCP Server in Copilot Studio work across environments (Dev agent → Prod Dataverse)?

(2) Share

Report

Posted on by akash.talole

Hi Community,

I'm working on setting up a Copilot Studio agent using the Dataverse MCP Server and ran into a question around cross-environment connectivity.

Scenario:
My Copilot Studio agent is built in a Dev environment, but I want it to connect to a Production Dataverse environment (different org URL). I'm using a service account / Application User for authentication.

Questions:

Does the built-in "Dataverse MCP Server" shortcut (via Tools > Add Tool > Model Context Protocol) only work with the Dataverse in the same environment as the Copilot Studio agent? Or can it be pointed at a different environment's Dataverse?

If cross-environment is not supported natively, is the recommended workaround to manually add the prod Dataverse MCP endpoint (https://<prod-org>.crm.dynamics.com/api/mcp) as a custom MCP server tool with OAuth authentication?

For ALM / solution deployment -- when moving a Copilot Studio agent from Dev to Prod via solutions, do connection references for the Dataverse MCP tool automatically remap to the target environment's Dataverse, or does this need to be done manually post-import?

Does MCP need to be separately enabled in each environment (Dev and Prod) via Power Platform Admin Center > Features > Dataverse Model Context Protocol?

What I've tried so far:

Any guidance, best practices, or real-world experience with this cross-environment setup would be hugely appreciated!

Thanks in advance

Enabled Dataverse MCP in the dev environment via PPAC

Added the Dataverse MCP Server as a tool in my Copilot Studio agent

Configured an Application User with the required security role in the target environment

Categories:

Model context protocol

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Sunil Kumar Pashikanti 2,095 Moderator on at

Like (3)

Report
Copy link

Link copied!
Hi @akash.talole,

Q1. Does the built‑in “Dataverse MCP Server” in Copilot Studio only work with the same‑environment Dataverse?
Yes (current behavior). When you add the built‑in Dataverse MCP Server tool in an agent, it uses a Dataverse connection scoped to the selected environment. It’s not designed to target another environment’s org URL from within that same Dev agent.

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-mcp-copilot-studio

Q2. If cross‑environment isn’t supported, can I add the Prod Dataverse MCP endpoint as a custom MCP server tool with OAuth?
Viable workaround. MCP supports adding custom MCP servers as tools. The official labs show adding external MCP servers to Copilot Studio (non‑Dataverse examples), and community guides show creating custom MCP enpoints/tools. You can register a custom MCP tool that authenticates against Prod Dataverse (ensure the Prod environment has MCP enabled/allowed).
https://microsoft.github.io/pp-mcp/labs/mcs-mcp/

https://github.com/sstalsberg/BYOA-CopilotStudio/blob/main/Lab-4-Work-With-MCP-Server.md

https://www.youtube.com/watch?v=0c_iunpal0I

3. During ALM (solution import Dev→Prod), do connection references for the Dataverse MCP tool remap automatically?
Yes, with the usual connection‑reference step. Because MCP tools use connector infrastructure, the connection reference will need to be bound to a Dataverse connection in the target environment during import (or post‑import). This is the same patern as other connectors once bound, the MCP tool points at the Prod Dataverse.

https://microsoft.github.io/pp-mcp/labs/mcs-mcp/

Q4. Does MCP need to be enabled in each environment (Dev and Prod)?
Yes, you must enable/configure the Dataverse MCP server and allow clients per environment in PPAC before Copilot Studio (or other MCP clients) can use it.

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-mcp

The recommended and governed approach is:

Dev agent → Dev Dataverse

Prod agent → Prod Dataverse (via solution + connection reference binding)

Calling Prod from a Dev agent is technically possible (via custom MCP server tool), but it is not best practice because it breaks environment isolation and governance controls.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No
Suggested answer

Valantis 5,267 on at

Like (1)

Report
Copy link

Link copied!
Hi @akash.talole,

Yes, cross-environment is supported. Add the production Dataverse MCP endpoint (https://<org>.crm.dynamics.com/api/mcp) as a second MCP server entry in your Dev agent and authenticate with your service principal.

Steps:

In PPAC (Prod): confirm Dataverse MCP is enabled and "Microsoft Copilot Studio" is listed as an allowed client

In Copilot Studio (Dev agent): Tools > Add tool > Model Context Protocol > connect to existing Dataverse MCP server > enter the Prod org URL

Use an Application User with least-privilege Dataverse roles in Prod

After importing your solution into Prod, manually rebind the Dataverse connection reference(s) to a valid connection in that environment before publishing

To verify: run "list tables" or "describe table account" in the Test pane and confirm results reflect Prod data.

Sources

Dataverse MCP with multiple environments (FAQ)

Connect Copilot Studio to Dataverse MCP

Manage Dataverse MCP per environment

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

Was this reply helpful? Yes No