I’ve been getting asked by some of my clients and attendees at some of my presentations on the difference between Microsoft Flow and Microsoft Azure Logic Apps.
Both are integration tools that have configurable workflow actions which makes it easy to build your workflow processes to integrate with all of your enterprise applications.
There are some differences though.
Below is a quick summary I’ve put together on this based on the information published by Microsoft on Choosing between Flow, Logic Apps, Functions, and WebJobs.
- First thing you should know is that Flow is built on top of Logic Apps.
- Next, flow is to be used for simple workflows & integrations and more intended towards office workers & business users whereas Logic Apps are more for IT professionals & Developers. In reality, I tend to think that the IT professionals and power users will end up using flow as well.
- What’s interesting is that both Flow and Logic Apps use similar if not the same web designer screens for creating and configuring the workflows.
- Logic Apps have the additional capability of deploying and developing in Visual Studio and declarative JSON code
- Connectors (to data or services within your workflows) are interchangeable between Flow and Logic Apps.
- Logic Apps are used for advanced mission-critical integrations where as
- Logic Apps require enterprise-level DevOps security practice with the appropriate source control, testing, support, and automation and manageability where as Flow workflows are done directly in production when needed
- Logic Apps can use Azure Resource Manager templates where you can quickly you define parameters for values you want to specify when the template is deployed and have it quickly done
- Admin experience for Flow is on https://flow.microsoft.comwhereas Logic Apps use the normal Azure Portal
- From a security perspective, Logic Apps have the additional built-in Azure security capabilities like auditing
View the full article here: Choosing between Flow, Logic Apps, Functions, and WebJobs