Azure Logic Apps Standard Gets a Local CLI in Preview

Microsoft has published a public preview of a local command-line interface for Azure Logic Apps Standard, delivered as the logicapp extension for the Azure CLI. Until now the Azure CLI could only manage already-deployed Logic Apps; the new extension adds local project creation, workflow authoring, a local runtime, connector and connection management, run inspection and test scaffolding. The practical effect is that a Standard workflow can be created, run and tested from a terminal without Visual Studio Code. InfoQ's Steef-Jan Wiggers reported the release, drawing on Microsoft's Community Hub announcement.
The extension installs itself automatically the first time an az logicapp developer command runs, provided the machine has Azure CLI 2.67.0 or later. It brings 19 command groups containing 64 commands, added beside the thirteen existing cloud-management commands, which the release leaves untouched. That split matters: existing scripts that use the older commands keep working, and the new surface sits alongside rather than replacing them.
Authoring is handled by a small set of project and workflow commands. project create either creates a new local project or adopts an existing one. workflow create, set, export and validate operate on individual workflow.json files, and validation runs offline by default. The runtime side is managed by runtime start, stop and show, which control a local host on port 7071. When a project is configured for development storage, the runtime launches the Azurite storage emulator, Microsoft's local emulator for Azure Storage services. In practice this means a developer can bring up a working local host without provisioning cloud storage, though local emulator behavior can differ from the real service in ways teams usually discover late.
The remaining groups reach into running and deployed apps. connector and connection inspect built-in and managed connectors, and wire connections into either a local project or a deployed app. run and trigger history can start, wait on, cancel and resubmit executions, and can download an action's recorded inputs and outputs, which is useful for debugging a failed run without leaving the terminal. deployment package produces what the documentation describes as a deterministic deployment package. Named context shortcuts store a target so later commands do not have to repeat it, a small convenience that matters more in scripted or agent-driven sequences.
Two command families, doctor and test, reveal who the tool is designed for. runtime doctor is strictly read-only: it reads project files, tool versions, cached bundle evidence and loopback ports, and per the announcement never installs, downloads, starts, stops, repairs, decrypts settings, changes context or contacts cloud storage. It exits 1 for a required failure and 2 when a required check returns unknown, giving automation a clean signal to branch on. Testing is deliberately split into three steps: test create scaffolds a native SDK test project and stops before restoring a package or running anything, test plan writes a preflight report without executing tests, and test run is the only command that builds and runs them, under a deadline. The announcement lists limitations on that last step, and in the pull request that added the extension, author Riley Evans notes that native SDK test code is trusted rather than sandboxed, and that an agent bootstrap command does not exist yet.
Microsoft MVPs have framed the release around AI-assisted development. Sagar Sharma wrote on LinkedIn that the CLI is pitched as adding determinism to local AI-assisted coding: an agent validates, runs, inspects and tests, then repeats until the run is green, with secrets reaching it through stdin rather than on the command line. He had earlier called the CLI the sleeper hit of Microsoft's recent Logic Apps announcements, arguing that an agent without a deterministic way to validate and run a workflow is guessing. Named contexts, capability discovery and secret handling were his evidence that the tool was designed for that case. Sonny Gillissen, also an MVP, described the team-level benefit: a new hire clones a repository and has a local runtime up in minutes rather than hours, a coding assistant drafts a workflow against an authoritative shell instead of assumptions, and integration flows get tested from the CI/CD pipeline rather than by hand. He also suggested an agent could test a workflow locally without touching Azure at all.
That last remark is the one Christos Panagiotidis, another Microsoft MVP and certified trainer, would test first. His pilot plan is explicitly a proposal rather than a report of a run, and its two main cautions come from Microsoft's own walkthrough. That walkthrough uses live Azure and Microsoft 365 resources, and some of its commands change deployed connections, so a local run can have remote effects regardless of how the terminal session feels. Microsoft itself notes that validation does not establish authorization or business correctness. Panagiotidis adds a housekeeping point: CLI extensions do not update with the CLI, so anyone comparing results across runs needs the CLI, extension, runtime and project versions recorded next to each result.
Microsoft has said a broader command surface will follow soon. Until then the visual designer stays in VS Code. The CLI edits workflow.json directly, cannot change the state of a running local app, and the pull request's limits section concedes that Linux CI results prove neither native SDK execution nor execution against live Azure. My reading is that the workflow.json-first approach suits agents and pipelines better than humans doing visual wiring, but it also means validation quality and change review become the main safeguards when a model is generating JSON.
Why it matters: teams building Logic Apps Standard gain a scriptable path to create, run and test workflows in CI and in agent loops, which lowers the barrier for automated integration testing. Developers already invested in the VS Code extension will likely keep it for visual design and adopt the CLI for pipelines and agents. As inference, the biggest near-term risk is teams treating a green local run as proof of correctness, when authorization, business logic and cross-environment behavior still need separate checks. Version pinning across CLI and extension is worth building into CI from day one.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Microsoft has released a public preview of the logicapp extension for the Azure CLI, adding local project creation, workflow authoring, a runtime lifecycle, connector management, run inspection, and test scaffolding for Logic Apps Standard, work that previously required the VS Code extension. The product team pitches the terminal surface as determinism for AI-assisted development. By Steef-Jan Wiggers