Azure Logic Apps
Designer-built integration workflows over 1,400+ connectors, hosted per-execution (Consumption) or on a dedicated plan (Standard).
- Provider
- azure
- Kind
- Workflow engine
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| compensation | boolean | — | no | false | ▸ false |
| durable | boolean | — | no | true | ▸ true |
| hostingPlan | enum | consumption | standard | app-service-environment | hybrid | no | consumption | inherited |
| humanReview | boolean | — | no | false | inherited |
| integrationAccount | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ true |
| pattern | enum | saga | tcc | two-phase-commit | dag | no | dag | ▸ dag |
| stateful | boolean | — | no | true | inherited |
| stepsIdempotent | boolean | — | no | false | ▸ false |
| vnetIntegration | boolean | — | no | false | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "logic-apps", component: "azure-logic-apps" }CloudFlowalibaba-cloudflowCloudOps Orchestration Servicealibaba-oosAmazon Augmented AI (A2I)aws-augmented-aiAmazon Managed Workflows for Apache Airflowaws-mwaaAWS Systems Manager Incident Manager and Change Manageraws-ssm-incident-and-change-managerAWS Step Functionsaws-step-functionsAmazon Simple Workflow Serviceaws-swfAzure Durable Functionsazure-durable-functionsCloudflare Workflowscloudflare-workflowsApache AirflowairflowArgo Workflowsargo-workflowsAstronomer AstroastronomerCadencecadenceCamunda 8camundaConductorconductorDagsterdagsterDigdagdigdagFlowableflowableInngestinngestjBPMjbpmKestrakestraLuigiluigin8nn8nNode-REDnode-redPrefectprefectPrefect Cloudprefect-cloudRestaterestateTemporaltemporalTemporal Cloudtemporal-cloudTrigger.devtrigger-devWindmillwindmillWorkatoworkatoGeneric workflow engineworkflow-engineZapierzapierApplication Integrationgoogle-application-integrationCloud Composer (Managed Service for Apache Airflow)google-cloud-composerWorkflowsgoogle-cloud-workflowsOrchestration Pipelinesgoogle-orchestration-pipelinesIBM App Connectibm-app-connectOracle Integration 3oci-integration
and 4 more → Workflow engine page# yaml-language-server: $schema=../../schema/component.schema.json # Azure Logic Apps: designer-built workflows of a trigger plus actions. The platform delivers a message # "at least once" and states the workflow must implement idempotence itself; the default Consumption # resource is fully managed, holds one stateful workflow and is billed per execution. # Facts from "Workflow Integration and Automation - Azure Logic Apps" and # "Differences between Standard and Consumption logic apps". schemaVersion: "1" type: "component" id: "azure-logic-apps" kind: "workflow-engine" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-overview" defaults: managed: true durable: true pattern: "dag" stepsIdempotent: false compensation: false properties: hostingPlan: type: "enum" values: ["consumption", "standard", "app-service-environment", "hybrid"] default: "consumption" stateful: type: "boolean" default: true vnetIntegration: type: "boolean" default: false integrationAccount: type: "boolean" default: false