After writing a lot about Microsoft Flow (see References), it’s time to move on with his older brother: Azure Logic Apps. To get an idea of the relationship between the two products, it’s best to start with
Microsoft Flow is built on the features and architecture provided by Azure Logic Apps.
Both tools give us the ability to define processes using a visual designer, they have hundreds of connectors for Microsoft tools and 3rd party services. And these processes are started by a trigger. The main advantage behind Microsoft Flow and Logic Apps is that complex processes can be approached quickly and simply.
Another important point is that there are many templates that solve the most common problems that we can find. And, we also have the option to use a template as a starting point for solving a problem.
If we get formal, both platforms would be part of
IPaaS, Integration Platform as a Service
Note: If with IaaS, PaaS and Saas you had no enough, then take IPaas!
Now, I return to the post title question; What is the difference between Microsoft Flow and Logic Apps? The following table of LogicApps’s official documentation explains it very clearly
Well, now that we’ve seen that Logic Apps is Microsoft Flow on steroids, it’s time to start writing posts explaining a little more about advanced scenarios that we can implement with logic apps. Logic apps focuses on it role-oriented, mission-driven scenarios Criticizes and also supports advanced features like editing the code of a process.
This also guarantees that we will be able to define a development life cycle for the Logic Apps (ALM rules!) processes. And finally we will be able to integrate and use Azure services like Azure Security or azure Logs in our Logic Apps processes.
Greetings @ Toronto
My posts on Flow
- Check your Apps health in Azure using Application Insights and Microsoft Flow
How To iterate through collections of elements (Excel, Sharepoint, Cognitive Services and more…)Trigger a Flow associated to an item in a #SharePoint list
- New input options when using Flow Button: list of choices
- Working with Expressions
- Export and Import Flow definitions with advanced options
- How To emulate a Button for a Flow using a Browser
- Advanced options to work with an HTTP Action in Microsoft Flow, Headers, Authentication and more
- Working with Variables in Microsoft Flow
- Handle exceptions, errors, timeouts and more in a Microsoft Flow definition
- Buttons Widgets in iOS and Android
- New action definition to use Computer Vision APIs from Microsoft Cognitive Services
- Schedule a Flow execution, recurrence supported!
- “Save as ” and interaction with physical buttons FLIC and BTTN
- Email Sentiment Analysis on a PowerBI dashboard, and Flow
- Support for Team coauthoring and sharing
- Calling a Flow from a C# ConsoleApp
- Push Notification Support
- How to review a Flow process
- How to invoke a Flow from an external app using HTTP Request