Business Central Azure integration that runs reliably

When Business Central Azure integration is the right call

AL extensions run inside Business Central and share its resources. That is ideal for business logic. It is less ideal for converting large files, calling slow outside services or running code written in another language. Moving that work to Azure keeps the ERP responsive. It also lets each piece scale on its own.

Azure also fills gaps in connectivity. Business Central online cannot reach a file share or an FTP server on its own. It also has no place for a long-running listener. A small Azure component bridges those gaps. The ERP talks to it over standard web calls.

The Azure services we pair with Business Central

Azure Functions host small pieces of code. Business Central calls them over HTTP, or they call the Business Central APIs on a timer. Logic Apps offer a visual designer and a ready connector for Business Central. That suits document flows with partners. Blob Storage holds files such as exports, images and archived documents.

Service Bus provides queues and topics. So messages wait safely if one side is busy or offline. Key Vault keeps secrets and keys out of code, and extensions can read from an app key vault. Application Insights collects telemetry from Business Central and from the Azure parts around it.

Secure sign-in for Business Central Azure integration

Every Azure component that calls Business Central needs an identity. We register an application in Microsoft Entra ID. Then we grant it access in Business Central with a permission set limited to the tables it touches. We use OAuth service-to-service sign-in. No user password is stored anywhere, and nobody's account is borrowed.

In the other direction, we protect calls from Business Central to a Function with keys or Entra sign-in. We keep these in Key Vault or isolated storage, not in source code. We rotate secrets on a schedule. Where your security policy asks for it, we add network limits.

Integration patterns that survive failures

Networks fail and services restart. A design that assumes otherwise loses orders. So we prefer asynchronous patterns. Business Central raises a business event or writes to an outbox table. A queue carries the message. The receiver confirms once it has processed it. If anything breaks, the message waits and tries again.

Each message carries an identifier. So the receiver spots a repeat delivery and does not post it twice. Failed messages move to a dead-letter queue. There, someone can inspect and resubmit them. We also respect the Business Central API limits through batching and backoff. That prevents throttling in busy periods.

Monitoring and maintaining Business Central Azure integration

An integration that nobody watches fails silently. So we send telemetry from both sides to Application Insights. Then we build alerts for the signals that matter. Examples are messages that pile up in a queue, repeated sign-in errors and a timer that has not fired. Alerts go to a named person or mailbox, with a note on what to check.

We define Azure resources as templates in source control. A test copy can then sit beside a Business Central sandbox, and changes deploy the same way each time. We write down what each resource does. We also explain how consumption-based Azure charges arise, so the monthly bill holds no surprises.

Business Central Azure integration questions

Do we need our own Azure subscription for Business Central Azure integration?

Yes. Business Central online runs on Azure, but that setup belongs to Microsoft, and you cannot use it. Functions, Logic Apps, storage and queues for your integrations live in a subscription your company owns. That also keeps control and billing in your hands. We help you set up the subscription and name each resource so your team can find it later.

When should we use Power Automate instead of Logic Apps?

Power Automate suits flows that business users own, such as approvals and notices. Logic Apps suit system integrations that IT manages. They offer source control, staged deployment and finer control over networking. Both have a Business Central connector. We often use each where it fits, and we explain the choice in plain words.

Can Azure Functions replace AL extensions?

No. Logic that must run inside a posting routine or change how a page behaves belongs in AL. Functions complement extensions. They handle work that is awkward or slow inside the ERP. A typical solution has a thin extension and a Function that work together. That keeps each part small and easy to test.

Does Business Central Azure integration work on-premises?

It can. On-premises servers expose the same APIs. But Azure components need a network path to reach them. That usually means a gateway, a relay or a published endpoint. We look at your network first. Then we design around what your security team allows. Nothing opens to the internet without their approval.

Can Business Central data be copied to Azure for analytics?

Yes. You can export data on a schedule to a data lake or an Azure SQL database. Then you report on it from there, which takes load off the ERP. We plan which tables to include and how to detect changes. We also plan how the figures reconcile to Business Central. That way, the reports match what finance sees.

Related integration services

Azure is one route among several for connecting Business Central. These pages cover API integration, web services, Power Automate and telemetry. Together they decide how systems talk to the ERP and how you watch them. To plan a Business Central Azure integration, use the contact page and describe the systems you want to link. For the product detail, see Business Central documentation on Microsoft Learn.