Overview

Azure Logic Apps is a managed service that facilitates the design, construction, and operation of automated workflows at scale. It acts as an integration platform as a service (iPaaS), enabling organizations to connect disparate systems, applications, and data sources, whether they reside in the cloud or on-premises Microsoft Azure Logic Apps documentation. The service is designed for scenarios ranging from simple task automation to complex enterprise integrations, including business process automation, data synchronization, and B2B communication through Electronic Data Interchange (EDI).

The platform offers a visual workflow designer, allowing users to define workflows using a drag-and-drop interface. This approach can reduce the need for extensive code development, making it accessible to a broader range of technical users, including business analysts and developers focused on integration. For more advanced use cases, Logic Apps supports integration with development tools like Visual Studio Code and can be managed using Azure Resource Manager (ARM) templates, which facilitates infrastructure-as-code practices and source control Deploy Logic Apps with ARM templates.

Logic Apps supports a wide array of connectors to various services, including other Azure services like Azure Functions, Azure Service Bus, and Azure Event Grid, as well as third-party SaaS applications such as Salesforce, Office 365, and Dropbox. This extensive connector ecosystem streamlines the integration process, abstracting away the complexities of API interactions. The service operates on a serverless model, meaning users do not need to provision or manage underlying infrastructure. Resources are dynamically allocated and scaled based on demand, which is a common characteristic of serverless computing platforms Martin Fowler's take on Serverless Architectures.

There are two primary hosting models for Azure Logic Apps: the Consumption plan and the Standard plan. The Consumption plan is a fully managed, pay-as-you-go model where costs are based on the number of actions executed, connector calls, and storage used. This model is suitable for stateless workflows and scenarios with variable loads. The Standard plan offers dedicated hosting with a single-tenant environment, providing greater control, predictable performance, and the ability to run stateful and stateless workflows within the same logic app. This plan is often chosen for enterprise-grade applications requiring advanced networking capabilities, higher throughput, and more consistent latency. Both plans offer robust capabilities for building event-driven architectures and automating business processes.

Key features

  • Visual Workflow Designer: A graphical interface for creating, editing, and visualizing workflows by dragging and dropping actions and connectors Logic Apps designer overview.
  • Extensive Connector Ecosystem: Pre-built connectors for hundreds of services, including Azure services, Microsoft services (e.g., Dynamics 365, SharePoint), and popular SaaS applications (e.g., Salesforce, Dropbox, Twitter) Azure Logic Apps connector reference.
  • Serverless Execution: Automatic scaling and infrastructure management, allowing developers to focus on workflow logic without managing servers.
  • Conditional Logic and Loops: Support for complex workflow logic including conditional statements, switch cases, and various looping constructs (for-each, until).
  • Enterprise Integration Pack (EIP): Capabilities for B2B communication, including EDI standards (X12, AS2) and XML processing, often used for supply chain automation and partner integration Enterprise Integration Pack for Logic Apps.
  • Custom Connectors: Ability to create and register custom connectors to integrate with services that do not have pre-built connectors, using OpenAPI (Swagger) definitions Create custom connectors for Logic Apps.
  • Integration with Azure Services: Seamless integration with other Azure services like Azure Functions for custom code execution, Azure Event Grid for event-driven scenarios, and Azure Service Bus for messaging Call Azure Functions from Logic Apps.
  • Monitoring and Management: Built-in monitoring tools through Azure Monitor, providing logs, metrics, and alerts for tracking workflow execution and performance Monitor Logic Apps with Azure Monitor.
  • Infrastructure as Code (IaC): Support for defining and deploying logic apps using ARM templates and Bicep, enabling repeatable deployments and version control.

Pricing

Azure Logic Apps offers two main pricing models: Consumption and Standard, each with different cost structures based on usage and hosting environment. The pricing below is accurate as of May 2026.

Metric Consumption Plan Standard Plan
Actions Executed $0.000025 per action Included in dedicated hosting plan (throughput based)
Standard Connector Operations $0.000125 per operation Included in dedicated hosting plan
Enterprise Connector Operations $0.001 per operation Included in dedicated hosting plan
Built-in Operations $0.000008 per operation Included in dedicated hosting plan
Standard Plan (WS1 instance) N/A Starts at approximately $0.15/hour (includes compute, storage, throughput)
Storage (Consumption) $0.0245 per GB per month Included in dedicated hosting plan's storage allocation

For detailed and up-to-date pricing information, refer to the official Azure Logic Apps pricing page.

Common integrations

Alternatives

  • AWS Step Functions: A serverless workflow service that orchestrates AWS services and microservices using visual workflows, similar to Logic Apps.
  • Google Cloud Workflows: A fully managed orchestration service that executes sequences of services using HTTP calls and Cloud Events, comparable in function.
  • Zapier: An online automation tool that connects apps and services, primarily targeted at business users for everyday task automation.
  • Cloudflare Workers Cron Triggers: Provides serverless execution of code on a schedule, which can be used for simpler automation tasks without the visual workflow builder.
  • Azure Functions: A serverless compute service that allows running small pieces of code (functions) in the cloud without explicitly provisioning or managing infrastructure. While not a direct workflow orchestration tool, it can be combined with other services to build custom automation.

Getting started

While Azure Logic Apps primarily uses a visual designer, a common way to define and deploy them programmatically is through Azure Resource Manager (ARM) templates. Below is a simplified ARM template example for a basic HTTP-triggered logic app that returns a 'Hello World' response.

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "logicAppName": {
      "type": "string",
      "defaultValue": "HelloWorldLogicApp",
      "metadata": {
        "description": "Name of the Logic App."
      }
    },
    "location": {
      "type": "string",
      "defaultValue": "[resourceGroup().location]",
      "metadata": {
        "description": "Location for the Logic App."
      }
    }
  },
  "resources": [
    {
      "type": "Microsoft.Logic/workflows",
      "apiVersion": "2019-05-01",
      "name": "[parameters('logicAppName')]",
      "location": "[parameters('location')]",
      "properties": {
        "state": "Enabled",
        "definition": {
          "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
          "contentVersion": "1.0.0.0",
          "parameters": {},
          "triggers": {
            "manual": {
              "type": "Request",
              "kind": "Http",
              "inputs": {
                "schema": {}
              }
            }
          },
          "actions": {
            "Response": {
              "runAfter": {},
              "type": "Response",
              "inputs": {
                "body": "Hello World from Logic Apps!",
                "statusCode": 200
              }
            }
          },
          "outputs": {}
        },
        "parameters": {}
      }
    }
  ]
}

To deploy this template, you would typically use the Azure CLI or Azure PowerShell:

az group create --name MyResourceGroup --location eastus
az deployment group create --resource-group MyResourceGroup --template-file path/to/your/template.json

After deployment, the logic app can be triggered by sending an HTTP POST request to its generated URL, which can be found in the Azure portal.