In my last post about serverless architectures for decoupling integrations between Dynamics 365 Business Central and external applications, I’ve talked about the usage of queues and Azure Functions for exchanging messages between different cloud applications.
One of the quite common and simplest schema presented in the post was the following:
In this schema there’s a Timer Trigger…
Continue Reading demiliani’s Article on their blog
Timer Trigger Azure Functions: handling retry policies
In my last post about serverless architectures for decoupling integrations between Dynamics 365 Business Central and external applications, I’ve talked about the usage of queues and Azure Functions for exchanging messages between different cloud applications. One of the quite common and simplest schema presented in the post was the following: In this schema there’s a…
Blog Syndicated with demiliani’s Permission
More About This Author
Array
Business Central15 April 2024Dynamics 365 Business Central 2024 Wave 2 release plans: “as is” and “to be”
Business Central10 April 2024Dynamics 365 Business Central and Shopify connection: access key rotation.
Business Central10 April 2024Azure Functions: .NET 7 support is ending and you should upgrade to .NET 8.
Business Central4 April 2024Dynamics 365 Business Central 2024 Wave 1 release: important server changes to remember.
