Yaniv Arditi

Azure Function is a fantastic mechanism for various integration scenarios. Here are few key characteristics: Being a serverless application, Azure Function has the best time to market when it comes to deploying a web service Pay-per-use pricing model means you pay only for what you use Built in integration options in PowerApps and Flow allows you to give non-developers new building blocks when designing application and processes CORS (Cross-Origin Resource Sharing) support allows consuming Functions from server/client side in any domain you find suitable What can you do with Azure Functions in the context of Microsoft Dynamics integration scenarios? Just about anything: Export/Import data to/from...

While reviewing existing Microsoft Dynamics 365 Online implementations, I have noticed a repeating assumption by which Custom Workflow Activity, executing within an a-synchronous process, is not subjected to the sandbox 2 minutes execution timeout limitation. This false assumption led to wrong architectural designs in which long running processes are assigned to be handled by CWA components.  As this article states, Custom Workflow Activity code registered to work in sandbox mode is subjected to the 2 min. execution timeout limit, just like Plug-in code. If you want to test this declaration yourself, just put a Sleep statement in your...