Forum Discussion

SalmanAliTMV's avatar
SalmanAliTMV
Copper Contributor
Sep 29, 2026

How does ERP MCP determine F&O environment?

How does the Dynamics 365 ERP MCP Server determine the target Finance & Operations environment when multiple environments (SIT, UAT, and Production) have MCP enabled? In Copilot Studio, the MCP connection only shows the authenticated user and does not expose any environment selection or environment identifier. Is the target F&O environment determined by the underlying Power Platform connection, the MCP client registration, a connection reference, or another routing mechanism? How can administrators verify which F&O environment an MCP-enabled agent is actually connected to?

copilot chat
copilot control system
Microsoft Copilot Admin
security and compliance
training and resources
troubleshooting

1 Reply

  • Jason_M's avatar
    Jason_M
    Brass Contributor
    Sep 30, 2026

    The authenticated user shown in Copilot Studio identifies whose credentials the connection uses, not which F&O environment it targets. Having MCP enabled in SIT, UAT, and Production doesn’t make that connection’s destination apparent from the sign-in details.

    The routing needs to be traced through the particular ERP MCP integration you added. An environment-specific server URL can identify the destination directly; a shared service endpoint would need an environment binding elsewhere in its configuration. Without inspecting that configuration, I wouldn’t assume it automatically selects the F&O environment linked to the current Power Platform environment.

    To verify it:

    1. Open the agent’s MCP tool configuration and identify the server/connector, connection, and any configured endpoint or environment parameter. If the UI hides these, inspect the connector definition or solution configuration where available.
    2. Follow the connection reference, if one is used, to the actual connection in the destination Power Platform environment. A connection reference points to a connection; its display name isn’t proof of the target F&O environment.
    3. Check the Power Platform–F&O environment link in the admin configuration. Record it as part of the investigation, but confirm that this MCP integration actually uses that link for routing.
    4. Verify with a read-only call and telemetry. Use an operation against a known, non-sensitive test record that differs between environments. Correlate the call’s time or request ID with available F&O/MCP logs to establish which environment received it. Don’t use a write operation as a connectivity test.

    The client registration primarily establishes application identity and permissions; it isn’t, by itself, evidence of environment selection.