Downloaded 18 times
Uploaded byAzure Riyadh User Group
Azure Logic Apps
This document discusses Azure Logic Apps, which allow users to automate workflows and integrate apps, data, and systems. It provides an overview of what Logic Apps are, how they work using connectors and triggers, and when they should be used compared to Microsoft Flow. The presentation includes demonstrations of creating a Logic App and using connectors and triggers to automate tasks and integrate services.
More Related Content
![[164] pinpoint](https://cdn.slidesharecdn.com/ss_thumbnails/164pinpoint-150914054628-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
![[AWS Builders] AWS 네트워크 서비스 소개 및 사용 방법 - 김기현, AWS 솔루션즈 아키텍트](https://cdn.slidesharecdn.com/ss_thumbnails/1network-191112092246-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Azure Logic Apps
Azure Logic Apps
- 1. Wael ElKadim Build automatedworkflows with Azure Logic Apps Senior Customer Engineer 09:00 pm Riyadh Time 08:00 pm Cairo Time Sunday ,19-07-2020
- 2. Agenda Azure Integration Services What is Azure LogicApps? How Logic Apps works? When to use Logic Apps? What is Microsoft Flow? Microsoft Azure Logic Apps vs. Microsoft Flow
- 3.
- 4. Continuous Integration This Photoby Unknown Author is licensed under CC BY-NC-ND This Photo by Unknown Author is licensed under CC BY-SA
- 5. Integration Is Simple •Flow • Protocol • Message • Security • Exception Handling • Logging and Monitoring
- 6. Service Bus Logic AppsAPI Management Event Grid Azure Integration Services
- 7. Logic Apps • Cloudservice • Automates the execution of your business processes. This Photo by Unknown Author is licensed under CC BY-SA
- 8.
- 9. Logic Apps simplifieshow you design and build scalable solutions for • Applications integration • Data integration • System integration • Enterprise application integration (EAI) • Business-to-business (B2B) communication
- 10. For simple andcomplex integration
- 11.
- 12. How Logic Appsworks Connectors Execution Environment Security Monitoring Pricing Model Limitations
- 13.
- 14. The Age ofConnectors • Proxy or a wrapper around an API • REST or SOAP API to do its work.
- 15.
- 16. Components of aConnector Actions • Changes directed by a user. • All actions directly map to operations defined in the Swagger Triggers • Notify your app when specific events occur. • Polling Triggers • Push Triggers
- 17.
- 18. Dropbox and TwilioConnectors
- 19. How to buildLogic Apps from triggers and actions • Begin with a trigger • Include as many actions as you need to implement your workflow
- 20. How do triggersand actions work together? • Return values available throughout the rest of the operations. • Pass the results from one operation as input to the next operation
- 21. What are controlactions? • Condition statements controlled by a Boolean expression • Switch statements • For each and Until loops • Unconditional Branch instructions.
- 22.
- 23.
- 24. Recurrence trigger • Runs ona specified schedule . • Not associated with a particular service or system.
- 25. Polling trigger 1. Polls aspecific service or system based on the specified schedule. 2. Checking for new data or whether a specific event happened 3. Creates and runs a new instance of your logic app
- 26. Push trigger 1. Waitsand listens for new data or for an event to happen 2. Creates and runs new instance of your logic app
- 27.
- 28. Alter control flow usinga control action Condition action Switch action Foreach loop Until loop
- 29. Types and operators Numeric •is-equal-to • is-not-equal-to • is-greater-than • is-greater-than- or-equal-to • is-less-than • is-less-than-or- equal-to String • is-equal-to • is-not-equal-to • Contains • does-not-contain • starts-with • does-not-start- with • ends-with • does-not-end- with Boolean • is-equal-to • is-not-equal-to JSON objects • is-equal-to • is-not-equal-to
- 30.
- 31.
- 32. When to useLogic Apps Integration Performance Conditionals Connectors
- 33. Integration Do I needto integrate services? Building an app with no external connections
- 34. Performance Execution engine scales yourapps automatically. Can process large data- sets in parallel to let you achieve high throughput Don't guarantee super- fast activation. Don’t enforce real-time constraints on execution time
- 35. Conditionals Can build highly complexand deeply nested conditionals into your Logic Apps. It's often easier to write conditional logic in code. Embedded business rules aren't easily sharable with your other apps.
- 36. Connectors There are pre-built connectorsfor all the services you need to access. Need to create a custom connector Need to create the API first before making the connector
- 37.
- 38. Microsoft Flow (PowerAutomate) • Software as a Service (SaaS), for automating workflow across number of apps and SaaS Services. • Use Connectors.
- 39. Microsoft Flow vsLogic Apps Microsoft Flow Logic Apps • Business User • Citizen Developer/Integrator • Developers • It Pros • Developers • IT Pros Automating Workflow Extending Microsoft Workflow Simple Integration Extend/Advanced Integration
Editor's Notes
- #11 Azure Logic Apps is a cloud service that helps you schedule, automate, and orchestrate tasks, business processes, and workflows when you need to integrate apps, data, systems, and services across enterprises or organizations. Logic Apps simplifies how you design and build scalable solutions for app integration, data integration, system integration, enterprise application integration (EAI), and business-to-business (B2B) communication, whether in the cloud, on premises, or both.
- #18 https://docs.microsoft.com/en-us/Connectors/connector-reference/
- #19 Actions Actions are changes directed by a user. For example, you would use an action to look up, write, update, or delete data in a SQL database. All actions directly map to operations defined in the Swagger. Several connectors provide triggers that can notify your app when specific events occur. For example, the FTP connector has the OnUpdatedFile trigger. You can build either a Logic App or a flow that listens to this trigger and performs an action whenever the trigger fires. There are two types of triggers. Polling Triggers: These triggers call your service at a specified frequency to check for new data. When new data is available, it causes a new run of your workflow instance with the data as input. Push Triggers: These triggers listen for data on an endpoint, that is, they wait for an event to occur. The occurrence of this event causes a new run of your workflow instance.
- #22 A trigger is an event that occurs when a specific set of conditions is satisfied. Triggers activate automatically when conditions are met. For example, when a timer expires or data becomes available. An action is an operation that executes a task in your business process. Actions run when a trigger activates or another action completes.
- #38 Logic Apps provides control constructs like Boolean expressions, switch statements, and loops so your apps can make decisions based on your data. You can build highly complex and deeply nested conditionals into your Logic Apps. There are two reasons you might prefer not to. First, it's often easier to write conditional logic in code rather than using the Logic Apps Designer. Second, embedded business rules aren't easily sharable with your other apps. Some people like including complex business rules directly in their Logic Apps. Others think it's simpler to write something like an Azure Function to encapsulate the conditional logic and invoke that Function from all their apps.
- #39 The last consideration is whether there are pre-built connectors for all the services you need to access. If so, then you're ready to go. If not, then you'll need to create a custom connector. If the service has an existing REST or SOAP API, you can make the custom connector in a few hours without writing any code. If not, then you'll need to create the API first before making the connector.