DEV Community

Daniel Jonathan
Daniel Jonathan

Posted on

Logic Apps Local Dev Tools — Now with ACA and Azure Sign-in Support

The Logic Apps Local Dev Tools VS Code extension started as a local dev tool — connect to a Logic Apps container running via Docker and browse run history without leaving the editor.

This update adds two new connection types: ACA support via direct FQDN and Azure Sign-in for cloud-hosted Logic Apps Standard. If you used the original version for local Docker, everything still works — you just have more options now.


One dashboard, three connection types

The extension now supports three types of Logic Apps instances in a single panel:

  • Runtime — direct HTTP endpoint, works for local Docker (localhost:7074) or an ACA FQDN
  • AZ-LA — Azure Sign-in, connects to Logic Apps Standard via your subscription
  • EasyAuth — ACA endpoint secured with Azure AD ingress auth; the extension handles the Bearer token using a Service Principal

All instances appear side by side in the Logic Apps Instances view:


Managing connections

Click Connections to add, edit, or remove any instance. Each connection has a label, type, and endpoint or Azure resource identifier:

  • Runtime connections take a plain URL — ACA FQDN or localhost for Docker
  • AZ-LA connections use Azure Sign-in: select subscription, resource group, and Logic App — no endpoint URL needed
  • EasyAuth connections take the ACA FQDN plus a Service Principal (client ID + secret) — the extension acquires a Bearer token automatically on each request

EasyAuth — connecting to a protected ACA endpoint

If your Logic Apps container on ACA has Azure AD ingress auth enabled (unauthenticatedClientAction: Return401), the Runtime type won't work — requests without a Bearer token get a 401 before reaching the container.

Use EasyAuth instead: provide the ACA FQDN and a Service Principal with access to the app registration. The extension acquires a token via client credentials flow and attaches it to every request. SAS payload fetches (run history inputs/outputs) pass through the ACA platform exemption for /runtime/webhooks/* without needing a token.

When to use each type:

Scenario Connection type
Local Docker (localhost) Runtime
ACA container, no auth Runtime
ACA container, ACA Easy Auth enabled EasyAuth
Cloud Logic Apps Standard (App Service) AZ-LA

ACA workflow view

Clicking View Workflows on an ACA instance shows the full workflow list with kind, status, health, and trigger. From here you can get the callback URL or jump straight into run history:

The run history panel works the same as local — full input/output per action, no Azure Portal needed.


Install from the VS Code Marketplace:
Logic Apps Local Dev Tools

For the original local dev walkthrough — Docker setup, Azurite, and the design → test loop:
Logic Apps Local Dev Tools — Visual Walkthrough

Top comments (0)