Eshop integration with Microsoft Dynamics 365 Business Central: workflows, prerequisites and testing

Integrate the store with Microsoft Dynamics 365 Business Central around a defined workflow and the installation's available interface. Business Central requires explicit environment and company selection before any business data is read or written. Map customer, item and sales-order lines, retaining confirmed IDs rather than matching vague names.

Business Central requires explicit environment and company selection before any business data is read or written. Map customer, item and sales-order lines, retaining confirmed IDs rather than matching vague names. Unattended access uses an Entra application and restricted permission sets. We recommend a separate integration identity so that an employee leaving does not disable the store connection. Deliver the credential-change and permission-approval procedure together with the implementation.

Microsoft provides salesOrder resources and guidance for unattended access using OAuth client credentials. An Entra app registration and access granted within Business Central are required. The application receives appropriate permission sets rather than SUPER. Business Central differs from Dynamics 365 Sales or Finance. On-premise requires appropriate Entra/OIDC configuration and confirmation that the APIs are enabled.

An importer has two companies in Business Central, but the online store belongs to one. Bind the company ID to that integration and check it before creating a sales order. The connector links the customer and items using actual IDs in the destination company. If permissions allow reading but not writing, the order remains pending with a clear reason. Test credential replacement so that scheduled access maintenance does not require manual duplicate entry.

An important failure scenario occurs when the application permissions allow reading but not creating sales orders. Keep the external reference and confirmed destination ID before retrying. Separate access failure, business rejection and an unknown outcome. An operator must be able to inspect the relevant record and resolve its status without replaying completed steps. Agree which fields may appear in logs and who handles unresolved cases.

Test restricted access, the correct company, and credential renewal without interruption. For each case record the expected source data, destination record and customer-visible state. Include one denied-permission case and one interrupted response. Re-run a previously confirmed event and check that its business effect is unchanged. The acceptance record should identify the responsible team and the evidence required to close any discrepancy.

The initial discovery should confirm: Entra app registration and consent; Enabled Business Central application with least privilege; Environment/company IDs and test data. Before launch, document the mapping for OAuth application → authorised API → Correct company → customer/item mapping → Sales order → stored confirmed ID. Assign responsibility for access renewal, monitoring and correction. A change to product configuration or the agreed business rule should trigger targeted regression checks. Begin with this defined workflow; add another channel only after its ownership and acceptance cases are clear.