Dynamics 365 Business Central Integration Guide

If you run Dynamics 365 Business Central, the ERP is rarely the whole story. Your customer records live in a CRM, your orders arrive through an online store, your leadership wants dashboards in Power BI, and somewhere there is still a legacy app nobody wants to touch. A Dynamics 365 Business Central integration is what ties those systems together so data moves automatically, instead of through copy-paste and late-night spreadsheet exports.

The good news: Business Central connects to almost anything. The hard part is choosing the right method — there are at least six, and the wrong one costs you weeks of rework or a monthly bill you never needed.

This guide covers every practical way to connect Business Central to your stack: a decision matrix organized by the system you are trying to reach, an honest framework for choosing a free connector versus a custom build, and realistic cost and timeline ranges. We write as a Microsoft Partner whose team has 20+ years of combined experience building these integrations — so the aim is the cheapest option that genuinely works, not the biggest invoice.

What Business Central Integration Actually Means

At its simplest, integration means two systems exchanging data without a human retyping it. Most integrations to and from Business Central (a few built-in ones aside) run over web services — the APIs it publishes so other software can read and write its data securely.

Before you compare methods, it helps to answer three questions about the data flow you need:

• One-way or two-way? Does the store just push orders into Business Central, or do inventory levels also need to flow back out?
• Real-time or scheduled? Must a change appear instantly, or is an hourly or nightly sync fine?
• A live view or a stored copy? Should the other system show live Business Central data, or keep its own synchronized copy?

Those answers drive almost every decision below: a nightly one-way export is a very different project from a real-time, two-way sync — even between identical systems.

How Dynamics 365 Business Central Integration Works: The Core Methods

The Business Central integration methods below run from no-code connectors you switch on in an afternoon to fully custom code your developers own. Here is the honest overview, from lightest to heaviest lift.

REST API and OData: The Recommended Business Central API Integration

Under the hood, most integration runs through Business Central's web services. There are three types, and the differences matter:

• REST API — the modern, recommended stack, optimized for performance. Business Central ships an extensive list of built-in APIs that need no code and minimal setup, and your developers can publish custom APIs (API pages and API queries) for anything the standard ones don't cover.
• OData (v4) — still supported and handy for tools like Excel and some Power BI scenarios, but Microsoft points new Business Central API integration work toward the REST stack.
• SOAP — the legacy option. Microsoft has deprecated SOAP and is phasing it out, so we migrate integrations to OData v4 or REST rather than building anything new on it.

Authentication is worth calling out: Business Central online no longer supports basic-auth access keys (deprecated in 2022). Integrations authenticate with OAuth 2.0 through Microsoft Entra ID, which is more secure but adds a setup step to plan for.

A simple REST call to read customers looks roughly like this:

GET https://api.businesscentral.dynamics.com/v2.0/{environment}/api/v2.0/companies({companyId})/customers
Authorization: Bearer {access_token}
Accept: application/json

(Endpoint simplified — confirm the exact URL format for your environment in Microsoft's documentation.)

Business Central Power Platform Integration

If your team already lives in Microsoft 365, a Business Central Power Platform integration is often the fastest win. Business Central connects natively to four Power Platform services:

• Power Automate — automate approvals and hand-offs; a flow can, for example, route any purchase order over a threshold to a manager. Note the Business Central connector is a premium connector, so budget for the right Power Platform licensing.
• Power Apps — build a lightweight mobile or task app (say, warehouse stock counts) that writes straight into Business Central. If it has to work offline all shift or scan at volume, that is a job for a custom mobile app.
• Power BI — feed live financials into leadership dashboards.
• Power Pages — stand up a self-service portal where vendors or customers check status without emailing your team.

AppSource Connectors (Connect Apps)

For many common targets, someone has already built the bridge. Microsoft AppSource lists prebuilt "connect apps" you install and configure rather than build. The Shopify Connector is the flagship example: a Microsoft-built app (preinstalled on new Business Central online environments) that does two-way sync of products, inventory, customers, and orders through the job queue. Checking AppSource first can turn a would-be custom project into a configuration task.

Azure Integration Services

When an integration gets genuinely complex — many systems, message transformation, guaranteed delivery, or an awkward legacy endpoint — Azure is the middleware layer. Azure Logic Apps offers a Microsoft-published Business Central connector plus 1,400+ others; Azure Functions handles custom logic; and Azure Service Bus provides queued messaging so a downstream outage doesn't lose data. It is the pattern our Business Central integration services use when a business outgrows point-to-point connections and needs an integration hub.

Custom AL Extensions and APIs

Sometimes the logic is unique to your business, or the target system has no connector at all. That is when a custom AL extension — code that runs inside Business Central — earns its place. From AL, the HttpClient data type calls out to any external service. Two realities to plan around, both straight from Microsoft's guidance:

• Outbound calls are blocked by default. Each extension must be explicitly allowed to make HttpClient requests, and that setting resets when an environment is copied — a classic "it worked in sandbox" trap.
• The call is synchronous (it holds the user session until it returns) and responses are capped at 150 MiB, so heavy or chatty integrations belong in Azure middleware, not inline AL.

Custom AL gives you total control. It also carries the most maintenance, which is exactly why it should be the last resort, not the first instinct.

Live Data or a Synced Copy? The Four Dataverse Patterns

When you connect Business Central to another Dynamics 365 app — most often Dynamics 365 Sales — you go through Microsoft Dataverse. Here is the wrinkle almost nobody explains in business terms: Dataverse offers four built-in ways to integrate, and they answer very different questions. It comes down to one: should the other system see live Business Central data, or its own copy?

A few honest caveats we have learned to flag up front:

• Synchronization is near-real-time, not guaranteed real-time. It runs on scheduled job-queue entries, so if your sales team needs the live number, use virtual tables or the API instead.
• Virtual tables need the "Business Central Virtual Entity" app and have limits — they don't yet support charts, images/attachments, or some advanced filters. Great for live records; not a universal answer.
• Webhooks batch their notifications. Business Central waits about 30 seconds and, if more than ~1,000 records change in that window, sends a single "collection" notification that the Power Automate connector can't process. Fine for everyday changes; something to design around for bulk updates.
• Business events are still in preview, so treat them as promising rather than production-hardened, and confirm current status before you depend on them.

Which Method for Which System? Connecting Business Central to Your Stack

Most guides organize this by method. We organize it by the question you actually have: I need to connect Business Central to ___ — what should I use? This matrix is the shortcut.

Two patterns stand out. Everything inside the Microsoft family — Dynamics 365, Power BI, Microsoft 365 — has a native or prebuilt path, so those projects are usually configuration, not code. The further you get from Microsoft's ecosystem (a non-Microsoft CRM, an old on-prem system), the more you lean on APIs, Azure middleware, or custom AL — and the more the effort climbs. Your integration budget is largely a map of how far your stack sits from Business Central's front door.

Native, Connector, or Custom? An Honest Decision Framework

Here is where most advice breaks down, because the source is usually biased: the platform vendor says "use our platform," the iPaaS says "use middleware," and the dev shop says "build it custom." As a partner that does all three, our incentive is different — the cheapest integration that holds up is the one you don't have to rebuild. We work down this list in order:

1. Check AppSource first. If a maintained connector exists for your target (Shopify being the obvious one), start there. You get Microsoft- or ISV-maintained code and a fraction of the cost. Never pay to build what you can switch on.
2. Use native Dataverse / Power Platform for anything in the Microsoft family. Connecting to Dynamics 365 Sales, Power BI, or Teams rarely needs custom code.
3. Reach for Power Automate for light, event-driven automation — approvals, notifications, simple record-to-record moves — especially triggered by Business Central webhooks.
4. Step up to Azure middleware (Logic Apps, Functions, Service Bus) when you have multiple systems, need data transformed or reliably queued, or must reach a stubborn legacy endpoint.
5. Build custom AL only when the logic is genuinely unique to your business or no connector reaches the target. It is the most powerful option and the most expensive to own — worth it when warranted, overkill when it isn't.

The honest test for going custom: if a prebuilt connector covers 80% of what you need, adapt your process to fit it before you commission code. If it covers 30%, custom is probably the lower-risk path. Most regret we see comes from building custom too early — or forcing a no-code tool into a job it was never meant for.

What Changes at 50 Employees vs. 300

Scale shifts the calculus. At ~50 employees, integrations tend to be one or two connections (store-to-ERP, ERP-to-CRM), volumes are modest, and a prebuilt connector plus a few Power Automate flows usually does the job. At ~300, you are juggling several systems and higher volume with a real cost to downtime — the point where a governed Azure integration layer (error handling, retries, monitoring) stops being over-engineering and starts being insurance. Same ERP; a different right answer.

What Business Central Integration Costs and How Long It Takes

We will be straight with you: anyone quoting a firm price for a Business Central integration without seeing your systems is guessing — cost swings on real drivers, not a list price. Still, honest ranges beat hand-waving, so here are timelines you can plan around.

Ranges reflect typical Craftware project experience and will vary with your environment — treat them as planning guides, not quotes.

The factors that drive cost up or down:

• Number of systems — each additional endpoint adds mapping, testing, and failure modes.
• Real-time vs. scheduled — live, two-way sync is more work than a nightly batch.
• Data-mapping complexity — clean, matching fields are quick; custom fields and transformations are not.
• Prebuilt vs. custom — a connector is configuration; a bespoke build is engineering.
• Error handling and monitoring — the difference between a demo and something you trust in production.
• On-prem or legacy endpoints — networking, security, and older protocols add time.

On the costs you can pin down: some AppSource connectors carry a subscription, the Business Central Power Automate and Power Apps connector is premium-licensed, and Azure services bill on consumption. We fold those into a fixed scope after a short discovery, so the number is real, not a range.

An Illustrative Business Central Integration

To make this concrete — and to be clear, the following is an illustrative, composite scenario, not a named client — picture a mid-market distributor running Business Central for finance and inventory, Shopify for its store, and Dynamics 365 Sales for its reps.

Before integrating, the pattern is familiar: someone re-keys Shopify orders into Business Central each morning, website inventory lags real stock by a day, and reps in Dynamics 365 Sales can't see whether an item is available before they promise it. Every hand-off invites error, and month-end reconciliation drags.

The right build here isn't exotic. The Shopify Connector handles store-to-ERP order and inventory sync out of the box. For the sales team, Dataverse virtual tables surface live Business Central inventory and customer data inside Dynamics 365 Sales — no duplicate copy to drift out of date. A couple of Power Automate flows cover the exceptions.

The outcome, in the scenarios we see, is qualitative but real: orders flow without re-keying, the website reflects near-current stock, and reps quote from live numbers. Notice there is no custom AL in that build — the honest recommendation leaned on prebuilt and native paths, usually the cheaper, more durable answer. The same prebuilt-first logic applies to quoting: our own Deal Desk 365 for Dynamics 365 Sales adds quote templates and discount approval.

Frequently Asked Questions

What systems does Business Central integrate with?

Effectively anything with an API. Natively, it connects to the Dynamics 365 family (Sales, Field Service) through Dataverse, the full Power Platform (Power Automate, Power Apps, Power BI, Power Pages), Microsoft 365 apps, and Shopify via a built-in connector. Beyond that, its REST and OData APIs, Azure middleware, or custom AL can reach third-party SaaS, non-Microsoft CRMs, and legacy systems.

What is the best method for Business Central integration?

It depends on what you are connecting and how live the data must be — which is what the by-system matrix above is for. Rule of thumb: check AppSource first, use native Dataverse and Power Platform for the Microsoft family, and reserve Azure middleware or custom AL for complex, multi-system, or legacy needs.

Can Business Central integrate with Salesforce or other non-Microsoft CRMs?

Yes. The tightest, near-native experience is with Dynamics 365 Sales through Dataverse, but Business Central can integrate with Salesforce or any other CRM through its REST API — typically via Azure Logic Apps, an iPaaS, or a custom connector that maps records between the two systems.

Is REST API better than OData for Business Central integration?

For most new integrations, yes. Microsoft optimizes and recommends the REST API stack, and it is the preferred way to connect external systems. OData v4 still has its place (Excel, some Power BI scenarios), while SOAP is deprecated and should not be used for anything new.

Do I need middleware for Business Central integration?

Not always. Native connectors and Power Automate handle many everyday integrations with no middleware at all. You need middleware like Azure Logic Apps or Service Bus when connecting several systems, transforming data between them, guaranteeing delivery, or bridging to a legacy or on-prem endpoint.

How much does Business Central integration cost?

It ranges from a modest configuration engagement for a single prebuilt connector to a multi-week or multi-month project for a custom, multi-system build. Cost is driven by the number of systems, real-time versus scheduled sync, data-mapping complexity, and prebuilt versus custom work — plus any connector subscriptions, premium licensing, or Azure consumption. The responsible way to get a real number is a short scoping conversation; confirm current licensing and pricing as part of it.

Talk to a Business Central Integration Partner

Business Central can connect to almost anything you run — the value is in choosing the method that fits your systems, your data, and your budget the first time. That is the call we help our clients get right every day, as a Microsoft Partner whose team has 20+ years of combined experience on the stack, with a Human + AI delivery model that keeps integration work efficient.

If you can tell us what you need Business Central connected to, we will recommend the right approach — an AppSource connector, Power Platform, Azure, or a custom build — with a rough scope, timeline, and cost, and we will point you to a free connector before we ever quote a custom one. Book a free integration consultation and get a straight answer before you commit budget.