microsoft3 min read

Azure Logic Apps Tutorial: Enterprise Integration from Scratch (2026)

Azure Logic Apps Tutorial: Enterprise Integration from Scratch (2026)

Published:  |  Category: Microsoft  |  Reading time: ~15 min
Azure Logic Apps Tutorial: Enterprise Integration from Scratch (2026)

When I needed to integrate a legacy SAP system with modern cloud services, Azure Logic Apps saved me weeks of custom coding. Its enterprise connectors, built-in transformation, and robust error handling made the integration project a success. Logic Apps has become my go-to for enterprise application integration.

Azure Logic Apps is a cloud-based platform for creating automated workflows that integrate apps, data, systems, and services across enterprises. Use the visual designer to build workflows with hundreds of connectors. Logic Apps handles scaling, retry, and state management automatically.

Logic App Types and Triggers

Consumption Logic Apps run in multi-tenant environment with pay-per-execution pricing. Standard Logic Apps run in single-tenant with dedicated pricing and VNet support. Triggers: recurrence, HTTP webhook, Service Bus, Event Grid, and many SaaS connectors.

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "triggers": {
            "Recurrence": {
                "type": "Recurrence",
                "recurrence": {"frequency": "Hour", "interval": 1}
            }
        }
    }
}

Enterprise Connectors and Integration Accounts

Connectors include SAP, SQL Server, Oracle, IBM MQ, Service Bus, and hundreds more. Integration Account stores trading partners, agreements, schemas, and maps for B2B scenarios. EDI processing with X12 and EDIFACT standards.

// Integration Account artifacts:
// - Schemas (XSD) for XML validation and transformation
// - Maps (XSLT) for data transformation
// - Partners and Agreements for B2B/EDI
// - Certificates for encryption and signing

Workflow Actions, Conditions, and Loops

Design workflows with parallel branches, conditions, switch cases, and until loops. Built-in actions: HTTP, compose, parse JSON, create tables. Variables store state. Scope groups actions for error handling. Configure run after for each action.

{
    "actions": {
        "HTTP_GetOrder": {
            "type": "Http",
            "inputs": {
                "method": "GET",
                "uri": "https://api.contoso.com/orders/@{triggerOutputs()?['body/orderId']}"
            },
            "runAfter": {}
        },
        "Condition": {
            "type": "If",
            "expression": "@greater(body('HTTP_GetOrder')?['total'], 1000)",
            "actions": {
                "Send_Approval": {"type": "ApiConnection"}
            }
        }
    }
}

Error Handling and Retry Policies

Configure retry policies for transient failures — exponential, fixed, or none. Scope groups actions; configure run after for success, failure, skipped, or timed out. Dead-letter queues capture failed messages for later analysis.

{
    "actions": {
        "Call_SAP": {
            "type": "ApiConnection",
            "inputs": {
                "host": {"connectionName": "shared_sap"},
                "operationId": "RFC_CALL"
            },
            "retryPolicy": {
                "type": "Exponential",
                "count": 5,
                "interval": "PT10S"
            }
        }
    }
}

B2B Integration with AS2, X12, and EDIFACT

Process EDI documents using AS2 transport and X12 or EDIFACT message formats. Integration Account stores agreements. Decode/encode actions transform EDI to XML and back. Trading partner management handles certificates and identifiers.

// AS2 agreement configuration:
// - Identifiers: AS2From/AS2To
// - Certificates: signing and encryption
// - MDN: synchronous or async
// X12 message processing:
// - Decode X12 message to XML
// - Transform XML with maps
// - Encode XML back to X12

Monitoring, DevOps, and Deployment

Track workflow runs in Azure Portal. Application Insights provides detailed telemetry. Export Logic App templates for DevOps. Use ARM templates, Bicep, or Terraform for infrastructure as code. Deploy across environments with parameter files.

az logic workflow create --resource-group MyRG --name MyLogicApp --definition workflow.json
dotnet build LogicAppProject.csproj # For Standard Logic Apps
# ARM template deployment:
New-AzResourceGroupDeployment -ResourceGroupName MyRG -TemplateFile template.json -TemplateParameterFile parameters.json

Frequently Asked Questions

What is the difference between Logic Apps and Power Automate?

Logic Apps targets developers with enterprise features, more connectors, and DevOps integration. Power Automate targets business users with simpler UI and Microsoft 365 focus.

Can Logic Apps connect to on-premises systems?

Yes via the on-premises data gateway. Supports SQL Server, SAP, Oracle, IBM MQ, file shares, and custom on-premises APIs.

How does pricing work for Logic Apps?

Consumption: pay per execution and action. Standard: fixed hourly rate with included actions. Premium connectors cost extra.

Can I use Logic Apps for EDI/B2B scenarios?

Yes. Integration Account enables AS2, X12, and EDIFACT processing. Supports trading partner management, certificate handling, and MDN receipts.

Originally published on Ayodhyyya. Last updated June 1, 2026.