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
Dyn365BC2023.01.31Dynamics 365 Business Central and Dynamics NAV on-premises Security Vulnerability CVE-2022-41127: how to fix- Dyn365BC2023.01.26Dynamics 365 Business Central 2023 Wave 1 release plans pillars
- Dyn365BC2023.01.25Dynamics 365 Business Central: retrieving Azure AD User informations via AL
- Dyn365BC2023.01.18Telemetry with Azure Application Insights: prevent anomalies on data ingestion
