Power Platform Community Forum Thread Details

I am testing the Microsoft built-in Dynamics 365 ERP MCP / Fin & Ops Apps (Dynamics 365) tool in Copilot Studio.

Scenario

Copilot Studio agent is in Tenant A

Dynamics 365 Finance & Operations is in Tenant B

Tenant A Power Platform tenant isolation allows outbound connections to Tenant B

Tenant B allows inbound connections from Tenant A

A Fin & Ops Apps OAuth connection created from Tenant A successfully authenticates a native Tenant B F&O user

Copilot Studio client ID 7ab7862c-4c57-491e-8a45-d52a7e023983 is enabled in Tenant B F&O Allowed MCP Clients

Tenant B F&O is version 10.0.48

Dynamics 365 ERP MCP server feature is enabled

Problem

The cross-tenant OAuth connection is successfully created and shows Connected, but when that connection is selected for the Dynamics 365 ERP MCP tool in the Tenant A Copilot Studio agent, Copilot Studio displays:

“Couldn't load MCP tools.”

We performed the following control tests:

Tenant A Copilot Studio → Tenant A F&O: MCP tools load successfully.

VS Code → Tenant B F&O /mcp: authentication succeeds and 22 MCP tools are discovered.

Tenant B Copilot Studio → Tenant B F&O: the Dynamics 365 ERP MCP tools load successfully.

Tenant A Copilot Studio → Tenant B F&O: OAuth succeeds, but “Couldn't load MCP tools.”

Therefore, the F&O MCP server, F&O version, user authentication, Allowed MCP Client configuration and MCP tool catalog have been independently validated.

Question:

Does the Microsoft built-in Dynamics 365 ERP MCP / Fin & Ops Apps (Dynamics 365) tool in Copilot Studio support the following topology?

Copilot Studio Tenant A → OAuth connection using native Tenant B user → Dynamics 365 F&O ERP MCP Tenant B

If cross-tenant ERP MCP tool discovery is supported, what additional configuration is required? If it is not supported, is this a documented limitation?

Categories:

Copilot Studio pre-built agents/templates

Model context protocol

Bot extensibility