# Microsoft Dynamics 365 Sales ID: 06-microsoft-dynamics-365-sales Page: https://gtmmcps.com/tools/06-microsoft-dynamics-365-sales JSON: https://gtmmcps.com/data/tools/06-microsoft-dynamics-365-sales.json Documentation references: https://gtmmcps.com/docs/06-microsoft-dynamics-365-sales/ Category: RevOps Infra MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-09-07 Endpoint check: not-probed; date: Not recorded Microsoft's enterprise CRM for sales, built on Dataverse and the Power Platform, covering leads, opportunities, accounts and forecasting, with a first-party MCP server that lets Copilot Studio agents and other MCP clients qualify leads, research opportunities and read and write Dataverse records. ## MCP links - https://agent365.svc.cloud.microsoft/mcp/environments/ - https://learn.microsoft.com/en-us/dynamics365/sales/connect-agents-to-model-context-protocol ## Sources - https://learn.microsoft.com/en-us/dynamics365/sales/connect-agents-to-model-context-protocol - https://www.microsoft.com/en-us/dynamics-365/products/sales/pricing ## Research notes Verified 2026-09-07 from Microsoft Learn. The endpoints are tenant-specific templates, not a shared host, so there is nothing to probe without an environment ID and this entry carries no liveness probe result; that is a property of the design, not a gap in the research. The single most useful line for this directory's readers is in Microsoft's own prerequisites: "Claude Desktop isn't supported at this time." A Microsoft-shaped MCP server that the most widely used MCP client cannot reach is the sharpest available illustration of MCP support being a spectrum rather than a yes or no. The docs give a working mcp.json example pairing both servers, and note that CRUD on Dataverse records requires connecting the Dataverse MCP server as well as the Sales one, so an agent needs two connections to do what a rep does in one screen. Copilot Credit consumption is per tool and documented in a separate Microsoft rate table, so cost scales with agent chattiness rather than with seats. 2026-09-07: the Agent 365 endpoint is per-tenant and templated (https://agent365.svc.cloud.microsoft/mcp/environments//servers/msdyn_SalesMCPServer), so no capability harvest can ever enumerate its tools without a customer EnvironmentID. The route itself is confirmed real (HTTP 400 with an MCP-shaped error to a probe carrying a placeholder environment id). DO NOT RE-INVESTIGATE: this entry is permanently unharvestable from outside a tenant. ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. ## CLI evidence Status: none-found Read current vendor documentation before configuring or running commands.