Secure Business Central integrations with clear ownership and recovery
Diesen Beitrag auf Deutsch lesen
Design Business Central integrations with supported interfaces, least privilege, safe retries, monitoring, and explicit ownership.
TL;DR
Business Central integrations should use supported APIs, least-privilege access, managed secrets, bounded retries, correlation identifiers, and defined recovery paths. Direct links suit small flows, while middleware or queues help coordinate multiple systems or asynchronous work. SOAP is deprecated, and Microsoft-owned pages will no longer be exposable as OData endpoints starting in version 30.0.
Original by Softchief Author, on Softchief Technologies. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Match each interface to the data, timing, and support needs, because direct links can become tightly coupled as systems grow.
- Admins/CoE: Assign only the Business Central permissions required, store secrets in a managed secret store, and monitor failures, retries, queues, and authentication events.
- Security/Compliance: Keep exposed data and logs limited, avoid recording tokens or sensitive payloads, encrypt transport, and define retention periods.
- Leadership/Business: Require clear ownership for records, transformations, schemas, and recovery before expanding beyond a bounded integration flow.
Frequently asked questions
How should Business Central integrations handle SOAP and OData deprecation?
Use supported APIs for new designs. Retain SOAP only for compatibility needs and plan migration, while Microsoft-owned OData pages require a supported replacement.
What authentication model does Business Central support for unattended service integrations?
Business Central supports OAuth 2.0 client credentials through Microsoft Entra ID for applications running without a signed-in user.
How can queued Business Central messages prevent duplicate business outcomes?
Design for duplicate delivery by using an idempotency key or equivalent detection, then provide dead-letter handling and a safe manual recovery path.