A VS Code extension for inspecting and debugging Azure Logic Apps Standard workflows — connect to local Docker containers, Azure Container Apps, or live Azure portal instances, all from one panel.
Features
Multi-Connection Management
Connect to multiple Logic Apps instances simultaneously — Local Docker, ACA-hosted, and Azure Logic Apps Standard (portal) — all appearing side-by-side in a single overview.
- Connections Manager: Use the ⚙ Connections panel in the overview to add, edit, delete, and reload connections without touching
settings.json
- Add Connection Wizard: Step-by-step guided setup via
LogicAppRunHistory: Add Connection — no manual JSON editing
- Edit Connection: Click ✏️ on any connection to update its settings with the wizard pre-filled
- Connection Type Badges: Each instance shows a
Local, ACA, or AZ-LA badge at a glance
- Backwards Compatible: The legacy
managementApi.endpoints array continues to work alongside the new connections setting
Run History & Debugging
- Run History Panel: Browse run history, filter by status and date range, paginate, and drill into individual runs
- Full-Page Run Details: Each run opens a dedicated details view with a
← Back button preserving filter state
- Action-Level Debugging: View input and output for every action in a run, including nested loops
- Loop Iteration Viewer: ForEach and Until scopes automatically expand per-iteration child action payloads
- Failed Actions Summary: A collapsible summary at the top of run details lists all genuinely failed actions with error codes
- Flow Diagram: Hierarchical text-based diagram of workflow execution order with status icons (🟢 🔴 ⚪)
- Collapsible UI: All action cards and loop iterations collapse/expand to reduce scroll depth
Note: Detailed run history view for Agentic workflows (workflows using AI/agent actions) is not yet supported — this is work in progress.
Triggering Workflows
- HTTP Trigger Request Builder: Click
▶ HTTP on any workflow to open an inline modal — choose method (GET/POST/PUT/PATCH/DELETE), add headers, compose a JSON body with validation
- Run Trigger: Fire any workflow trigger directly from the extension with a single click
- Resubmit Run: Replay any failed or completed run from scratch with
⟲ Resubmit
- Resubmit from Action: Partial replay starting from a specific action (
⟲ Resubmit from here)
Authentication
- Auto Key Management: Automatically fetches the local
_master key for secured endpoints (401/403 retry flow)
- VS Code Microsoft Sign-in: AZ-LA portal connections use the built-in VS Code Microsoft auth provider — triggers a browser sign-in the first time, then reuses the cached session. No extra extension required.
- Service Principal: Alternatively supply a client ID and secret for non-interactive/CI auth
- ARM Hostruntime Proxy: AZ-LA calls are routed through
management.azure.com/.../hostruntime/... so the ARM bearer token works directly — no Logic Apps host key needed
Developer Utilities
- HTTP Trigger Callback URLs: One-click retrieval with automatic internal hostname replacement for container environments
Requirements
- VS Code 1.105.0 or higher
- Azure Logic Apps Standard runtime (local host, Docker, ACA, or Azure portal)
- Azurite storage emulator (for local development)
- For AZ-LA portal connections: No extra extension required — uses VS Code's built-in Microsoft auth provider. You must be signed in to Azure via the Accounts menu (bottom-left status bar)
Quick Start
- Open the Command Palette (
Cmd/Ctrl+Shift+P)
- Run
LogicAppRunHistory: Open Logic Apps Run History Panel
- Use ⚙ Connections to add your Logic Apps endpoints
- Click ↺ Reload to connect — instances load in parallel
Commands
| Command |
Description |
LogicAppRunHistory: Open Logic Apps Run History Panel |
Open the Logic App Instances Dashboard |
LogicAppRunHistory: Add Connection |
Launch the connection wizard |
Settings
| Setting |
Type |
Default |
Description |
logicAppsLocalDevTools.managementApi.connections |
Array |
[] |
Typed connection objects (runtime or az-la). Preferred over endpoints. |
logicAppsLocalDevTools.managementApi.endpoints |
Array |
[] |
Legacy plain URL list — still supported |
logicAppsLocalDevTools.managementApi.apiVersion |
String |
"2016-06-01" |
Management API version |
logicAppsLocalDevTools.managementApi.apiKey |
String |
null |
Optional API key (auto-retrieved if omitted) |
Connection Configuration Examples
Runtime connection (Local Docker or ACA):
{
"logicAppsLocalDevTools.managementApi.connections": [
{
"type": "runtime",
"label": "Local Docker",
"endpoint": "http://localhost:7071/runtime/"
},
{
"type": "runtime",
"label": "ACA Staging",
"endpoint": "https://my-app.westeurope.azurecontainerapps.io/runtime",
"apiKey": "optional-key"
},
{
"type": "runtime",
"label": "ACA with EasyAuth",
"endpoint": "https://my-app.westeurope.azurecontainerapps.io/runtime",
"tenantId": "00000000-0000-0000-0000-000000000000",
"clientId": "service-principal-client-id",
"clientSecret": "service-principal-secret",
"easyAuthScope": "api://<aca-app-client-id>/.default"
}
]
}
Azure Logic Apps Standard (portal):
{
"logicAppsLocalDevTools.managementApi.connections": [
{
"type": "az-la",
"label": "Production",
"tenantId": "00000000-0000-0000-0000-000000000000",
"subscriptionId": "00000000-0000-0000-0000-000000000000",
"resourceGroup": "my-rg",
"appName": "my-logic-app"
}
]
}
The Add/Edit Connection wizard in the panel writes these entries for you — no manual JSON editing needed.
Troubleshooting
Can't connect to runtime
- Verify the runtime is up:
curl http://localhost:7071/runtime/webhooks/workflow/api/management/workflows
- For Docker, confirm port mapping with
docker ps
- Open ⚙ Connections in the dashboard and click ↺ Reload to retry all connections
401 / Unauthorized errors
- For runtime connections: the extension auto-fetches the
_master key. If that fails, set logicAppsLocalDevTools.managementApi.apiKey manually
- For AZ-LA portal connections: sign in to Azure via the Accounts menu in the VS Code status bar (bottom-left)
- Reload the VS Code window:
Developer: Reload Window
- Check
logicAppsLocalDevTools.managementApi.connections in your global settings (Cmd/Ctrl+,)
Panel is blank after opening
- Connection errors are now shown as VS Code warnings with the connections grid still visible
- Click ↺ Reload after fixing the connection issue
Callback URLs show internal IPs (172.x.x.x)
- The extension automatically replaces internal hostnames. Ensure your endpoint setting uses the public-facing URL
Documentation
Issues & Feedback
Report bugs at GitHub Issues. Include your VS Code version, extension version, and the Output panel log (View > Output → Logic Apps Local Dev Tools).