Slides from the presentation on Integration Downunder discussing Logic Apps x Microsoft Flow, when to choose each technology.

1. Sponsored by
Logic App x
Microsoft Flow
Which one should I choose
Wagner Silveira
@wsilveiraNZ

2. About me • Principal Integration Architect
• Microsoft Azure MVP
• MCA Cloud Platform
• ACSUG co-organizer
wsilveiranz
wagner.silveira@notetoself.tech
https://notetoself.tech

3. Agenda
• Getting Started
• Logic Apps
• Microsoft Flow
• Comparing the offers
• Million Dollar Question
• Summary
• To Know More

4. Getting Started

5. Azure Logic Apps
Automate workflows and orchestrate business
processes easily
• Out-of-the-box connectors reduce
integration challenges
• Connect and integrate data from the cloud
to on-premises
• B2B and enterprise messaging in the cloud
• Powerful web-based workflow designer

6. Logic Apps Details
• Pricing
• No free tier
• Micro billing based on actions
• Subscription based on dedicated
offer (ISE)
• Cloud and Hybrid Model
• On-premises data Gateway
• VNET Integration (ISE)
• Extensibility
• Custom Connectors
• Implementation model
• Web based
• IDE (Visual Studio, VS Code)
• Monitoring
• Single (Portal)
• Aggregated (Log Analytics)
• Governance
• Based on Azure model
• Access control
• Based on Azure RBAC

7. Integration Services Environment
• Dedicated Model
• Isolated Workload
• Monthly subscription
• VNET integration
• Aimed to large volumes of transactions
• Is represented as another “region” in the portal

8. Development Support
• Visual Studio – with designer support
• VS Code – no designer support – JSON autocomplete
• Deployment can be automated
• Official guidance for deployment still in progress

9. Microsoft Flow
Automate workflows and orchestrate business
processes easily
• Out-of-the-box connectors reduce office
productivity challenges
• Connect and integrate data from the cloud
to on-premises
• First party Integration and Office
productivity in the cloud
• Powerful web-based workflow designer

10. Microsoft Flow Details
• Pricing Model
• Free tier
• Office offering
• Plan tiers (1 & 2)
• Cloud and Hybrid Model
• On-premises data gateway for
selected connectors
• Extensibility
• Custom connectors
• Implementation model
• Web based
• Monitoring
• Run history
• Flow Analytics
• Governance
• Based on Office 365
• Data loss prevention policies
• Access Control
• Team Flows
• Solutions

11. Pricing
• Micro billing per execution
• Each license has an allowances on executions and polling
• Execution allowance is bubbled up to organization
• Flow Plan 1 and 2 are paid “add-ons”
• Some advanced features are only available in paid plans
• Flow Plan 1 – premium connectors
• Flow Plan 2 – Organization Policies, Business Process Flow

12. Development Support
• Browser based only
• Flows can belong to a team or individual
• Flow checker – highlight errors in flow
• Deployment is not automated – packaging between environments

13. Governance
• Microsoft Flow Analytics
• Organization Policies
• Data Loss Prevention
• User access based on Office 365 users

14. Comparing the offers

15. Things that only Logic Apps do
• IDE based development experience
• Support for Automated deployment (using ARM templates)
• Access to code for fine tuning tweaks
• Aggregated Monitoring / Alerting (via Log Analytics)
• B2B scenarios (AS2, EDIFACT integration, XML transformations)
• VNET Integration (via ISE)

16. Things only Microsoft Flow do
• Data loss prevention policy
• Advanced Business Process Flows
• Rich integration with Office 365 (embedded in the tooling)

17. The million dollar question:
Which one should I choose?

18. How about both?
• Both technologies can compliment
each other
• The final answer depends on:
• Environment
• Needs
• Team
• Topology

19. Choose Logic Apps when:
• Workflows are part of a larger solution involving other Azure
resources
• Solution requires source control and CI/CD
• Fine grained control over my code (access to code behind)
• Need closer to real time triggering for polling
• Monitoring and alerting is more complex, requires aggregation and
correlation
• Solution requires EDI or XML validation & transformation
• Solutions requiring VNET integration

20. Choose Microsoft Flow when
• Your solution do not require an Azure subscription
• You need to create personal workflows
• Your solution is the backend of a Power App
• Your organization have D365 of Office 365 active subscription and
requires 1st party app automation
• You have a non-dev background but need organizational workflows
• My solution is not part of a bigger Azure solution
• My management/monitoring are simple

21. In summary…
• Don’t feel pressured to choose
just one technology
• Identify the places where each
technology will help you the
most
• When it doesn’t make a
difference, use the one you feel
more comfortable
• Mix and match is ok

22. To know more…
• Microsoft Flow Pricing - https://flow.microsoft.com/en-us/pricing/
• Integration Services Environment - https://azure.microsoft.com/en-
us/blog/announcing-azure-integration-service-environment-for-logic-
apps/
• Logic Apps x Microsoft Flow Which one should I choose? -
https://notetoself.tech/2018/04/08/logic-apps-x-microsoft-flow-
which-one-should-i-choose/
• Logic Apps x Microsoft Flow – why not both? -
https://www.serverless360.com/blog/azure-logic-apps-vs-microsoft-
flow