This document summarizes a presentation about Azure Logic Apps. It introduces Logic Apps as a configuration-first integration platform that allows automating business processes and integrating cloud and on-premises systems through a no-code designer or code view. It describes built-in API connectors, when to use Azure Functions instead, and compares Logic Apps to Microsoft Flow. The document also provides examples of using Logic Apps with cognitive services and best practices for Logic App development.

1. Azure Logic Apps The new workflow engine
David Schneider @fiddi
SharePoint Saturday Zurich 26.5.2018
@Kraftwert Impact Hub Zurich

2. Thanks to our Sponsors <3

3. About me
• David Schneider
• isolutions (CTO & Barcelona)
• MVP for Office Server and Services
• https://twitter.com/fiddi
• https://www.linkedin.com/in/david-schneider
• https://www.davidschneider.blog
• https://www.sharepointcommunity.ch

4. Azure Logic Apps
• Configuration-first integration
services
• Integration Platform as a Service
(IPaaS)
• Automate business processes
• Integrate Cloud and on-premises
systems
• No code designer for rapid
creation but also a code view for
developers
• Use with custom API apps of your
own

5. Trigger …
if, switch, loop …
… and actions.

6. Built-In API Connectors
• 200+ Connectors with different Triggers
and Actions
• Standard Connectors to Microsoft and
3rd Party Cloud Services
• On-Premises Connectors (using on-
premises data gateway)
• Enterprise and Integration Connectors
• Custom Connectors (REST-based API)

7. For everthing else
Azure Functions
• Serverless functions in
C#, F#, JavaScript,
etc.
• Implement code-
based microservices
• Different trigger, input
and output bindings
• Synchronous and
asynchronous
execution
Azure Service Bus
• Message based
integration of
applications
• Decoupling of
applications
• Protection against
service failure
API Apps
• Use Swagger
framework
• Hosted on Azure or
elsewhere
• Simple
authentication
• Bring in existing APIs
written with .NET,
PHP, Node.js, Java or
Python

8. Demo:
Convert Document to PDF

9. Logic Apps vs. Flow
Platform as a Service Software as a Service

10. Limits
Logic Apps Flow
Run Duration 90 Days 30 Days
Minimum recurrence interval 1 Second 1 Minute
Maximum recurrence interval 500 Days 500 Days
ForEach Items 100’000 5’000
ForEach Parallelism 50 1
Message Size 100 MB 100 MB
Allowed action nesting depth 8 5
More Details Logic Apps Limits Flow Limits

11. Where is Flow better?
Logic Apps
• No overview of approvals.
Expect your Inbox.
• Start Logic App using triggers
only («When a File / Item is
Created, Updated or Deleted»)
Flow
• List of all pending and
requested approvals
• Triggers and User Interaction
can start a Flow

12. Start a Logic App from Flow
Flow Action: HTTP Request Logic App Trigger: HTTP Request

13. Demo:
Start a Logic App from Flow

14. Application Lifecycle Management
• Build in Visual Studio
• Visual Studio 2015/2017 Community Edition (or greater)
• Azure SDK and Azure PowerShell
• Azure Logic Apps Tools for Visual Studio 2015/2017
• Deploy as Azure Resource Manager Template
• Release Management in Visual Studio Team Services
• Monitor using Azure Capabilities
• Azure Monitor, Azure Operation Management Suite, etc.

15. Demo:
Build and Deploy a Logic App like a Pro

16. Cognitive Services
• Easy to Interact with Cognitive Services
• Text Analytics, LUIS
• Computer Vision, Custom Vision, Face API
• Content Moderator
• Video Indexer
• Bing Search

17. Demo:
Not Bacon

18. Pricing
CHF 0.000023 per Actions
CHF 0.000113 per Connector Execution
Additional Cost for Enterprise Connectors and
Integration Accounts
Price Calculator:
https://azure.microsoft.com/en-
us/pricing/calculator/?service=logic-apps
Cost per Month
Poll data once every minute ≈ 43’000 Billable Connector Executions
500 workflow steps per day ≈ 15’000 Billable Actions
≈ 4.20 CHF

19. Best Practices
Create Logic App in Visual Studio 2017 using Visual Designer or
JSON
Use “Build & Release” to deploy the ARM templates from Git
Repo to Azure
Prefer Webhooks over polling
Use Azure Service Bus to queue requests
Establish monitoring (Alert Rules, OMS, Application Insights, etc.)

20. Evaluation Form
http://mvp.ms/SPSZurich2018
This survey is anonymous, but you can voluntarily enter your
name and email address for a chance to win a license of Nintex
Workflow Cloud.
Consent is necessary to participate to the lottery.

21. Thank you for attending!