D365 CX MCP Server (Preview)

Dynamics 365 CX MCP Server, allowing users to interact with Dynamics 365 Customer Engagement MCP tools through Agent Gateway.

This connector is available in the following products and regions:

Dynamics 365 CX MCP Server

The Dynamics 365 CX MCP Server provides supported Microsoft experiences with access to Dynamics 365 Customer Engagement capabilities through Agent Gateway.

Publisher: Microsoft

Prerequisites

• A Microsoft Entra ID account
• Access to the required Dynamics 365 environment and data
• Any tenant policies required by the experience using this connector

Supported Operations

Dynamics 365 CX MCP Server

Provides the available Dynamics 365 Customer Engagement MCP tools.

Obtaining Credentials

Sign in with your Microsoft Entra ID account and consent when prompted. No API key or manually created secret is required.

Getting Started

Use the connector from a supported Microsoft experience and sign in when prompted.

Use the MCP environment-selection tools to choose the Dynamics 365 environment when prompted. Subsequent tool calls use the MCP service's selected environment for your user and tenant, not the Power Platform environment that hosts the connector connection. The MCP endpoint URL does not change when you switch environments.

Caller Application Context

The connector forwards the authenticated caller's app ID to Agent Gateway in x-ms-clientAppId, before replacing the authorization token. It prefers the shared Power Platform policy's computed app ID, otherwise resolves the appid or azp claim from the server-preserved original caller authorization. It uses the current incoming bearer token only when that saved context is absent; unusable saved context never falls back to a possible backend token. It never trusts a supplied x-ms-clientAppId header. If no usable app ID is available, it removes that header and logs the missing attribution without failing the MCP request. This identifies the caller reaching Power Platform, which may be an intermediary; it cannot distinguish surfaces sharing an app registration, such as Word, Excel, and PowerPoint. Agent Gateway requires separate support to forward this context to MCP. This change does not alter authorization or billing.

The connector also forwards supplied AI request context in x-ms-ai-billing-service-id (initiating billing workload), x-ms-ai-tenant-id (customer tenant), x-ms-ai-user-id (optional attributed user), and x-ms-ai-correlation-id (cross-service join key). Each must contain one UUID; accepted values are normalized without changing their identity. Missing or blank values are omitted, as is an all-zero user UUID. Malformed or repeated values are removed with diagnostics that do not include their values; the tool request continues. Valid fields are forwarded independently, without deriving missing values from OAuth claims or generating IDs.

These are caller-supplied context, not authenticated billing or authorization identities. The attributed user need not be the delegated token subject. Agent Gateway must separately support forwarding these headers to MCP; this connector change does not enable metering or alter billing decisions.

Known Issues and Limitations

• This connector is in Preview, and its capabilities may change before general availability.
• Availability and capabilities depend on tenant configuration and the signed-in user's permissions.
• The connector does not grant access to data or capabilities that the signed-in user is not already authorized to use.
• Environment selection is shared for your user and tenant across supported experiences; it is not isolated per conversation.
• Remembering a selection across service instances depends on the MCP service successfully saving it. If the selected environment is missing or unexpected, verify or reselect it before invoking data tools.

Deployment Instructions

This Microsoft first-party connector is deployed and managed by Microsoft.

Support

Visit Microsoft Support for help.

Creating a connection

The connector supports the following authentication types:

Login with Microsoft Entra ID

Auth ID: certOauth

Applicable: All regions

Provide Microsoft Entra ID credentials using PFX certificate and password

This is shareable connection. If the power app is shared with another user, connection is shared as well. For more information, please see the Connectors overview for canvas apps - Power Apps | Microsoft Docs

Default [DEPRECATED]

Applicable: All regions

This option is only for older connections without an explicit authentication type, and is only provided for backward compatibility.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Actions

Dynamics 365 CX MCP Server