Common scenarios, examples, tutorials, and walkthroughs for Azure Logic Apps

  • Article

Azure Logic Apps helps you orchestrate and integrate different services, systems, apps, and data by providing 1,400+ prebuilt and ready-to-use connectors for Azure services, Microsoft services, GitHub, SQL Server, SAP, Salesforce, and more. Azure Logic Apps is a "serverless" integration platform, meaning you don't need to provide your own infrastructure nor manage scaling for your application instances. You can focus your energy and effort on designing the logic for your integration solutions and building your automated workflows. The platform handles scale, availability, and performance. Azure Logic Apps is especially useful for use cases and scenarios where you need to coordinate actions across multiple systems and services.

To help you learn about the capabilities and patterns that Azure Logic Apps supports, this guide describes common starting points, examples, and scenarios.

Common starting points for logic app workflows

Every workflow starts with a trigger, which fires either on a specified schedule or when the trigger condition is met. When the trigger fires, subsequent actions run in the workflow, and pass along any trigger outputs to these actions. Many connectors provide triggers, which have either of the following types:

  • Polling trigger: Based on the specified schedule, this trigger checks an endpoint for data or an event that meets the trigger condition. If the trigger condition is met, the trigger fires, creates, and runs a new workflow instance. Any trigger outputs pass as inputs to the first action in the workflow.

  • Push trigger: This trigger waits for an event that meets the trigger condition to happen at the specified endpoint. For example, events might include , to receive a request, a message, or a file created or updated at the endpoint location. When this event happens, the trigger fires, creates, and runs a new workflow instance. Any trigger outputs pass as inputs to the first action in the workflow.

Polling trigger examples

Trigger Description More information
Recurrence trigger Set the recurrence for running your workflow, including the start date and time. For example, you can select the days of the week and times of day. - Schedule and run recurring automated tasks, processes, and workflows with Azure Logic Apps
When an email is received Check for new email from any mail provider that's supported by Azure Logic Apps, for example, Office 365 Outlook, Outlook.com, and so on. - Tutorial: Automate tasks to process emails by using Azure Logic Apps, Azure Functions, and Azure Storage
HTTP trigger Call a service endpoint over HTTP or HTTPS. Call, trigger, or nest workflows by using HTTP endpoints

Push trigger examples

Trigger Description
Request trigger Receive incoming HTTPS requests.
HTTP Webhook trigger Subscribe to a service endpoint by registering a callback URL with that service. That way, the service can just notify the trigger when the specified event happens, so that the trigger doesn't need to poll the service.

After you add the trigger, continue building your workflow by adding one or more actions. The following how-to guides help you build your first Consumption logic app workflow, which runs in global, multitenant Azure Logic Apps:

The following how-to guides help you build a Standard logic app workflow that runs in single-tenant Azure Logic Apps:

Migrate to Azure Logic Apps

Control flow and error handling capabilities

Azure Logic Apps includes rich capabilities for advanced control flow, such as conditions, switches, loops, and scopes. To ensure resilient solutions, you can also implement error and exception handling in your workflows.

Run code from your workflows

Secure your workflows

Reliability

Handle content types, conversions, and transformations

You can access, convert, and transform multiple content types by using the many functions in the Azure Logic Apps workflow definition language. For example, you can convert between a string, JSON, and XML with the @json() and @xml() workflow expressions. Azure Logic Apps preserves content types to support content transfer in a lossless manner between services.

Create custom APIs and connectors

For systems and services that don't have published connectors, you can also extend Azure Logic Apps to create custom APIs and connectors:

Build business-to-business (B2B) solutions

For enterprise integration solutions and seamless communication between organizations, you can build automated scalable workflows for these scenarios by using the Enterprise Integration Pack (EIP) with Azure Logic Apps. Although organizations use different protocols and formats, they can exchange messages electronically. The EIP transforms different formats into a format that your organizations' systems can process and supports industry-standard protocols, including AS2, X12, EDIFACT, and RosettaNet. To build these solutions, you create an integration account, which is a separate Azure resource that provides a secure, scalable, and manageable container for the artifacts that you define and use with your logic app workflows. For example, artifacts include trading partners, agreements, maps, schemas, certificates, and batch configurations.

Deploy, manage, and monitor logic app workflows

You can fully develop and deploy logic app resources with Azure DevOps or any other source control and automated build tools. To support deployment for workflows and dependent connections in a resource template, logic app resources use Azure resource deployment templates. For notification and diagnostic logs for workflow run status, Azure Logic Apps also provides monitoring and alerts.

Deploy

Manage

Monitor

Monitor Consumption workflows
Monitor Standard workflows

Other integrations and capabilities

Azure Logic Apps integrates with many services, such as Azure API Management, Azure App Service, and custom HTTP endpoints, for example, REST and SOAP.

End-to-end scenarios

Customer stories

Learn how Azure Logic Apps, along with other Azure services and Microsoft products, helped these companies improve their agility and focus on their core businesses by simplifying, organizing, automating, and orchestrating complex processes.

Next steps