Microsoft's MCP-First Enterprise ERP Play: Transitioning to the Dynamic Dynamics 365 MCP Server and Consumption Billing
Update (Oct 12, 2026) — the retirement has taken effect on schedule: Microsoft's official documentation confirms the static Dynamics 365 ERP MCP server "will be retired on October 1, 2026," a date now passed, with customers transitioned to the dynamic server and its consumption-based billing. No reports of major service disruptions surfaced in this cycle's searches.
The dynamic Dynamics 365 ERP MCP server exposes three tool categories — data CRUD, form navigation, and action invocation — and introduces agent-specific monetization: for agents built outside Copilot Studio, "usage of the Dynamics 365 ERP MCP server incurs a cost of one copilot credit per 10 tool calls to the server (or 0.1 credits per tool call)," separate from the LLM orchestration cost billed by the agent client. Agent identities are exempt from Dynamics user licenses when assigned the System agent security role — a licensing structure that prices agents as first-class economic actors, distinct from human seats.1
The significance for the displacement thesis stands, and is now confirmed in production: the incumbent's integration surface is an MCP endpoint with metered, per-call billing2 — the same consumption economics AI-native startups use, deployed defensively by the incumbent. Any agent (including third-party AI-native products) that wants to operate on Dynamics ERP data does so through Microsoft's metered gateway. Watch whether other enterprise vendors follow with MCP-first, consumption-billed integration surfaces (see Model Context Protocol (MCP) Becomes the Dominant Enterprise GTM and CRM Integration Standard).
-
An instance of Autonomous agents are emerging as the software industry's fastest-growing consumer class. — Dynamics now licenses machine identities per tool call instead of human users, pricing agents as first-class economic actors in the customer base. ↩︎
-
An instance of Standardized context protocols must replace stateless APIs to coordinate agents across enterprise boundaries. — Microsoft's production retirement of a static integration endpoint for a dynamic MCP gateway confirms standardized context protocols have replaced custom and stateless APIs as the enterprise integration surface. ↩︎