Skip to Content

MC1420830 Finance and operations apps: End of support for static Dynamics 365 ERP Model Context Protocol (MCP) server (Preview)

By: Author Alex Lim

Posted on

Categories Update

Home » Update » MC1420830 Finance and operations apps: End of support for static Dynamics 365 ERP Model Context Protocol (MCP) server (Preview)

Summary

  • The static Dynamics 365 ERP Model Context Protocol (MCP) server (Preview) will be retired and replaced by the new Dynamics 365 ERP MCP server.
  • This change affects Dynamics 365 finance and operations app integrations that use MCP-based agents, Copilot experiences, or other connected workflows.
  • The new dynamic MCP server is available in Dynamics 365 finance and operations version 10.0.47 and 10.0.46 PQU-2.
  • Admins using the static MCP server should migrate agents to the new dynamic MCP server, update security restrictions, and validate prompts and behavior.
  • If you are not using MCP-based integrations, no immediate action is required, but Microsoft recommends reviewing your environment for potential impact.

Primary Service: D365 Apps
Admin Impact: High
User Impact: Low
Release Start: 01 Oct 2026
Release End: 01 Oct 2026
Services: D365 Apps, Dynamics
Category: Stay informed
Tags: Admin Action

History

7/8/2026 Item Added to Message Center

Microsoft Message

On October 1, 2026, the static Dynamics 365 ERP Model Context Protocol (MCP) server (Preview) will be retired.

The static MCP server is being replaced by the new Dynamics 365 ERP MCP server (“new dynamic MCP server”), which provides a more flexible, extensible, and maintainable integration model for Copilot and agent experiences in Dynamics 365 finance and operations apps. The new dynamic MCP server is generally available in Dynamics 365 finance and operations version 10.0.47 and 10.0.46 PQU-2.

How does this affect me?

The new dynamic MCP server introduces a modern MCP‑based architecture designed to support:

  • A configurable and extensible MCP server model rather than a fixed, static definition.
  • Improved alignment with agentic and Copilot scenarios across Dynamics 365 finance and operations apps.
  • A clearer separation between MCP server capabilities and underlying platform connectors.
  • Ongoing evolution without requiring a static connector‑based implementation. This change enables more consistent behavior, better maintainability, and future expansion of ERP‑specific MCP capabilities.

What action do I need to take?

To migrate any existing static MCP server agents to the new dynamic MCP server, take these steps:

  1. Remove the static MCP server from your agent tools and replace it with the new dynamic MCP server.
  2. Ensure the agent has the correct security restrictions. The new dynamic MCP server provides access to more functionality, restricted by the permissions granted to the user through finance and operations apps roles, duties, and privileges.
    • See Use Model Context Protocol for finance and operations apps for more information.
  3. Validate that your agent prompts execute as expected.

While no immediate action is required if you are not using MCP‑based integrations, we recommend reviewing your environment(s) to understand potential impact by following the steps listed below:

  1. Review the new dynamic MCP server architecture and capabilities in the official documentation.
  2. Identify any agents, Copilot experiences, or integrations that currently rely on the static MCP server.
  3. Plan migration to the new dynamics MCP server where applicable.