So we are setting up an integration with an external system to bring data into a journal in BC; we will send a call to the external system to bring in the data. After talking with a developer he mentioned that an integration table also needs to be set up on Business Central whereby Application ID and client secret needs to be registered for the external system. I mentioned isn't that normally set up in Azure but he mentioned that's only if you're sending data from an external system into Business Central not the other way round (api connection). So that left me somewhat confused. Surely there can be a quicker/better way of setting up an integration setup (to register the app ID and secret) when you are doing a pull of data rather than a push of data.
For a pull integration, think of it this way: Business Central is the client, and the external system is the server. So BC does not need a standard “BC application account” setup unless the external system will call into BC APIs. If BC is calling the external API, then you only need to store/configure whatever that external API requires: endpoint URL, client ID, client secret/API key, token URL, company mapping, journal template/batch, etc. This is usually done in a custom Integration Setup table/page in BC, not because Microsoft requires a special integration table, but because your extension needs somewhere to keep the connection settings. The app registration/client secret may still exist, but it belongs to the external system’s authentication flow, not necessarily to Business Central/Entra ID. For sensitive values, avoid hardcoding and use proper secret handling such as SecretText / secure storage approach.
Regards,
Oussama Sabbouh
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
297
Share
Report
All responses (
Answers (
