ERP · Microsoft

Microsoft Dynamics 365 Business Central integration services

Microsoft Dynamics 365 Business Central (formerly Dynamics NAV) is Microsoft’s ERP for small and mid-sized companies, sold online as Essentials or Premium and also available on-premises. Companies integrate it when a store, marketplace, CRM, accounting package or AI assistant sits outside Business Central and orders, stock, invoices and customers must move without re-keying. AIONDATA builds these integrations on the Business Central API v2.0, custom API pages written in AL, webhook subscriptions, Microsoft’s own connectors where they fit, and MCP servers for AI agents.

California-based leadership · Serving US and international teams

Dynamics 365 BC
AIONDATAsync · MCP · rules
AI agentsClaude · ChatGPT · yours
CustomersOrdersInvoicesInventoryPaymentsTickets
Illustrative integration flow

Scope a Dynamics 365 BC integration

Tell us the other system and what needs to flow between them. You'll get an honest scope and timeline.

Please share the systems and workflow—not credentials or customer records. We’ll confirm API access, scope and next steps.

NVIDIA Inception

NVIDIA Inception member

Part of NVIDIA’s program for startups building with AI and accelerated computing.

About the program
Pravin BansalSravan Modugula

Bay Area roots. Enterprise experience.

Pravin’s experience includes Google and SmartBear. Sravan previously held leadership roles at JPMorgan Chase and First Republic Bank.

Meet the founders

San Francisco Bay Area, California

9110 Alcosta Blvd Ste H345, San Ramon, CA 94583

US-led delivery, with engineering in India. Supporting US and international organizations.
Prefer email? info@aiondata.io

Let’s scope your integration.

Just your name and email to get started. Your details are handled under our Privacy Policy.

Data

What we typically sync

  • 01Customers, vendors and contacts
  • 02Items, item variants, GTINs and item categories
  • 03Sales quotes, sales orders and sales order lines
  • 04Posted sales invoices and sales credit memos
  • 05Purchase invoices and purchase invoice lines
  • 06Inventory on hand per item and location
  • 07General ledger entries, accounts and dimensions
  • 08Journals and customer payment journals

Outcomes

Common Dynamics 365 BC integration use cases

  • Turn Shopify, Amazon or Adobe Commerce orders into Business Central sales orders and send stock, prices and shipment tracking back to the channel.
  • Keep Business Central customers, items and posted invoices aligned with HubSpot, Salesforce or Dynamics 365 Sales, and create sales orders from won deals.
  • Exchange invoices, bills and payments between Business Central and Zoho Books or another ledger that a subsidiary or a Nordic entity runs.
  • Let Claude, ChatGPT or Microsoft Copilot answer questions about customer balances, open orders and stock through the Business Central MCP server or a custom one, under each user’s permissions.

Editions and APIs

Microsoft Dynamics 365 Business Central: editions, hosting and APIs

The edition, hosting model and API on each side decide what the integration can do and how it is built.

Editions, hosting and APIs
Business Central Essentials (online)Microsoft list price $80 per user per month, paid yearly (Sep 2026). Online only: API v2.0 enabled by default, one production and three sandbox environments at no extra charge, the Shopify Connector, Dataverse integration, Copilot and the official MCP server.
Business Central Premium (online)$110 per user per month, paid yearly (Microsoft list price, Sep 2026). Same APIs, environments, connectors and limits as Essentials; the edition changes which application areas users get, not what an integration can reach. Team Members ($8) is a limited-user license, not one an integration signs in with.
Business Central on-premisesSame API v2.0 and custom AL APIs once ODataServicesEnabled and ApiServicesEnabled are set on the server instance, the OData port (7048 by default) is open and Integrate APIs has run on the API Setup page. Authentication is NavUserPassword with an access key or Microsoft Entra ID with OpenID Connect, which service-to-service requires. No Shopify Connector, Copilot or official MCP server.
APIs and web servicesREST API v2.0 at https://api.businesscentral.dynamics.com/v2.0/{environment}/api/v2.0, updated monthly, with company-scoped resources such as customers, items, salesOrders and salesInvoices. Custom API pages publish at /api/{publisher}/{group}/{version} with SystemId as the key; API queries are read-only. OData V4 still publishes pages, queries and codeunits; SOAP is deprecated, and Microsoft pages lose SOAP exposure in version 29.0 and OData exposure in version 30.0. Power Platform connectors use only the REST APIs.
Rate limits, webhooks and environments (online)Per user or service principal: 6,000 OData requests in a 5-minute sliding window, 5 concurrent requests, 100 connections, an 8-minute operation timeout, 100 operations per $batch and 20,000 entities per page. Up to 200 webhook subscriptions per environment, each expiring after three days unless renewed. 300 companies per environment; 80 GB shared storage plus a per-user allowance.
AI access (MCP)Microsoft’s MCP server at https://mcp.businesscentral.dynamics.com has been generally available since update 28.0 for Business Central online, read-only by default and governed per API page from the MCP Server Configurations page. Update 29.0, in preview on sandboxes with general availability planned for the first week of October 2026, adds tools that define and run custom data queries.

Options, cost and timeline

Ways to deliver Microsoft Dynamics 365 Business Central integration

A prebuilt connector is sometimes enough. This comparison shows when each route fits, what it typically costs and how long it takes.

Delivery options, cost and timeline
ApproachTypical costTypical timeFits whenWatch for
Microsoft-built connectors (Shopify Connector, Dynamics 365 Sales through Dataverse)Included with Business Central online; you still need a Shopify license or Dynamics 365 Sales licenses. Configuration and testing time only.Days to a few weeksOne or more Shopify shops, including B2B companies, with standard pricing, taxes and locations; Dynamics 365 Sales customers who accept Microsoft’s table mappings and 30-minute job queue cadence.Online only. The Shopify Connector pins one Shopify API version per Business Central major release, so environments must take major updates on time. Reconnecting Dynamics 365 Sales through Dataverse resets custom mappings to defaults. Both are extensible in AL.
Marketplace connector (Tinx, Suite Engine CSM, HubSpot’s Business Central app)Subscriptions: Suite Engine CSM Core $250 per month plus $225 per month for order or listing management and $200 per month for Amazon financial management; Tinx connectors on a fixed monthly fee per Amazon region or shop (vendor list prices, Sep 2026). HubSpot’s app needs Data Hub Starter or Professional for custom field mappings.A few weeks to configure, map and testAmazon, Adobe Commerce, BigCommerce, WooCommerce or Walmart channels with standard flows; small HubSpot sales teams that need contacts, products, deals and orders.Check each listing’s supported Business Central versions and localizations. HubSpot’s app syncs contacts, not companies. Settlement, tax and return handling differ by connector, so test them before go-live.
Power Automate, Power Apps or Logic AppsThe Business Central connector is Premium in Power Automate, Power Apps and Copilot Studio and Standard in Logic Apps; add that licensing to the build time.Days for approvals and notifications; a few weeks for record syncsApproval flows, alerts, simple record copies and Teams or Outlook steps where the client already runs Power Platform.Each connection is limited to 300 calls per 60 seconds and records over 8 MB fail. Flows cannot process collection webhook notifications, so a change touching more than 1,000 records in 30 seconds never triggers them. Retries and reconciliation are yours to design.
Custom API integration or MCP server built by AIONDATAQuoted after a short discovery of flows, companies, volumes and reconciliation needs. No extra Business Central license for service-to-service access.Usually a few weeks for a standard scope; typically two to three months for multi-company, on-premises or marketplace settlement workSeveral companies or channels, custom AL fields, on-premises, high volumes, finance-grade reconciliation, and AI agents that need governed tools across Business Central and other systems.Needs a named owner for alerts and held records. Custom API pages ship as an extension and follow your update and testing cadence. We hand over mapping documents and runbooks.

Vendor prices are list prices from their public pages on the date shown; confirm current pricing with each vendor.

Business Central API and authentication model

Business Central online exposes the REST API v2.0 at https://api.businesscentral.dynamics.com/v2.0/{environment}/api/v2.0 with every resource under a company, so a sync works company by company (up to 300 per environment). When a standard resource lacks a field, we write a custom API page in AL with its own APIPublisher, APIGroup and APIVersion and SystemId as the OData key, which Microsoft recommends so that Power Automate and webhooks work with it; read-only joins become API queries.

Authentication is Microsoft Entra ID only. Unattended syncs use the client credentials flow with a token for https://api.businesscentral.dynamics.com/.default and an entry on the Microsoft Entra applications page carrying the permission sets the integration needs; applications cannot hold SUPER and need no user license. On-premises, service-to-service works from versions 18.11 and 19.5 when the server uses Entra ID with OpenID Connect and ValidAudiences includes https://api.businesscentral.dynamics.com; older Dynamics NAV installs fall back to OData or SOAP with NavUserPassword.

  • Web service access keys stopped working online on October 1, 2022; on-premises still allows them.
  • Microsoft pages lose SOAP exposure in version 29.0 and OData exposure in version 30.0; copy the page into your extension if you still need it.
  • Custom APIs default to $schemaversion 2.0 since version 24, and delta links were removed in favor of webhooks.

What to sync and how records are matched

Every record has a human number (customer No., item No., order number) and an immutable SystemId GUID returned as id. We store the GUID on the other system’s record after the first match and use the number only for the initial load, because numbers can be renamed and repeat across companies. On a salesOrder, externalDocumentNumber holds the store or CRM reference, which is how a Shopify, Amazon or HubSpot order is found again and how duplicates are blocked.

Direction follows ownership: Business Central owns items (number, displayName, gtin, unitPrice, itemVariants and the read-only inventory quantity) and posted documents; the channel owns orders and web customers; the CRM owns contacts and deals. Posted invoices are history, so corrections go through credit memos. Dimensions, posting groups and tax groups must exist before a record can post, so the mapping workbook lists them per company.

  • Sales order status is Draft, In Review or Open; the shipAndInvoice bound action posts shipment and invoice in one call.
  • Item type is Inventory, Service or Non-Inventory; only Inventory items carry stock.
  • lastModifiedDateTime on each resource drives delta pulls and the nightly reconciliation.

Failure, retries and reconciliation

Business Central answers 429 when a user exceeds 6,000 requests in five minutes or 100 connections, 503 when a queued request waits more than eight minutes, 408 when an operation runs past eight minutes and 413 when a page exceeds 20,000 entities. Microsoft’s guidance is retry with a cool-off period, fewer and larger calls through $batch, $expand and deep inserts, and webhooks instead of polling. We queue every call, back off on 429, keep batches inside the timeout and spread heavy loads across more than one service principal because limits are per user.

Webhooks are the primary trigger and the weakest link if left alone. A subscription lives three days and is renewed with a PATCH that repeats the validationToken handshake; notifications are delayed about 30 seconds and more than 1,000 changes collapse into one collection notification with a filter; a failed delivery is retried for 36 hours only after a 408, 429 or 5xx, otherwise the subscription is deleted; and changes by a delegated admin are not notified until a licensed user changes the entity. We renew daily, answer 200 and process from a queue, treat collection notifications as a delta pull and run a scheduled comparison on lastModifiedDateTime.

  • Updates send If-Match with the record’s ETag so a stale write fails instead of overwriting a user’s change.
  • Records that fail validation (blocked customer, missing posting group, closed period) are held with the Business Central error text and retried once the data is fixed.
  • A daily reconciliation report compares counts and totals per company and flags anything unmatched.

Security, permissions and data residency

Business Central online authenticates only through Microsoft Entra ID, so Conditional Access, MFA and sign-in logs cover integrations as well as people, and admins can restrict which external tenants may reach an environment. Data at rest is encrypted with Transparent Data Encryption, environments linked to a Power Platform environment can use a customer-managed key and Customer Lockbox, and administrative actions land in the Microsoft Purview audit log, kept 180 days by default.

Residency follows localization: the country chosen for an environment decides its Azure geography (United States for US, Sweden for SE, Norway for NO, India for IN, Europe for DK and FI) and the admin center shows the exact region. Backups are kept 28 days. Copilot prompts may leave that geography to reach Azure OpenAI: US environments need no consent, EU-hosted ones process inside the EU Data Boundary, and elsewhere admins confirm the Allow data movement toggle on the Copilot & agent capabilities page. Outbound IPs for allow-listing come from the Dynamics365BusinessCentral service tag.

  • A sandbox copied from production disables webhooks and the CRM and Dataverse connection setups and blocks outbound HttpClient calls per extension, which Microsoft does to prevent accidental use of production services.
  • Our services run in your Azure tenant or ours, in the region you choose; secrets sit in a key vault and tokens are short-lived.

Timeline, environments and acceptance tests

Essentials and Premium tenants get one production and three sandbox environments, and a sandbox can be a copy of production with job queue tasks stopped, agents off and integration setups cleared. We build and test there, on your data, before touching production; sandboxes run on a lower performance tier, so throughput is measured in production during a controlled cut-over.

Business Central online takes a major update every April and October, with previews on sandboxes a month earlier and a five-month window to schedule production; minor updates arrive monthly. Custom API pages ship as an extension, so before each major we rerun the integration tests on a preview sandbox and confirm the Shopify Connector, which pins one Shopify API version per major, is current. A standard scope usually takes a few weeks; multi-company, on-premises or marketplace settlement work typically two to three months.

  • Create, update and re-send the same channel order; exactly one sales order exists and externalDocumentNumber matches.
  • Post a partial shipment and a credit memo; the channel and CRM show the right status and amounts.
  • Renew a webhook subscription past its three-day expiry and replay a collection notification.
  • Force a 429 and a validation error; both retry or hold as designed and appear on the reconciliation report.

AI agent access via MCP

Business Central online has an official MCP server, generally available since update 28.0 (2026 release wave 1). Hosts connect to https://mcp.businesscentral.dynamics.com and select the environment with TenantId, EnvironmentName, Company and an optional ConfigurationName header; values with non-ASCII characters, common in Nordic company names, are Base64-encoded. Authentication is OAuth 2.0 with PKCE against Microsoft Entra ID, so every tool call runs as the signed-in user. The server is read-only by default; the MCP - ADMIN permission set unlocks configurations where Unblock Edit Tools and per-page Allow Create, Modify, Delete and Bound Actions govern writes, and Dynamic Tool Mode works around Copilot Studio’s 70-tool limit.

Try the official server first. Its limits are why customers still ask for a custom MCP server: it is online only, so on-premises tenants need a custom server or a community project; its tools are API pages, so rules that span pages or systems (check credit, stock and open orders, then draft an order for approval) live in a custom AL API or a custom server; and background agents with their own service identity are not what it is designed for. Update 29.0, with general availability planned for the first week of October 2026, adds tools that define and run custom data queries. Our Business Central MCP server guide, linked below, compares the options for Claude, ChatGPT and Copilot Studio.

  • Non-Microsoft hosts such as Claude and ChatGPT need your own Entra app registration; VS Code and Copilot Studio use Microsoft’s preregistered app.
  • ListPart and CardPart API pages are not available as tools; expose a top-level API page instead.
  • The Power Platform connector also offers a Dynamics 365 Business Central MCP action for Copilot Studio agents.

How AIONDATA scopes and delivers a Business Central integration

AIONDATA is an independent consultancy, not a Microsoft partner, with leadership in San Ramon, California, engineering in Noida, India, and delivery processes certified to ISO 9001:2015 and CMMI Level 3. Discovery is a short call plus read-only access to a sandbox: we list your companies, localizations, custom fields and extensions, the systems on the other side, volumes and what finance must reconcile, then send a written scope with a fixed price and a mapping workbook per company.

Build follows the mapping: custom AL API pages where standard ones fall short, a queue-based service or Power Automate flows where they fit, webhook subscriptions with renewal, monitoring and the reconciliation report. Acceptance tests run on your sandbox, cut-over happens in a window you choose, and handover includes runbooks, alert routing and optional support, so your Business Central partner or in-house team can maintain what we deliver.

Technical details last reviewed September 30, 2026. Product capabilities and prices change; confirm them for your edition.

Sources: Microsoft Learn: API (v2.0) for Business Central · Microsoft Learn: API endpoints (online and on-premises) · Microsoft Learn: Enabling the APIs on-premises · Microsoft Learn: Developing a custom API in AL · Microsoft Learn: REST APIs, OData and SOAP compared · Microsoft Learn: Web services authentication · Microsoft Learn: Service-to-service authentication · Microsoft Learn: Operational limits online · Microsoft Learn: Working with API limits · Microsoft Learn: Working with webhooks · Microsoft Learn: salesOrder resource type · Microsoft Learn: item resource type · Microsoft Learn: Production and sandbox environments · Microsoft Learn: Update cycles · Microsoft Learn: Deprecated platform features · Microsoft Learn: Developer and admin FAQ · Microsoft Learn: Security in Business Central online · Microsoft Learn: Country availability and Azure geography · Microsoft Learn: Shopify Connector overview · Microsoft Learn: Shopify Connector technical FAQ · Microsoft Learn: Integrating with Dynamics 365 Sales · Microsoft Learn: Business Central connector for Power Platform and Logic Apps · Microsoft: Business Central pricing · Microsoft Learn: Copilot FAQ for Business Central · Microsoft Learn: Consumption-based billing for agents · Microsoft Learn: Copilot data movement across geographies · Microsoft Learn: Business Central MCP server overview · Microsoft Learn: Configure the Business Central MCP server · Microsoft Learn: Update 28.0 (2026 release wave 1) · Microsoft Learn: Update 29.0 preview (2026 release wave 2) · Tinx: Amazon Connector for Business Central · Tinx: Adobe Commerce Connector for Business Central · Suite Engine: Channel Sales Manager pricing · Adobe Commerce Marketplace: Business Central Connect by i95Dev · Amazon: Selling Partner API documentation · Zoho Flow: Business Central integrations · Zoho Books API v3: introduction and limits · HubSpot App Marketplace: Microsoft Business Central app

AI agent access

Dynamics 365 BC and AI assistants (MCP)

Official MCP server: available. Microsoft's official remote server has been generally available since update 28.0 (2026 release wave 1); Business Central online only; read-only by default until admins enable writes.

Besides syncing Dynamics 365 BC with your other systems, we can give Claude, ChatGPT or Microsoft Copilot controlled access to it through an MCP server: read-only tools first, write actions with approval steps, and every call logged.

Status checked September 26, 2026.

Microsoft Dynamics 365 Business Central integration FAQs

Which Business Central APIs do you use, and when do we need a custom API?

We start with the REST API v2.0, which Microsoft calls the preferred way to integrate and enables by default online: customers, vendors, items, sales quotes, orders, invoices and credit memos, purchase invoices, journals, ledger entries and dimensions. Standard APIs cannot be extended with extra fields, so a missing field or table becomes a custom API page in AL under your own publisher, group and version, or an API query for read-only joins. OData V4 still exposes pages, queries and codeunits, but SOAP is deprecated and Microsoft pages lose SOAP exposure in version 29.0 and OData exposure in version 30.0, so new work goes on the REST APIs.

What is the difference between Essentials, Premium and on-premises for an integration?

Essentials and Premium expose the same APIs, environments, connectors and rate limits; the edition changes what users can do inside the product, not what an integration can reach. Microsoft lists Essentials at $80 and Premium at $110 per user per month, paid yearly, and Team Members at $8 (Microsoft list price, Sep 2026). Both include one production and three sandbox environments, the preinstalled Shopify Connector, Copilot and the official MCP server. On-premises has the same API v2.0 and custom AL APIs once an administrator enables OData and API services on the server, but no Shopify Connector, no Copilot and no official MCP server.

How do you authenticate, and does the integration need a Business Central user license?

Business Central online accepts only OAuth 2.0 through Microsoft Entra ID; web service access keys (basic authentication) stopped working online on October 1, 2022. Unattended syncs use service-to-service authentication: an Entra app registration with the API.ReadWrite.All application permission, entered on the Microsoft Entra applications page in Business Central with only the permission sets it needs, since applications cannot hold SUPER. Microsoft’s comparison table states that service-to-service integrations need no user license. Actions that must run as a person, such as approvals, use the authorization code flow so Conditional Access and MFA apply.

Does Business Central limit API calls, and how do webhooks work?

Yes. Online, each user or service principal may submit 6,000 OData or API requests in a five-minute sliding window and run five at a time; beyond that Business Central returns HTTP 429, and a request that waits or runs longer than eight minutes fails. Microsoft advises retry with back-off, $batch (up to 100 operations), $filter on lastModifiedDateTime, $expand, deep inserts and webhooks instead of polling. Webhook subscriptions expire after three days unless renewed with a PATCH, notifications are delayed about 30 seconds, more than 1,000 changes in that window arrive as one collection notification, and failed deliveries are retried for 36 hours only after a 408, 429 or 5xx. We queue calls, renew subscriptions and add a scheduled delta check.

How do I integrate Magento (Adobe Commerce) with Business Central?

Microsoft ships no Adobe Commerce connector, so there are three routes. Marketplace connectors: Tinx’s Adobe Commerce Connector on Microsoft Marketplace syncs products, stock, customers, orders and tracking; Suite Engine’s Channel Sales Manager (CSM) on AppSource covers Magento and Adobe Commerce alongside Amazon, Shopify, BigCommerce, Walmart and WooCommerce from $250 per month for CSM Core plus modules (vendor list price, Sep 2026); i95Dev lists Dynamics 365 Business Central Connect on the Adobe Commerce Marketplace. Power Automate or Logic Apps suit low volumes. A custom build on Adobe Commerce’s own API and Business Central API v2.0 fits multi-store setups, B2B pricing, bundles and custom AL fields.

How do I integrate Amazon with Business Central?

There is no Microsoft connector for Amazon either. Tinx’s Amazon Connector on Microsoft Marketplace syncs FBA and FBM orders, stock, settlements, fees and reimbursements, tracking and returns on a fixed monthly subscription per Amazon region and Business Central company (fee not published). Suite Engine’s CSM adds Amazon listing and financial management modules at $200 per month each on top of CSM Core (vendor list price, Sep 2026). A custom build uses Amazon’s Selling Partner API (SP-API), which serves sellers and vendors, with Business Central API v2.0, and fits companies that reconcile settlements to the cent, sell in several marketplaces or need FBA stock in Business Central by location.

How does a Business Central HubSpot integration work?

HubSpot publishes its own Microsoft Business Central app on the HubSpot App Marketplace: a two-way sync of Business Central customers, items, opportunities and sales orders with HubSpot contacts, products, deals and orders. The listing notes it currently syncs with contacts, not companies, and that custom field mappings need a Data Hub Starter or Professional plan; for a small sales team that is often enough. Companies that sell to companies, need closed-won deals turned into Business Central sales orders with lines, or want posted invoices and overdue balances on the HubSpot company record usually need a custom sync, which our Business Central and HubSpot page covers.

Which CRM integrates best with Business Central, and do you work as a CRM integration consultant?

If you run Dynamics 365 Sales, start with Microsoft’s built-in integration through Dataverse: it couples customers with accounts, items and resources with products, customer price groups with price lists, opportunities, posted sales invoices and sales orders, and runs its synchronization jobs from the job queue every 30 minutes by default, with optional bidirectional sales orders. HubSpot has HubSpot’s own app plus custom options; Salesforce and Zoho CRM are custom or iPaaS builds. AIONDATA is an independent consultancy, not a Microsoft partner: we map fields, ownership and match keys in a workshop, configure the native integration where it fits, build the rest and work alongside your Business Central partner.

Can Business Central be integrated with Zoho Books?

Yes. Zoho Flow, Zoho’s own automation service, has a Microsoft Dynamics 365 Business Central connector with a record created or updated trigger and create, update and fetch record actions, and connects it to Zoho Books among 1,000+ apps; that covers one-way pushes such as a Business Central invoice creating a Zoho Books invoice. A two-way sync of customers, invoices, bills and payments with reconciliation is built on the Zoho Books API v3 (OAuth 2.0, regional data centers such as .com, .eu and .in, 100 requests per minute per organization plus a daily quota by plan) and Business Central API v2.0. Nordic tenants: environments localized for Sweden and Norway are hosted in the Sweden and Norway Azure geographies, Danish and Finnish ones in Europe.

Do we need a separate license for Copilot in Business Central?

Not for the assistive features: Microsoft states that Copilot in Business Central is included with your license at no extra cost and needs no minimum number of users, while noting that fair-use policies, quotas or pricing might be introduced later. Copilot is online only. Agents are billed differently: the Payables Agent, Sales Order Agent, Expense Agent (preview) and the designing and coding agents (preview) consume Copilot Credits from prepaid packs or pay-as-you-go through an Azure subscription linked to the environment’s Power Platform environment; Microsoft’s example puts 100 Sales Order Agent requests a month at about 1,650 credits. Depending on hosting, an admin may also have to allow data movement across geographies on the Copilot & agent capabilities page.

Can AI agents such as Claude, ChatGPT or Copilot use Business Central?

Yes. Microsoft’s Business Central MCP server has been generally available since update 28.0 (2026 release wave 1) for Business Central online. Clients connect to https://mcp.businesscentral.dynamics.com, pick the tenant, environment and company through HTTP headers, sign in with Microsoft Entra ID using OAuth 2.0 with PKCE and act under that user’s permissions. The server is read-only by default; writes need an MCP Server Configuration with Unblock Edit Tools on and create, modify, delete or bound actions allowed per page. Visual Studio Code and Copilot Studio use a preregistered app; Claude, ChatGPT and other hosts need your own Entra app registration. On-premises has no official server, so there we build a custom MCP server over its APIs. Our Business Central MCP server guide, linked in the AI assistants section of this page, covers setup and options.

What does a Business Central integration cost, and how long does it take?

Cost follows the number of flows and directions, the custom AL work the mapping needs and how strict reconciliation must be. Service-to-service access needs no extra Business Central user license, and Essentials and Premium include three sandboxes for testing. Marketplace connectors are subscriptions, for example Suite Engine’s CSM Core at $250 per month plus modules and Tinx’s connectors on a fixed monthly fee (vendor list prices, Sep 2026); Power Automate needs its Premium connector licensing. A standard sync of customers, items, orders and invoices usually takes a few weeks including sandbox testing; multi-company environments, custom AL extensions and marketplace settlement reconciliation typically take two to three months. You get a written scope after a short discovery.

Need Microsoft Dynamics 365 Business Central connected to something?

The enquiry form is at the top of this page. Tell us the other system and what needs to flow between them.

Go to the enquiry form