10 Things in Microsoft Flow that isn’t in Azure Logic Apps

Reshared blog, here is the original one.

Sorry about the catchy headline.  I will start by saying I am perfectly ready to see a response post containing 20 things in Azure Logic Apps that we wish are in Microsoft Flow.  The point of this post isn’t about whether one product is better than another product, it is simply to highlight the very-intentional design differences and how as users we have access to both and should make our choice accordingly.

If a comparison must be made, then I think in reality, they are better seen as two siblings – LogicApps is the big sibling with more features, Flow piggybacks LogicApps, but itself has several unique tricks and sometimes, features do move between them.  I love both teams & products.

To best describe Flow to an Azure / Logic Apps person, Flow is Logic Apps + power-user / human workflow-focused workloads, combined with a mobile experience and better in-product integration.  As a result, it caters to a whole different set of scenarios that Logic Apps isn’t focused on.

1. Resource-Owned Flows

Continue reading “10 Things in Microsoft Flow that isn’t in Azure Logic Apps”

workflow execution from Plugin

Here is quick sample code for workflow execution from Plugin …

Execute workflow …

Continue reading “workflow execution from Plugin”