Connecting an AI Agent to Microsoft Dynamics 365
Microsoft sells Dynamics 365 as one brand, but under the hood it is a family of three platforms with different data stores, APIs and security models. Before you wire an AI agent into it, you need to know which of them your organisation actually runs. This guide maps the three, their interfaces and their MCP servers, as documented by Microsoft in November 2026.
What does connecting an AI agent to Dynamics 365 involve?
A connected agent reads and changes records in Dynamics 365 through supported interfaces. It might summarise an opportunity, explain a customer's overdue invoices or draft a sales order. To do that it needs an identity with permissions, a set of tools (API calls or MCP tools) and rules about what it may do without asking a human.
Common reasons organisations connect an agent to Dynamics:
- Sales: enrich leads, summarise pipeline deals, suggest next steps. See how a complete sales agent is put together.
- Quotes and orders: pull items, prices and customer terms from the ERP to prepare a quote, as described for the quotation agent.
- Field and technical service: combine case history, asset data and knowledge articles; see the technical service agent.
- Finance: answer questions about open items, payment status or supplier records and flag anomalies.
If you are weighing Dynamics against another large ERP, the guide on connecting an AI agent to SAP S/4HANA covers the SAP side. The key difference with Dynamics is that Microsoft now ships a separate MCP server for each product line, so much of the plumbing already exists.
The model behind the agent matters less than you might think. Whether you run Claude, another model, or Microsoft Copilot Studio, the real design decision is which Dynamics interface the agent talks to.
Which three platforms sit behind the Dynamics 365 name?
There are three technically separate platforms. Customer engagement apps store their data in Dataverse; Business Central is a standalone ERP with its own API; Finance and Supply Chain Management run on the finance and operations platform and expose data entities. Each has its own endpoints, throttling rules and MCP server.
| Platform | Typical apps | Data access | MCP server |
|---|---|---|---|
| Dataverse | Sales, Customer Service, Field Service | Dataverse Web API, OData 4.0 | Dataverse MCP server |
| Business Central | Finance, purchasing, sales, inventory | API v2.0 (REST/OData) | Business Central MCP server |
| Finance and operations | Finance, Supply Chain Management | OData endpoint at /data | Dynamics 365 ERP MCP server |
Microsoft's customer engagement overview states that online Sales, Customer Service, Marketing, Field Service and Project Service Automation run on Microsoft Dataverse and use Power Apps model-driven design. Business Central and finance and operations apps do not; they have their own databases and interfaces.
How do you reach Dataverse apps such as Sales and Customer Service?
Use the Dataverse Web API. It implements OData version 4.0, so any language that can send authenticated HTTP requests can call it. According to Microsoft's Web API overview, every data operation still runs through the underlying organisation service, so plug-ins and business rules fire exactly as they do for users.
The URL combines environment name, region, base URL, the path /api/data/ and a version; Microsoft's request guide gives the current version as v9.2. A query for open opportunities looks like this:
# Obtain a token from Microsoft Entra ID first (OAuth 2.0)
curl -s "https://contoso.crm.dynamics.com/api/data/v9.2/opportunities?\$select=name,estimatedvalue&\$top=5" \
-H "Authorization: Bearer $DATAVERSE_TOKEN" \
-H "Accept: application/json" \
-H "OData-MaxVersion: 4.0" \
-H "OData-Version: 4.0"
Agents that loop over records will meet the service protection limits. Per user and per web server, Dataverse allows by default 6,000 requests, 20 minutes of combined execution time and 52 concurrent requests in a sliding five-minute window, according to the service protection documentation. Beyond that it returns 429 Too Many Requests with a Retry-After header, and ignoring it makes the wait longer.
Dataverse as an MCP server. If the Model Context Protocol is new to you, the overview of MCP servers for AI agents explains the basics. Dataverse itself can act as an MCP server at https://{org}.crm.dynamics.com/api/mcp. Microsoft names Copilot Studio, GitHub Copilot, Claude Desktop and Claude Code among supported clients (Dataverse MCP). Tools include search_data, create_record, update_record and read_query; delete tools require explicit user approval. An administrator must enable the server and allowed clients per environment.
How do you connect Business Central?
Business Central offers API v2.0, a REST interface secured with Microsoft Entra ID. In the online service the APIs are on by default. The agent works through API pages for entities such as customers, items and sales orders, and only sees what the signed-in user or service principal is permitted to see.
For online environments, Microsoft documents the endpoint as https://api.businesscentral.dynamics.com/v2.0/<domain>/<environment>/api/v2.0. On-premises installations ship with the APIs disabled until an administrator turns them on.
Two characteristics shape agent projects on Business Central:
- Standard APIs cannot be extended. The API v2.0 reference states that you cannot add fields to a standard API. If the agent needs a custom field, you copy the AL code and publish your own API page.
- Limits are per user. The operation limits allow each user 6,000 OData requests in a five-minute sliding window, 5 requests processed at once, up to 20,000 records per response, 100 operations per
$batchand an 8-minute timeout per request.
Business Central MCP server. All clients connect to https://mcp.businesscentral.dynamics.com and pick tenant, environment, company and configuration through HTTP headers (MCP overview). Out of the box, the server offers read-only access to the API pages the user may see; administrators grant create, modify and delete rights per API page. Sign-in uses OAuth 2.0 authorisation code flow with PKCE against Microsoft Entra ID, and non-Microsoft clients such as Claude need their own app registration.
How do you connect Finance and Supply Chain Management?
Finance and Supply Chain Management expose data through an OData service at [environment URL]/data. It publishes every data entity that developers have marked as public. The service supports create, read, update and delete, batch requests and custom actions, but it has quirks an agent must respect.
From the finance and operations OData documentation:
$expandonly goes one level deep, and thehasandinoperators are not supported.- A page holds at most 10,000 records.
- By default you only see data from the user's default legal entity;
?cross-company=truewidens that to every company the user can access. - Writes must include every field in the entity key.
Load is managed by priority rather than a fixed quota. On the Throttling priority mapping page you assign Low, Medium or High to an Entra application or a user (throttling prioritisation). Put an experimental agent on Low so it cannot starve production integrations.
Dynamics 365 ERP MCP server. The dynamic server needs version 10.0.47 or later (or 10.0.46 PQU-2 or 10.0.45 PQU-7), a Tier 2 or higher environment, and the client listed under Allowed MCP Clients (ERP MCP). It offers three tool groups: data tools for entities, form tools that operate pages the way a person would, and action tools for approved X++ classes. Microsoft scheduled the older static server with 13 fixed tools for retirement on 1 October 2026, so new projects should use only the dynamic server.
How do the three platforms compare for agent work?
They differ in data model, extensibility and cost model. If one agent has to work across several Dynamics products, do not expect a single interface. Build a separate tool set for each platform, with its own credentials and roles, and let the agent combine the results.
| Criterion | Dataverse | Business Central | Finance and operations |
|---|---|---|---|
| Extending | tables and columns in the maker portal | custom API pages in AL | data entities and actions in X++ |
| Throttling | 6,000 requests / 5 min per user and web server | 6,000 requests / 5 min per user | priority per app or user |
| MCP permissions | Dataverse security roles | configuration per API page | finance and operations security roles |
| MCP cost outside Copilot Studio | Copilot Credits, premium licences exempt | not stated in the MCP docs | 0.1 Copilot Credits per tool call |
On cost, Microsoft says Dataverse MCP tools have been billed since 15 December 2025 when used by agents built outside Copilot Studio, with exemptions for licences such as Sales Premium, Customer Service Premium and the Microsoft 365 Copilot user licence (Dataverse MCP). For the ERP MCP server, Finance Premium and Supply Chain Management Premium are exempt from the tool charge (ERP MCP).
What do you need in place first?
Identity, permissions and data quality come before the first call. An agent inherits every gap in your master data and every loose permission in your role design. Budget time for a dedicated role, a test environment and a decision about which data the language model may see at all.
- Identity: an app registration in Microsoft Entra ID or a dedicated user for the agent, never a colleague's account.
- Least privilege: a custom security role that exposes only the tables, API pages or menu items the agent needs. With the ERP MCP server, the role even limits which forms and entities the agent can discover.
- Sandbox: a test environment with realistic data. For the ERP MCP server, a finance and operations environment must be Tier 2 or higher.
- Data protection: decide which model runs where and which customer data may leave your tenant. If that rules out a public cloud model, you can host the agent on your own infrastructure, as covered under sovereign AI. Such a setup can be operated in line with the GDPR when processing agreements and data flows are documented.
- Audit trail: every write must be traceable. Microsoft states that the Business Central MCP server performs all operations under the user's identity so audit trails show who acted; the ERP MCP server applies the security roles of the authenticated user.
What does a sensible rollout look like?
Move from read-only to tightly controlled writes. That way you learn whether the agent finds the right data before it is allowed to change anything. Each step should end with a review by the business team that owns the process, not only by IT.
- Pick one process with a clear outcome, such as "summarise an opportunity" or "explain this customer's open items".
- Choose platform and interface: Dataverse, Business Central or finance and operations, and decide between direct API calls and an MCP server.
- Start read-only. On Business Central this is already the default MCP configuration.
- Trim the tool list. Give the agent a short allow list instead of every tool. Microsoft has already renamed Dataverse MCP tools once, so recheck name-based allow lists after updates.
- Write with approval. First writes should be drafts that a person confirms, following the human-in-the-loop pattern.
- Handle limits and errors: honour
429andRetry-After, catch timeouts, and plan around maintenance windows. - Operate: watch per-call costs, review roles regularly and read the logs.
In our own operations, step 4 has had the clearest effect on quality: the fewer tools an agent can choose from, the less often it picks the wrong one.
What are the limits and risks?
An agent is only as safe as its permissions and as good as the data behind them. Over-broad roles, unchecked writes and unmonitored costs cause most problems. On top of that, Microsoft documents product-specific restrictions that not every use case can live with.
- Language and formats on the ERP MCP server: metadata and guidance are US English only, and dates and numbers use ISO format regardless of locale. Some controls, such as calendars and radio buttons, are not available to agents.
- Maintenance windows: the ERP MCP server is unavailable during environment servicing, and requests fail.
- Business Central extensibility: every extra field means a custom AL API page and development effort.
- Unintended actions: form tools are powerful. Without a confirmation step, an agent can post documents nobody asked for.
- Cost creep: Copilot Credits per tool call add up for agents that make many small queries. Check licensing before you scale.
- Legal: this is not legal advice. Whether personal data may be sent to a language model is a question for your data protection officer, and the answer differs between jurisdictions.
How do you get started?
Start with a question that currently costs people search time, and with one Dynamics platform. Connect the matching MCP server read-only in a sandbox and test it with real questions from the business team. Only add write access, with approval, once the answers are reliable.
A practical first test: connect an MCP-capable client to the sandbox, give it a narrow read-only role and ask ten questions that staff would normally look up themselves. Record which answers are right, which data is missing and which tools the agent called. The result tells you whether your roles, master data and tool selection are ready.
To see how complete agents for quotes, sales, service and knowledge management are built and which systems they connect to, browse the AI agents overview. Deeper guides on Business Central and the Dataverse Web API will appear in this topic area and are listed here automatically.
Frequently asked questions
Is there one API that covers every Dynamics 365 product?
No. Customer engagement apps use the Dataverse Web API, Business Central exposes API pages at api.businesscentral.dynamics.com, and Finance and Supply Chain Management publish data entities through their own OData endpoint.
Can Claude or other non-Microsoft agents use Dynamics 365 data?
Yes, through the MCP servers. Microsoft lists Claude as a supported client for both the Dataverse and the Business Central MCP servers; for Business Central, non-Microsoft clients need their own Microsoft Entra app registration.
Does MCP access cost extra?
Sometimes. Since 15 December 2025, Dataverse MCP tools are billed when used by agents built outside Copilot Studio, and the Dynamics 365 ERP MCP server charges 0.1 Copilot Credits per tool call in that case. Several premium licences are exempt.
Does the agent itself need a Dynamics licence?
For finance and operations apps, Microsoft exempts agent identities assigned to the System agent security role from user licence requirements. For Dataverse and Business Central, confirm the licensing position with your Microsoft partner before you start.
Sources
- Microsoft Learn: Use the Microsoft Dataverse Web API learn.microsoft.com
- Microsoft Learn: Compose HTTP requests and handle errors (Dataverse) learn.microsoft.com
- Microsoft Learn: Service protection API limits (Dataverse) learn.microsoft.com
- Microsoft Learn: Connect to Dataverse with model context protocol learn.microsoft.com
- Microsoft Learn: Customer engagement apps run on Dataverse learn.microsoft.com
- Microsoft Learn: API (v2.0) for Dynamics 365 Business Central learn.microsoft.com
- Microsoft Learn: Endpoints for the Business Central APIs learn.microsoft.com
- Microsoft Learn: Operation limits in Business Central learn.microsoft.com
- Microsoft Learn: Business Central MCP server overview learn.microsoft.com
- Microsoft Learn: Open Data Protocol (OData) in finance and operations apps learn.microsoft.com
- Microsoft Learn: Throttling prioritization (finance and operations) learn.microsoft.com
- Microsoft Learn: Use Model Context Protocol for finance and operations apps learn.microsoft.com