Azure Logic Apps

Visual workflow orchestration: trigger on events (HTTP, schedule, SaaS connectors) and chain actions (transform, branch, call APIs) without writing code.

AzureBeginner

Why

Logic Apps let analysts and developers build integrations (e.g., 'when a new email arrives, parse the attachment, insert into SQL, post to Teams') visually, with 400+ managed connectors. The Consumption tier bills per action execution, so low-volume workflows cost pennies.

It handles retries, polling, and error handling declaratively.

When

Use Logic Apps for SaaS integrations (Salesforce, Dynamics, Office 365), scheduled ETL, or event-driven automation where a visual flow is clearer than code. Use Functions for compute-heavy or code-heavy logic; use Logic Apps for orchestration that calls Functions for the heavy parts.

Avoid for high-throughput pipelines — per-action billing adds up.

How

1. Create a Logic App (Consumption for pay-per-action, Standard for single-tenant with VNet). 2. Add a trigger (Recurrence for scheduled, Request for HTTP, or a connector trigger). 3. Add actions: parse JSON, condition, loop, HTTP call, or a managed connector action. 4. Map fields with expressions (@triggerBody(), @json()). 5. Save and run; view the run history to debug each action's inputs/outputs. 6. For CI/CD, export the ARM template and deploy with Azure DevOps/GitHub Actions. ```bash az logic workflow create --name mylogic --resource-group rg --definition @workflow.json --location eastus ```

Example

A Logic App that runs daily, queries a SQL DB for new orders, and emails a summary — defined in JSON: ```json { "definition": { "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#", "triggers": { "daily": { "type": "Recurrence", "recurrence": { "frequency": "Day", "interval": 1 } } }, "actions": { "GetOrders": { "type": "ApiConnection", "inputs": { "host": { "connection": { "name": "@parameters('$connections')['sql']['connectionId']" } }, "method": "get", "path": "/v2/datasets/default/tables/orders/items" } }, "SendEmail": { "type": "ApiConnection", "runAfter": { "GetOrders": [ "Succeeded" ] }, "inputs": { "host": { "connection": { "name": "@parameters('$connections')['office365']['connectionId']" } }, "method": "post", "body": { "to": "ops@contoso.com", "subject": "Daily orders", "body": "@body('GetOrders')" } } } }, "outputs": {} } } ```

Common Problems

⚠Connector authentication expires — re-authenticate the API connection in the portal; for service principals, set credentials that do not expire or rotate via Key Vault.
⚠Run history shows an action failed with a 429 from the SaaS API — add retry policy and a delay action; Logic Apps retries 4 times by default but may need a longer interval for rate-limited APIs.
⚠Consumption tier cost explodes on high-frequency triggers — switch to the Standard tier (flat price) or add a filter condition early so the workflow exits cheaply when there is nothing to do.

Best Practices

✓Add a filter/condition as the first action so the workflow exits immediately when there is nothing to process — this avoids paying for downstream actions on no-op runs.
✓Use the Standard tier for high-volume workflows — it has a flat monthly price and runs in your VNet, unlike Consumption's per-action billing.
✓Export the workflow as an ARM template and version it in Git; deploy via CI/CD rather than editing in the portal directly.

FAQ

What is Azure Logic Apps and what problem does it solve?

Visual workflow orchestration: trigger on events (HTTP, schedule, SaaS connectors) and chain actions (transform, branch, call APIs) without writing code. It lets developers deploy, store, and scale without self-managing infrastructure — a core reference for cloud service selection.

How do I get started with Azure Logic Apps in 5 minutes?

Two steps to run it: (1) Create a Logic App (Consumption for pay-per-action, Standard for single-tenant with VNet).; (2) Add a trigger (Recurrence for scheduled, Request for HTTP, or a connector trigger).. Validate on the free tier first, then wire into production.

What is the #1 pitfall with Azure Logic Apps?

The most frequent issue is: Connector authentication expires — re-authenticate the API connection in the portal; for service principals, set credentials that do not expire or rotate via Key Vault.. Run a pre-launch checklist item by item, and add policy/config scanning in CI.

What are the best practices for Azure Logic Apps?

Best practices for Azure Logic Apps include: Add a filter/condition as the first action so the workflow exits immediately when there is nothing to process — this avoids paying for downstream actions on no-op runs.; Use the Standard tier for high-volume workflows — it has a flat monthly price and runs in your VNet, unlike Consumption's per-action billing.; Export the workflow as an ARM template and version it in Git; deploy via CI/CD rather than editing in the portal directly.. The first one — "Add a filter/condition as the first action so the workflow exits immediately when there is nothing to process — this avoids paying for downstream actions on no-op runs." — should be a team default baked into your IaC templates.

How do I control cost and avoid bill surprises with Azure Logic Apps?

Three ways to prevent overspend: (1) tag every resource with env/team and enable billing alarms; (2) set budget thresholds to trigger Slack/email alerts; (3) review idle resources in Cost Explorer regularly and clean them up. Most Azure Logic Apps options offer a free tier — validate within free quota before scaling.