Microsoft's 2026 release wave 1 introduces a public preview of an MCP server for the Dynamics 365 Business Central admin center. Microsoft's release plan says MCP-compatible AI agents can use standardized admin APIs to retrieve environment information and propose actions such as sandbox copies or update scheduling, subject to explicit user confirmation. The capability targets environment administration, not unrestricted autonomous access to ERP data.
Microsoft has introduced a public preview of a Model Context Protocol (MCP) server for the Dynamics 365 Business Central admin center as part of its 2026 release wave 1. Microsoft's release plan lists public-preview availability from April 1, 2026, and describes the service as a standardized, self-describing interface to Business Central environment-management APIs.
The server allows MCP-compatible AI agents to discover available administration operations, understand the relevant context, and return structured responses sourced from the admin center. Microsoft identifies Visual Studio Code as one supported AI-tool scenario. Administrators can query update status, available upgrades, installed extensions, and update history using conversational prompts rather than scripts or bespoke integrations.
Administration APIs, not a blanket ERP-data connector
Microsoft's documentation is specific about the initial scope: the MCP server exposes Business Central admin center APIs. The documented examples focus on environment operations, including:
- •Checking scheduled environment updates.
- •Copying an environment to a sandbox and triggering an update.
- •Reviewing update history and investigating failed upgrades.
- •Listing extensions installed in an environment.
Agents can propose follow-up actions, but Microsoft states that users retain control through explicit confirmation steps. This distinction matters for ERP teams assessing descriptions of MCP as a general natural-language interface to Business Central. The official release-plan entry substantiates admin-center workflows; it does not, by itself, establish unrestricted access to operational entities such as customer, item, or sales-order records.
Reduced scripting overhead, with familiar control requirements
Microsoft frames the feature as an alternative to routine administration that previously required PowerShell scripts or Logic Apps. Its stated business value is to make environment management more accessible and consistent while reusing the same secured Business Central admin-center APIs.
Stoneridge Software's April overview similarly characterizes MCP support as a way to simplify connections between Business Central and Copilot Studio, reducing reliance on complex API configuration for organizations building AI-driven workflows. Innovia's release overview also lists improved MCP tooling among the release's AI and Copilot changes.
For platform engineers, the practical value is the protocol boundary: an MCP client can discover tools and invoke standardized operations without a separate custom integration for each client. Companies implementing comparable agent interfaces still need to evaluate identity boundaries, role permissions, confirmation requirements, logging, and approval workflows. Those are especially consequential when an assistant can request environment copies, upgrades, or other operational changes.
Release context
Microsoft's Update 28.0 overview identifies the 2026 wave 1 release as the Business Central version 28 update and includes governance and administration capabilities among its new and updated features. The MCP server is in public preview rather than general availability, so implementation teams should treat availability and production-readiness requirements accordingly.
The ERP Software Blog's August 18 analysis argues that the feature can reduce custom integration work and make certain Business Central workflows conversational, while warning customers not to equate protocol support with risk-free autonomous access. That caution is consistent with Microsoft's own documentation, which emphasizes the admin-center scope and explicit confirmation for proposed actions.
For data and AI practitioners, the release is a concrete example of MCP being applied to enterprise operational tooling rather than only knowledge retrieval. Its near-term relevance is strongest for teams responsible for Business Central environment automation, Copilot Studio integrations, and governed agent access to administrative APIs.
Key Points #
- 1Microsoft's preview exposes Business Central admin-center APIs through MCP, enabling conversational retrieval of environment status, upgrades, extensions, and update history.
- 2Explicit confirmation remains part of documented follow-up actions, preserving an approval boundary for environment copies, updates, and related administrative operations.
- 3Comparable enterprise MCP deployments shift integration work toward identity, permissions, auditing, and tool-scope governance rather than custom client connectors.
Scoring Rationale #
This is a notable enterprise AI integration feature for Dynamics 365 Business Central administrators and teams building governed agent workflows. Its current preview status and admin-center focus limit broader impact, but MCP-based access to operational APIs is relevant to enterprise automation practitioners.
Sources #
Primary source and supporting public references used for this report.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.