Dynamics 365 Business Central Integration Developer

Ekloud Data Labs; Bengaluru; Hybrid; INR 900,000 - 1,500,000; Full time

Job summary

Ekloud Data Labs in Bengaluru seeks a hands-on developer who can write AL for Business Central and build Azure-based data integrations. You will design and implement end-to-end flows connecting Business Central with external partners, banks, logistics providers, and e-commerce platforms using Azure Functions, Logic Apps, Service Bus, API Management and Storage.

You will join a squad on a large Business Central modernization programme, replacing a legacy ERP and integration layer, with multiple

Qualifications

• Six or more years across Dynamics NAV and Business Central, at least three on BC SaaS writing AL in VS Code.
• Fluent with BC data model: tables, pages, codeunits, enums, interfaces, permission sets, deployment lifecycle.

Responsibilities

• Build integration flows end to end between Business Central and Azure services.
• Develop AL extensions to create/update/post BC documents from inbound data and extract data for outbound interfaces.

Skills

Business Central development

Azure integration services

AL extensions in VSCode

API design and integration

Telemetry and monitoring

Code testing

Azure DevOps

Data mapping

Performance tuning

Tools

Azure Functions

Logic Apps

Service Bus

API Management

Azure Storage

Azure Key Vault

Key/identity management (Entra ID)

Data Factory

Application Insights

AL-Go

Bicep/ARM/Terraform

Job description

This is a hands‑on build role for a developer who is genuinely strong in both halves of the job: writing well‑structured AL inside Business Central, and building the Azure services that carry data in and out of it.

You will design and build integrations between Business Central and the systems around it - external partners, banks, logistics providers, e-commerce platforms and other line‑of‑business applications - using Azure Functions, Logic Apps, Service Bus, API Management and Azure storage. You will own flows end‑to‑end: the AL that creates and posts documents, the Azure components that move and transform data, and the error handling, telemetry, and replay that keep it supportable in production.

You will join a squad on a large Business Central programme to replace a legacy ERP and its integration layer, with several external interfaces to build and put live, and further work of the same kind to follow across the practice.

What you will be doing

Day to day, you will:

• Build integration flows end to end - Business Central extensions on one side, Azure integration services on the other - from a written design and field mapping.
• Develop AL extensions that create, update and post Business Central documents from inbound data, and extract data for outbound interfaces, without modifying the base application.
• Build and expose APIs: Business Central API pages and custom APIs, and Azure‑side endpoints fronted where appropriate by API Management.
• Design the resilience: idempotency and duplicate detection, retry with backoff, dead‑lettering, quarantine, and controlled replay once the underlying problem is fixed.
• Externalise mapping and code‑conversion tables so business users maintain them without a code change.
• Instrument everything - Application Insights telemetry, correlation identifiers threaded from source message to posted document - so a production failure can be diagnosed without a debugger.
• Write AL test code units covering the awkward cases as well as the happy path, then support system integration testing, UAT, cutover and hypercare.

What you will bring

• Business Central development
• Six or more years across Dynamics NAV and Business Central, at least three of them on Business Central SaaS writing AL in Visual Studio Code.
• Fluent across the object model - tables and table extensions, pages, codeunits, enums, interfaces, permission sets, install and upgrade codeunits - and disciplined about extending through events and subscribers rather than touching the base app.
• Business Central API pages, custom API objects, OData v4, SOAP web services and webhook subscriptions, plus outbound HttpClient calls with OAuth 2.0, retry and timeout handling.
• Job queue entries and background sessions for scheduled and batch processing, including how to keep long‑running work inside platform limits and make it restartable.
• XML and JSON handling in AL - XmlDocument and namespace resolution, JsonObject and JsonToken - and parsing or generating fixed‑width and delimited files.
• A real working knowledge of the data model you integrate into: sales and purchase documents and their posted counterparts, posting through the standard codeunits rather than writing ledger entries, inventory and warehousing, transfer orders, item tracking including programmatic serial and lot capture, and the payment journal and bank export framework.
• Performance under volume: appropriate keys, SetLoadFields, set‑based operations and an understanding of what locking does to a batch.
• Extension packaging and lifecycle - per‑tenant extensions, versioning, dependencies, app signing, and deployment across sandbox and production environments.
• Azure integration services
• Azure Functions as integration compute - HTTP, timer and queue triggers, durable patterns for longer orchestrations, and sensible configuration and scaling.
• Azure Logic Apps for orchestration and connector‑based workflow, and knowing when a Function is the better answer.
• Azure Service Bus queues and topics: sessions, dead‑letter queues, at‑least‑once delivery and the deduplication that has to sit alongside it.
• Azure API Management for exposing and protecting APIs - policies, throttling, subscription keys and versioning.
• Azure Storage - Blob, File Share and Data Lake - for file‑based exchange, archiving and replay, with a clear folder and retention model.
• Azure Key Vault for secrets and certificates, and Microsoft Entra ID app registrations, service principals, managed identities and the OAuth 2.0 client credentials flow.
• Event Grid and event‑driven triggering, and Azure Data Factory where bulk or scheduled data movement is the right tool.
• Application Insights and Log Analytics: custom telemetry, correlating a message across components, and alerts that fire before the business notices.
• Enough judgement to choose between these rather than reaching for the same one every time, and to explain the choice to an architect.

Engineering practice

• Git and Azure DevOps - clean branching, reviewed pull requests, and CI/CD for AL extensions using AL-Go, Azure Pipelines or similar.
• Infrastructure as code for the Azure side (Bicep, ARM or Terraform), and AL test codeunits that you actually write.
• Working from a written design and mapping specification, and raising a gap as a question rather than filling it with an assumption.
• Clear written and spoken English - you will talk directly to client architects, business users and third parties.

Nice to have

• EDI experience - X12 or EDIFACT - or work with an enterprise B2B broker such as IBM Sterling B2B Integrator.
• ISO 20022 or other structured payment file generation, particularly through a bank certification.
• A Dynamics GP, AX or NAV to Business Central migration behind you.
• Third‑party logistics, warehouse management or e‑commerce integration.
• Power Platform and Dataverse, including virtual tables over Business Central. MB-820 or MB-800 certification.