1. Home
  2. Systems
  3. Dynamics 365 integration

Dynamics 365 integration starts with which app you run

Dynamics 365 is a family of apps, and they do not share one API. Business Central has API v2.0 and webhooks. Finance and Supply Chain use OData data entities, batch data APIs and business events. Sales and Customer Service run on Dataverse. The limits differ too: Business Central allows each user 6,000 OData requests in a 5-minute sliding window before it returns HTTP 429.

Checked 18 November 2026

Which Dynamics 365 app are you connecting?

Name the app first. Each one has its own main API in Microsoft’s docs. Limits, sign-in rules and end dates differ too.

Scroll the table sideways to see every column.

App Main API Microsoft’s own links
Business Central API v2.0 at api.businesscentral.dynamics.com/v2.0/<environment name>/api/v2.0, plus webhooks Shopify Connector, Dataverse sync, Power Automate connector, Teams
Finance and Supply Chain, which Microsoft calls finance and operations apps (F&O) OData on data entities, a batch data API, business events Dual-write to Dataverse, Power Automate, Link to Fabric
Sales and Customer Service Dataverse Web API, over OData Dual-write, Business Central’s Dataverse sync
Dynamics AX 2012 R3 Extended support ended January 10, 2023 F&O replaces its query and document services
Dynamics GP Retirement date December 31, 2029 Cloud migration tools to Business Central online

Business Central: API v2.0, webhooks and per-user limits

Business Central online has its APIs on by default. A sync calls API v2.0 with a Microsoft Entra token. It hears about changes through webhooks. Limits count per user, so the way you sign in sets how fast a sync can go.

Sign-in

Microsoft says live links should use Entra OAuth v2. A job that runs with no one at the keyboard uses the client credentials flow. A user sign-in can ask for a second check, such as a code on a phone, and nobody is there to type it. The job stops. On Business Central online, old web service access keys stopped working after October 1, 2022. On-premises, Microsoft keeps them as an option for now.

Limits a sync must respect

Scroll the table sideways to see every column.

Limit Microsoft’s number
OData requests per user 6,000 in a 5-minute sliding window, then HTTP 429
Requests handled at once per user 5; the rest wait in a queue
Entities in one response 20,000, then HTTP 413
Operations in one $batch call 100
Longest request 8 minutes, then HTTP 408 and the session ends
Webhook subscriptions per environment 200

Service principals are the app logins a sync uses. They get the same limits as people. For a heavy load, Microsoft says to spread the work across several users or service principals.

Webhooks

You sign up with a POST to /api/v2.0/subscriptions, naming the URL to call and the resource to watch.

A subscription lapses after three days unless you renew it with a PATCH. Your endpoint must echo back the token it gets, with status 200. One call can carry changes from several subscriptions.

Custom fields and old routes

API v2.0 cannot take extra fields. For a custom field, Microsoft says to copy the AL code, the code language of Business Central add-ons, and build your own API on top of it.

SOAP has given way to OData V4. From version 29.0, Microsoft’s 2026 release wave 2, a Microsoft page can no longer be a SOAP endpoint. Major releases ship in April and October, so that change is landing now.

F&O: pick the pattern by volume

Microsoft lists six patterns for F&O. They are Power Platform, OData, the batch data API, custom services, calls to outside web services, and Excel. Real-time work uses OData or a custom service, while big loads use the batch data API, and Microsoft’s rule of thumb is to go batch once a job passes a few hundred thousand records.

Scroll the table sideways to see every column.

Microsoft’s own example Volume Pattern it picks
A customer portal reads order status 5,000 records an hour OData
A front-end system sends in sales orders 200,000 records an hour, every five minutes Batch data API

OData and custom services run business logic at once. Errors come straight back to the caller. A batch job does not report back, so the caller must poll for the result. Microsoft also says not to use OData for Power BI reports. Use the entity store for those.

A data entity hides the tables behind it. A customer spread over CustTable, DirParty and other tables reads as one record. To reach one record over OData, you give every field in the entity key. OData actions added through extensions are not supported.

Recurring integrations and on-premises

Recurring integrations build on data entities and the Data management framework. They sign in through an app ID in Microsoft Entra. They do not run on-premises. There, the only supported API is the Data management package REST API.

Business events

Business events tell outside systems that something happened, such as a confirmed purchase order.

Scroll the table sideways to see every column.

Business events Microsoft’s rule
Where they go Power Automate, Service Bus, Event Grid or other endpoints, on your own subscription
Retries for a failed event 3 by default, 1,000 milliseconds apart
Endpoints per event in a legal entity Up to 10 by default
Repeats Each payload has a control number, so the receiver can spot them
Not meant for Exporting data or large payloads

Throttling

Since March 31, 2023, user-based service limits are no longer enforced. Resource-based limits stay on. You can give each link a Low, Medium or High priority. These limits apply only online.

Dataverse: where Sales, Customer Service and dual-write meet

Sales and Customer Service run on Microsoft Dataverse. Other systems reach them through its Web API, which speaks OData. By default, each user gets 6,000 requests and 20 minutes of execution time per web server in any 5 minutes, and at least 52 requests at once. Microsoft says these limits can change. Past a limit, the API returns HTTP 429 and says how many seconds to wait.

Dual-write for F&O

Dual-write links F&O to Dataverse both ways. A change on either side writes to the other. It comes as two Marketplace add-ons you install on Dataverse. Microsoft’s cases include one shared master list each for customers, products and vendors.

Business Central and Dynamics 365 Sales

The first link between Business Central and Sales must go through Dataverse. Reconnecting puts back Microsoft’s default settings and overwrites yours. Write your mappings down first. Stock levels sync on a job that runs every 30 minutes. Two-way order sync and the older order link cannot both be on. Business Central online links only to Dataverse in its own Entra tenant.

Power Automate: small flows on Microsoft’s connectors

Power Automate suits approvals and small flows around Dynamics. Its Business Central connector is Premium. In Azure Logic Apps, the same connector is Standard. It allows 300 API calls per connection every 60 seconds. So a flow that makes one call per record moves at most 300 records a minute through one connection, which suits approvals more than a nightly bulk sync. A record must be under 8 MB.

The Fin & Ops Apps connector reaches F&O data entities, and it is Premium too. Power Automate can also subscribe to business events directly.

Business Central’s Shopify Connector comes preinstalled for new sign-ups and trials. It syncs five things: items, prices and taxes, stock, customers and companies, and orders through to fulfillment. It renews its Shopify token by itself. If no refresh works for 90 days, you reconnect the shop. Microsoft lists connecting from a sandbox as a known issue.

For reports, Link to Fabric puts Dynamics 365 data, F&O included, into Microsoft OneLake. Export to Azure Data Lake stops for good on November 30, 2026, so plan that move now.

Business Central and F&O both have MCP servers now

MCP, the Model Context Protocol, lets an AI agent use a system’s data and actions as tools.

  • Business Central. The server sits at mcp.businesscentral.dynamics.com. By default it offers read-only discovery tools. Admins choose which API pages and queries agents may use. Microsoft says it plans to charge for these tools, with details to come.
  • F&O. The Dynamics 365 ERP MCP server needs version 10.0.47, 10.0.46 PQU-2 or 10.0.45 PQU-7 at least. It runs on Tier 2 or higher. It has data, form and action tools.

An older, static ERP MCP server had 13 tools. On 18 November 2026, Microsoft’s page still said it “will be retired on October 1, 2026”. That date has passed. The page tells users to move to the dynamic server. We could not confirm from Microsoft whether the static one is now off, so build on the dynamic one. Our page on Dynamics 365 AI agents covers Microsoft’s own agents and where a custom one fits.

AX 2012 support has ended, and GP ends on December 31, 2029

Microsoft’s lifecycle page lists January 10, 2023 as the extended end date for Dynamics AX 2012 R3. In F&O, the OData endpoint replaces AX 2012’s query services. Data entities replace its document services. So an AX link moves by being rebuilt on data entities.

Dynamics GP follows Microsoft’s Modern Lifecycle Policy. Its retirement date is December 31, 2029. Microsoft documents which GP data its cloud tools move to Business Central online. Weigh any new GP ecommerce link against that date.

Dates that break Dynamics integrations

Scroll the table sideways to see every column.

What changed Date or version What to do
Business Central online web service access keys Stopped after October 1, 2022 Sign in with Entra OAuth
Business Central OData V3 Removed in 2021 release wave 1 Use OData V4
Business Central nativeInvoicing API Removed in 2023 release wave 2 Use API v2.0
SOAP for Microsoft pages in Business Central Version 29.0, 2026 release wave 2 Move to OData V4
Export to Azure Data Lake Stops on November 30, 2026 Plan a move, such as Link to Fabric
Static ERP MCP server Microsoft’s page still says October 1, 2026 Use the dynamic ERP MCP server

Business Central ships two major releases a year, in April and October. Each major version’s update window lasts five calendar months. So test every link in each window.

The app, the volume and the speed decide the route

We start with the app, the volume and how fresh the data must be.

  • Thousands of records an hour, needed now. OData in F&O, or API v2.0 in Business Central.
  • Hundreds of thousands of records on a schedule. The batch data API or recurring integrations.
  • Dynamics must tell another system that something happened. Business Central webhooks or F&O business events.
  • Sales or Customer Service must share customers and products with the ERP. Dual-write, or Business Central’s Dataverse sync.
  • A Shopify store on Business Central. Try Microsoft’s Shopify Connector before a custom build.
  • An AI agent should work in Dynamics. The MCP servers, or a custom agent we build.

Our team has taken Dynamics 365 Business Central and Dynamics 365 Finance live. For a new setup, see ERP implementation services. For AI work across systems, see AI integration services.

Questions

What is CRM integration in Dynamics 365?

It links the CRM, where your sales team tracks customers and deals, to the ERP that holds orders and invoices. Business Central links to Dynamics 365 Sales through Dataverse, and a first link must go that way. Salespeople can then see Business Central information while they work in Sales, and sales orders can sync both ways. Finance and operations apps use dual-write for the same job.

How do I enable the Microsoft Teams integration?

A Teams admin installs the Business Central app from the Teams admin center: Teams apps, Manage apps, then Edit installs, for everyone or for chosen groups. That needs at least the Teams Administrator role. It works only with Business Central online. Each user needs Teams through a Microsoft 365 Business or Enterprise plan, Teams EEA or a similar plan. Free Teams and Teams Essentials are not supported. The URL previews policy must be on, or Business Central links will not show as cards.

What is replacing Microsoft Dynamics GP?

Microsoft's lifecycle page lists December 31, 2029 as the retirement date for Dynamics GP. Microsoft documents a move to Business Central online, with cloud migration tools that carry GP data across. GP fiscal periods become accounting periods. The main account segment becomes the Business Central account number, and the other segments become dimensions. Our team has taken Business Central live.

Does Dynamics 365 have an API?

Each app has its own. Business Central online has API v2.0, on by default, and you can explore it through an OpenAPI file. Finance and Supply Chain put each public data entity on an OData endpoint, with create, read, update and delete. They also have a batch data API for big files. Sales and Customer Service use the Dataverse Web API, which speaks OData too.

Can Business Central connect to Shopify without middleware?

Yes. Microsoft's Shopify Connector comes preinstalled for new Business Central sign-ups and trials. It syncs items, prices and taxes, stock, customers and companies, and orders with fulfillment. It renews its Shopify token by itself, but if no refresh works for 90 days you must reconnect the shop. Microsoft lists connecting from a sandbox as a known issue, so plan your tests around it.

Is Dynamics AX still supported?

No. Microsoft's lifecycle page, which shows dates in Pacific time, lists October 12, 2021 as the mainstream end date for Dynamics AX 2012 R3 and January 10, 2023 as the extended end date. Its successor is the finance and operations apps. There, the OData endpoint replaces the AX 2012 query services and data entities replace the document services. So an AX link moves by being rebuilt on data entities.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Talk through your Dynamics 365 links

Bring the Dynamics 365 apps you run and the systems they must talk to, and we can go through the routes, limits and dates for each link. The first call is free.

Book a Dynamics integration call