Top 20 Azure Logic Apps Interview Questions and Answers
- What is Azure Logic Apps?
- What is the difference between Logic Apps (Consumption) and Logic Apps (Standard)?
- What are connectors in Logic Apps?
- What is the difference between triggers and actions?
- How do you handle errors in Logic Apps?
- What is the difference between Logic Apps and Power Automate?
- How do you implement loops in Logic Apps?
- What are managed identities in Logic Apps?
- How do you call REST APIs in Logic Apps?
- What is the Workflow Definition Language?
- How do you implement conditional logic?
- What are integration accounts?
- How do you secure Logic Apps?
- What is the difference between stateful and stateless workflows?
- How do you monitor Logic Apps?
- What are inline code actions?
- How do you implement retry policies?
- What is the Liquid template in Logic Apps?
- How do you integrate Logic Apps with Azure Functions?
- What are best practices for Logic Apps?
Microsoft Azure Interview Questions
Comprehensive interview questions for Azure cloud services and data engineering roles.
1. What is Azure Logic Apps?
Azure Logic Apps is a cloud-based platform for creating and running automated workflows that integrate apps, data, services, and systems.Key Features:
- Low-Code/No-Code: Visual designer for workflow creation
- 400+ Connectors: Pre-built integrations with services
- Enterprise Integration: B2B scenarios, EDI, XML processing
- Serverless: Auto-scale, pay-per-execution
- Hybrid: Connect to on-premises systems
Use Cases:
- Business process automation
- System integration (SaaS, on-premises)
- B2B workflows (EDI, AS2)
- Event-driven processing
- API orchestration
2. What is the difference between Logic Apps (Consumption) and Logic Apps (Standard)?
| Aspect | Consumption | Standard |
|---|---|---|
| Hosting | Multi-tenant | Single-tenant / ASE |
| Pricing | Pay per execution | Hosting plan based |
| Workflows per Resource | 1 | Multiple |
| Deployment | Azure only | Azure, Docker, Kubernetes |
| VNET Integration | ISE required | Built-in |
| Development | Portal, VS Code | VS Code primary |
| Stateless Workflows | No | Yes |
| Local Development | Limited | Full support |
Choose Consumption when:
- Simple, event-driven workflows
- Unpredictable execution volumes
- Quick start without infrastructure
Choose Standard when:
- Need network isolation
- Multiple related workflows
- Predictable high-volume workloads
- Run anywhere requirement
3. What are connectors in Logic Apps?
Connectors provide pre-built access to services, applications, and systems.Connector Types:
Built-in Connectors:
- Run natively within Logic Apps runtime
- HTTP, Schedule, Batch, Request/Response
- Lower latency, higher throughput
Managed Connectors:
- Microsoft-managed API connections
- Standard: Office 365, SQL, Salesforce
- Enterprise: SAP, IBM MQ (additional cost)
Custom Connectors:
- Wrap REST/SOAP APIs
- Created using OpenAPI specification
// Example: SQL Server connector action
{
"type": "ApiConnection",
"inputs": {
"host": {
"connection": {
"name": "@parameters('$connections')['sql']['connectionId']"
}
},
"method": "get",
"path": "/datasets/default/tables/@{encodeURIComponent('dbo.Orders')}/items"
}
}
// Example: HTTP connector (built-in)
{
"type": "Http",
"inputs": {
"method": "POST",
"uri": "https://api.example.com/orders",
"headers": {"Content-Type": "application/json"},
"body": "@triggerBody()"
}
}
4. What is the difference between triggers and actions?
Triggers:- Start the workflow execution
- First step in every workflow
- Only one trigger per workflow
Trigger Types:
// 1. Recurrence (Schedule)
{
"type": "Recurrence",
"recurrence": {
"frequency": "Hour",
"interval": 1
}
}
// 2. HTTP Request (Webhook)
{
"type": "Request",
"kind": "Http",
"inputs": {
"schema": {
"type": "object",
"properties": {
"orderId": {"type": "integer"}
}
}
}
}
// 3. Polling (When item created)
{
"type": "ApiConnection",
"inputs": {
"host": {"connection": {"name": "@parameters('$connections')['sql']['connectionId']"}},
"method": "get",
"path": "/datasets/default/tables/@{encodeURIComponent('Orders')}/onnewitems"
},
"recurrence": {"frequency": "Minute", "interval": 5}
}
Actions:
- Perform operations after trigger
- Multiple actions per workflow
- Can be chained, parallel, or conditional
5. How do you handle errors in Logic Apps?
1. Configure Run After:
// Action runs after specific conditions
{
"actions": {
"Send_failure_email": {
"runAfter": {
"Process_order": ["Failed", "TimedOut"]
},
"type": "ApiConnection",
...
}
}
}
// Run after states: Succeeded, Failed, Skipped, TimedOut
2. Scope with Try-Catch:
{
"actions": {
"Try_Scope": {
"type": "Scope",
"actions": {
"Action1": {...},
"Action2": {...}
}
},
"Catch_Scope": {
"type": "Scope",
"runAfter": {
"Try_Scope": ["Failed", "TimedOut"]
},
"actions": {
"Log_Error": {
"type": "Compose",
"inputs": "@result('Try_Scope')"
},
"Send_Alert": {...}
}
}
}
}
3. Retry Policy:
{
"type": "Http",
"inputs": {...},
"retryPolicy": {
"type": "exponential",
"count": 4,
"interval": "PT10S",
"minimumInterval": "PT5S",
"maximumInterval": "PT1H"
}
}