Microsoft's MCP-First Enterprise ERP Play: Transitioning to the Dynamic Dynamics 365 MCP Server and Consumption Billing

Microsoft's MCP-First Enterprise ERP Play: Transitioning to the Dynamic Dynamics 365 MCP Server and Consumption Billing

As part of its enterprise agentic roadmap, Microsoft is officially retiring its legacy, first-generation static Dynamics 365 ERP MCP server on October 1, 2026. Customers are being transitioned to the next-generation dynamic Dynamics 365 ERP MCP server, which represents a major structural shift in how enterprise AI agents securely interact with core systems of record.

1. From Static to Dynamic: The Three-Tier Tool Architecture

The retired static server relied on a limited, pre-configured set of 13 tools built on the Dataverse connector framework. In contrast, the new dynamic server exposes hundreds of thousands of ERP functions in real-time, automatically adapting its context based on the agent's security permissions and environment extensions.

The dynamic server exposes three categories of tools to AI agents:

1. Data Tools (data_create_entities, data_find_entities_sql, etc.): Standard OData-based Create, Read, Update, and Delete (CRUD) operations on application data entities.
2. Form Tools (form_click_control, form_set_control_values, etc.): A server-side alternative to Computer Use Agents (CUA). Instead of scraping a user interface, these tools allow the agent to open forms, set field values, and click buttons by interacting directly with server-side APIs that return the application's view model as structured context.
3. Action Tools (api_find_actions, api_invoke_action): Allow developers to write custom business logic in finance and operations code (implementing the ICustomAPI interface) and expose it directly as an executable tool for agents.

2. The MCP Consumption and Licensing Model

To support this API-first architecture, Microsoft has introduced a dedicated consumption billing and licensing framework for enterprise agents:

• Tool Execution Billing (Non-Copilot Studio): For agents built on non-Microsoft or custom clients (such as Microsoft Foundry), every tool call to the ERP MCP server is billed at 0.1 Copilot Credits (or 1 credit per 10 tool calls). This is an incremental execution charge by Microsoft, separate from the client's LLM token consumption.
• Copilot Studio Bundling: For agents orchestrated within Microsoft Copilot Studio, the variable LLM token cost and the MCP tool execution cost are bundled together into a fixed rate per tool call, billed as an Agent Action.
• Licensing Exemptions:
  • Users with premium licenses (Dynamics 365 Finance Premium or Supply Chain Management Premium) are exempt from the 0.1 credit execution charge in custom clients.
  • Agent identities themselves do not require a standard Dynamics 365 user license, provided they are assigned to the default System agent security role in finance and operations apps.

This transition marks a critical milestone in enterprise GTM strategy: instead of building point-to-point custom integrations or relying on fragile UI-scraping bots, enterprise software vendors are standardizing on the Model Context Protocol (MCP) to turn legacy ERPs into highly secure, queryable, and action-capable environments for AI agents.