Quick answer
Connect the Dynamics 365 Customer Experience MCP Server for Service through Microsoft Agent 365 Tooling Gateway (ATG), not through the older preview-only D365 Service MCP instructions. Collect the Dataverse environment ID, select the matching ATG ring, grant the required delegated permission with tenant-admin consent, and start with a non-production test user whose Dataverse role exposes only the records needed.
For a discovery-capable client such as Visual Studio Code or GitHub Copilot CLI, the current server URL is:
https://<ring-host>/mcp/environments/<environment-id>/servers/mcp_D365CX_Service
The /mcp/environments/ segment is required. A missing segment returns a 404, and the environment must exist in the selected ring. The production ring host is https://agent365.svc.cloud.microsoft.
Start with the independent product guide if you first need to decide whether the independent MCP server is the right surface.
Prerequisites and responsibility split
Before creating a client connection, confirm these owners and inputs:
| Need | Current requirement |
|---|---|
| Environment | Dataverse environment ID and its correct Agent 365 ring |
| Configuration role | System Administrator or Omnichannel Administrator |
| Runtime role | Customer Service Representative or Customer Service Representative Manager |
| Consent | A tenant or delegated admin able to grant required delegated consent in advance |
| Client | An MCP host that supports OAuth discovery, or a Copilot Studio custom connector |
| Governance | Approved data destination, retention, residency, audit, and incident owner |
ATG authenticates the signed-in identity to Dataverse. It does not replace Dataverse authorization. A successful OAuth connection therefore does not grant every user access to every case, knowledge article, activity, or operation.
Path A: discovery-capable MCP clients
Microsoft’s setup documentation lists discovery-capable hosts including VS Code, GitHub Copilot CLI, Cursor, ChatGPT, and Claude Code. In these clients, add the server URL and let the host discover the protected-resource and authorization metadata. The user then signs in through Microsoft’s OAuth flow.
A minimal VS Code .mcp.json entry is:
{
"servers": {
"d365-customer-service": {
"type": "http",
"url": "https://<ring-host>/mcp/environments/<environment-id>/servers/mcp_D365CX_Service"
}
},
"inputs": []
}
Do not paste a client secret, bearer token, or production record into this file. Microsoft says the server uses OAuth 2.0 protected-resource discovery; the MCP host should take the user through sign-in instead of storing a shared credential in source control.
Path B: Copilot Studio
Copilot Studio currently requires a more explicit connector path. Register a single-tenant confidential application, add the delegated McpServers.D365Service.All permission, grant tenant-admin consent, and use the application in a custom connector pointed at the same environment-specific server URL.
Keep the application secret in the approved secret store or connection configuration. Record its owner, expiry, rotation plan, and allowed environment. Use a separate app registration for production rather than reusing an individual’s development credential.
ATG’s token audience is the gateway, and its scope ends in /.default. Microsoft notes that the gateway does not support dynamic incremental consent, so an administrator must grant the required permission before users connect.
Validate before production
Run these checks with a low-privilege test identity:
- Confirm the ring host and environment ID independently in the admin center.
- Connect and enumerate tools without taking a write action.
- Read one permitted test case and verify a prohibited record stays inaccessible.
- Exercise a reversible update in a sandbox environment and inspect Dataverse audit history.
- Disconnect the client, revoke its session, and confirm the operational owner can repeat the process.
The GA server exposes more than 90 service-oriented tools across case management, customer context, knowledge, communications, recommendations, search, and administration. Do not approve all possible operations merely because discovery returns them. Restrict the user, environment, client, and task to the smallest useful boundary.
Data egress and government environments
An MCP host can send Dynamics 365 context to a service outside Microsoft. Microsoft says data sent to that destination is governed by the destination’s terms, compliance commitments, and data-residency controls. Review what the host retains, which models or subprocessors it uses, and whether administrators can revoke access and inspect activity.
Microsoft also calls out a US government boundary: enabling this connection can allow data to leave the FedRAMP High boundary. The tenant administrator must validate the security and compliance posture before enabling it.
For a fuller host and role matrix, use the supported clients and permissions guide. To compare the MCP route with Microsoft’s packaged user experience, see Service Agent versus Customer Experience MCP.
Frequently asked questions
What URL connects to the Dynamics 365 Customer Experience MCP Server for Service?
Use the Agent 365 Tooling Gateway URL https://<ring-host>/mcp/environments/<environment-id>/servers/mcp_D365CX_Service. The /mcp/environments/ segment is required, the environment must be in the selected ring, and production uses https://agent365.svc.cloud.microsoft as the ring host.
Which roles are required to configure and use the Dynamics 365 Service MCP server?
Microsoft lists System Administrator or Omnichannel Administrator for configuration, and Customer Service Representative or Customer Service Representative Manager for use. Dataverse security still determines which records and operations each signed-in user can access.
Does enabling the server send Dynamics 365 data to another service?
It can. Microsoft warns that an external MCP client or destination can receive Dynamics 365 data and process it under that destination’s terms, compliance, and residency controls. US government tenants must also evaluate the documented FedRAMP High boundary warning before enabling it.
Official sources
- Microsoft Learn: Connect Dynamics 365 CX MCP Server - Service through Agent 365 Tooling Gateway
- Microsoft: Dynamics 365 Customer Service MCP server general availability
Source check: August 3, 2026. Verify the live ring, application ID, delegated scope, supported host, Dynamics roles, and compliance notice before enabling production access.