Secure authentication between Azure Logic App and Function Apps has been possible for a while. What's less clear is whether we can automate the setup of this as part of an Azure Resource template deployment. So, that leaves us with only one option - let's find out!
It's relatively rare that you will find differences between what's available in Power Automate flows and Logic Apps. The Common Data Service is perhaps the exception to this rule, as its missing some options to allow you to define which attribute data to return from your instance...
Azure API Management and resource manager templates are not natural bedfellows, as I recently discovered. Although it's possible to get them working alongside each other, there is a bit of trial and error involved. That's why I thought I'd share my recent experiences working with them both.
A few weeks ago, I did a post on the process involved when migrating Microsoft Azure Cloud Solutions Provider (CSP) subscriptions across tenants. Having done some actual work relating to this since then (shock horror!), I thought I'd follow up with a new post, sharing some additional thoughts and lessons learned.
Migrating across from Microsoft Flow to Azure Logic Apps is ridiculously easy. However, there are some critical feature differences that you must make yourself aware of. One difference relates to how triggers actions work, particularly in tandem with an Azure template.