Azure Logic Apps vs. Microsoft Flow

Which would you choose? Or should you be choosing at all?

Introduction

These days, you can’t go to a Microsoft conference where the question of “What is the difference between Microsoft Flow and Azure Logic Apps?” isn’t asked. For many people, they think the answer is binary; you need to use one or the other. While people have preferences, and perhaps even biases, it is important not to rule the other technology out, as you are likely missing out on opportunities for your organization.

You may also enjoy:  When to Use Logic Apps and Azure Functions

Personas

When Microsoft has answered the Azure Logic Apps vs. Microsoft Flow question in the past, personas generally played a role in deriving an answer. When it comes to “Power users” or even “Citizen Developers,” Microsoft Flow is generally identified as the tool of choice, in part due to it being the targeted audience for why the tool was created.

Doing Your DevOps Stuff With Azure Functions Instead of Logic Apps

So, a couple of weeks back I wrote about leveraging the power of Logic Apps to retrieve Alerts from within your Azure ecosystem and send them to Microsoft Teams. This works great and a fellow Azure MVP, Tom Kerkhove, has enhanced the Logic Apps Template when handling Azure Monitor events.

I'm starting to become a pretty big fan of Logic Apps, but there are some (obvious) downsides to it.
First, they live inside your Azure Portal. You can create, modify and export them from within the Portal, which is great, unless you want to integrate them in your "regular" development cycle.