Serverless workflow orchestration platform for automating business processes and integrating applications. Azure Logic Apps provides:
- Visual designer: Drag-and-drop workflow design with 1,400+ connectors
- Standard vs Consumption: Choose between multi-tenant and single-tenant hosting
- Connectors: Built-in connectors such as SQL Server, Service Bus and HTTP, plus managed connectors for SAP, Oracle, Dataverse, Salesforce, and more
- Enterprise Integration Pack: B2B messaging with EDI, AS2, and X12
Azure Logic Apps development
Standard vs Consumption
Choose the right hosting model based on your requirements:
| Feature | Consumption | Standard |
|---|---|---|
| Hosting | Multi-tenant, serverless | Single-tenant, dedicated |
| Pricing | Pay per execution | Hourly hosting plan (WS1–WS3) plus managed connector calls |
| VNet integration | Not available (ISE was retired in 2024); use Standard | Built-in support |
| Local development | Limited | Full VS Code support |
| Best for | Low-volume, cloud-only | High-volume, hybrid, dev/test |
Advanced Logic Apps features
Stateful vs stateless workflows
Standard Logic Apps support both execution modes:
- Stateful: Run history persisted, supports long-running operations, retry with history
- Stateless: No history, faster execution, ideal for high-throughput scenarios
Built-in connectors
Built-in connectors run in the same process as Logic Apps runtime for better performance:
- Azure Service Bus, Azure Blob Storage, Azure Cosmos DB
- HTTP, request/response, schedule
- SQL Server (built-in version for better performance)
- Inline code (JavaScript execution within workflow)
Custom connectors
Build connectors for any REST API with OpenAPI specification:
- Import OpenAPI 2.0 (Swagger) definitions or Postman collections
- Configure authentication (OAuth 2.0, API key, Basic)
- Add custom code for request/response transformation
- Share connectors across organization or publish publicly
Error handling & resilience
Integrations fail: a partner API times out, a database is briefly unavailable. Good workflows expect it.
A Logic Apps run with error handling
When an HTTP request is received
Parse JSON
Scope · Try
Upsert order in ERP
Retry policy (exponential):#1 …#2 …
run after: succeeded
Response 200
Scope · Catch — run after: failed
Log to Application Insights
Notify support
Run history
- 08584…a1Running
- 08584…9c1.2 sSucceeded
- 08584…930.9 sSucceeded
- 08584…8e31 sFailed, handled
Illustrative example
- Retry policies: Default, none, fixed interval or exponential interval (up to 90 retries)
- Scope actions: Group actions with shared error handling
- Run after configuration: Control action execution based on previous action status
- Try-catch-finally: Structured exception handling with scope actions
- Timeout settings: Action-level and workflow-level timeouts