Azure Logic Apps, API Management and Integration Patterns: Workflows, Connectors, Policies and Gateways
Azure Integration Services
| Service | Role |
|---|---|
| Logic Apps | Low-code workflows with hundreds of connectors |
| API Management (APIM) | Publish, secure, throttle and monitor APIs |
| Service Bus / Event Grid | Messaging and events (previous lesson) |
| Functions | Custom code steps |
| Data Factory | Large scale data movement |
Logic Apps
- A workflow = trigger (starts it) + actions (steps) with conditions, loops and error handling
- Connectors exist for Office 365, SharePoint, SQL, Service Bus, Salesforce, SAP, Twitter, HTTP and many more
- Designed visually in the portal or VS Code. Stored as JSON definitions that you deploy with Bicep or ARM
| Plan | Notes |
|---|---|
| Consumption | Multi-tenant, pay per execution. Quick and cheap for small flows |
| Standard | Single-tenant, runs on workflow service plan or App Service Environment, VNet integration, stateful and stateless workflows, local development |
Logic Apps or Power Automate? Power Automate is for business users inside Microsoft 365. Logic Apps is for developers and IT with ARM deployment, source control and enterprise integration.
Example flow: When a blob is added to the invoices container, extract data with an AI step, insert a row into Azure SQL and send an email to finance. If any step fails, send a Teams message.
API Management
- A gateway in front of your backend APIs (App Service, Functions, AKS, on-premises). Clients call APIM, APIM calls the backend
- Developer portal for documentation and subscription keys
- Concepts: API, operation, product (a bundle of APIs with a policy and approval), subscription (keys), policy (XML rules applied to requests and responses)
- Tiers: Consumption (serverless), Developer, Basic, Standard, Premium (multi-region, zones, VNet) and v2 tiers. Check current names and features
Common Policies
xml
<policies>
<inbound>
<base />
<validate-jwt header-name="Authorization" failed-validation-httpcode="401">
<openid-config url="https://login.microsoftonline.com/<tenant-id>/v2.0/.well-known/openid-configuration" />
<audiences><audience>api://shop-api</audience></audiences>
</validate-jwt>
<rate-limit calls="100" renewal-period="60" />
<set-header name="X-Forwarded-By" exists-action="override"><value>apim</value></set-header>
<cache-lookup vary-by-developer="false" vary-by-developer-groups="false" />
</inbound>
<backend><base /></backend>
<outbound><base /><cache-store duration="30" /></outbound>
<on-error><base /></on-error>
</policies>
| Policy | Effect |
|---|---|
validate-jwt | Reject requests without a valid token |
rate-limit / quota | Throttle callers |
ip-filter | Allow or block IPs |
cache-lookup / cache-store | Cache responses |
rewrite-uri, set-header | Transform requests |
retry, forward-request | Resilience and routing |
Putting It Together
- Clients call Front Door / App Gateway (WAF)
- Traffic goes to APIM for authentication, throttling and routing
- APIM calls Functions or App Service backends in a VNet
- Backends publish events to Service Bus and Logic Apps handle long business workflows
Practice
- Build a Logic App that reads a blob and sends an email
- Import an API into APIM and apply a rate limit
- Add JWT validation and test a call without a token
Conclusion
Logic Apps automate cross-system workflows with connectors. API Management protects and publishes APIs with policies for security, throttling and caching. Combine them with messaging for reliable integration.
Quick Summary: integration services; Logic Apps; APIM; policies; architecture.

