Azure Logic Apps
Many business processes involve repetitive workflows — receiving an email with an attachment, saving it to SharePoint, notifying the team on Teams, and logging it in a spreadsheet. Automating these steps traditionally requires custom code. Azure Logic Apps is a low-code/no-code workflow automation service that connects hundreds of apps and services through visual, drag-and-drop workflows — without writing a single line of code.
What is Azure Logic Apps?
Azure Logic Apps allows building automated workflows that integrate apps, data, services, and systems. A workflow is triggered by an event, then runs a series of automated steps (actions) to process, transform, and route data between connected services. Over 400 built-in connectors are available — covering Microsoft services, Google, Salesforce, SAP, Twitter, Slack, and virtually any REST API.
Logic App Building Blocks
Trigger
Every workflow starts with one trigger. The trigger defines the event that starts the workflow. Triggers are either polling (check for new data on a schedule) or webhook-based (wait for an external system to notify).
Action
Actions are the steps that execute after the trigger fires. Each action connects to a service — send an email, create a record in Salesforce, post a message in Teams, transform JSON data, or call an HTTP API.
Control Flow
Logic Apps supports conditional logic (If/Else), loops (For Each, Until), parallel branches, and error handling (Try/Catch) — allowing complex, branching workflows.
Example Workflow – Email Attachment to SharePoint
Trigger: When a new email arrives in Outlook
(Filter: Subject contains "Invoice")
│
▼
Action 1: Get the attachment from the email
│
▼
Action 2: Create a file in SharePoint
Path: /Finance/Invoices/[filename]
Content: [attachment content]
│
▼
Action 3: Post a message in Microsoft Teams
Channel: Finance Team
Message: "New invoice received: [filename] from [sender]"
│
▼
Action 4: Add a row to an Excel file
Workbook: Invoice-Log.xlsx
Row: Date=[today], Sender=[email], File=[filename]
No code written. The entire workflow is configured using the visual designer by selecting connectors and filling in parameters.
Logic App Connectors
Connectors are pre-built integrations with external services. They expose triggers and actions that can be used in workflows.
| Category | Example Connectors |
|---|---|
| Microsoft 365 | Outlook, SharePoint, Teams, Excel, OneDrive, Dynamics 365 |
| Azure Services | Service Bus, Event Hub, Blob Storage, SQL, Cosmos DB, Functions |
| SaaS Applications | Salesforce, ServiceNow, SAP, Workday, Zendesk, HubSpot |
| Communication | Slack, Twilio (SMS), SendGrid (Email), Gmail |
| Social Media | Twitter/X, LinkedIn, RSS feeds |
| Developer Tools | GitHub, Azure DevOps, Jira |
| Generic | HTTP (call any REST API), SFTP, FTP, AS2, X12 (EDI) |
Logic Apps Hosting Options
| Type | Hosting | State | Best For |
|---|---|---|---|
| Consumption (Multi-tenant) | Microsoft manages infrastructure | Stateful and Stateless | Simple integrations, pay-per-execution model |
| Standard (Single-tenant) | Runs on Azure App Service Plan | Stateful and Stateless | Enterprise workflows, VNet integration, local dev support |
| Integration Service Environment (ISE) | Dedicated environment inside a VNet | Stateful | Compliance-heavy scenarios needing fully private deployment |
Stateful vs Stateless Workflows
- Stateful workflows: The run history and intermediate state of every step is saved to storage. Workflows can be long-running (days, weeks) and can be inspected, rerun, or resumed after failures. Best for critical business processes.
- Stateless workflows: No state is saved between steps. Runs entirely in memory for maximum speed. Best for high-frequency, short-lived workflows like real-time event processing.
Built-in Actions for Data Transformation
Logic Apps includes powerful built-in operations that do not require external connectors:
- Parse JSON / Compose: Extract and restructure JSON data between steps.
- Filter Array: Keep only items in an array that match a condition.
- Select: Transform each item in an array (similar to a map operation).
- Join: Combine array elements into a single string.
- XML Transform: Convert XML documents using XSLT maps (enterprise B2B scenarios).
- Inline Code: Execute a snippet of JavaScript code for transformations too complex for built-in actions.
Error Handling and Retry Policies
Every action in a Logic App can have a retry policy configured. If an action fails due to a transient error (network blip, service temporarily unavailable), the Logic App automatically retries the action with configurable intervals. Custom error paths (similar to try/catch) can route failed runs to an alert action or a compensating workflow.
Integration with Azure Services
Common Azure Integration Scenario:
Service Bus Queue Message Arrives
│
▼
Logic App Triggered
│
├── Parse the message body (JSON)
│
├── Call Azure Function (complex business logic)
│
├── Write result to Azure SQL Database
│
├── IF success → Send Teams notification
└── IF failure → Send alert email + write to dead-letter queue
Key Takeaways
- Azure Logic Apps is a low-code/no-code workflow automation service that connects 400+ apps and services.
- Every workflow has one trigger (what starts it) and one or more actions (what it does).
- Connectors provide pre-built integrations with Microsoft 365, Azure services, Salesforce, Slack, SAP, and any REST API.
- Stateful workflows retain run history for long-running processes; stateless workflows run in memory for maximum performance.
- Built-in retry policies and error handling make Logic Apps workflows resilient to transient failures.
