Microsoft has released a public preview of a local command-line interface for Azure Logic Apps Standard, shipped as the logicapp extension for the Azure CLI. It adds project creation, workflow authoring, a local runtime, connector and connection management, run inspection, and test scaffolding to a tool that until now only managed deployed apps, so that a Standard workflow can be created, run, and tested without Visual Studio Code.
The extension installs automatically the first time an az logicapp developer command runs on Azure CLI 2.67.0 or later, and adds 19 command groups with 64 commands beside the thirteen existing cloud-management commands, which it leaves untouched. On the authoring side, project create creates or adopts a local project; workflow create, set, export, and validate work on individual workflow.json files with offline validation by default, and runtime start, stop, and show manage a local host on port 7071, launching the Azurite storage emulator when the project is configured for development storage.
The remaining groups reach into running and deployed apps. connector and connection inspect built-in and managed connectors and wire connections into a project or a deployed app, run and trigger history start, wait on, cancel and resubmit executions and download an action’s recorded inputs and outputs, and deployment package produces what the documentation calls a deterministic deployment package. Named context shortcuts hold a target so later commands do not repeat it.
(Source: Microsoft Community Hub)
The doctor and test commands say the most about who the tool expects to be typing. runtime doctor only reads: project files, tool versions, cached bundle evidence, loopback ports. It "never installs, downloads, starts, stops, repairs, decrypts settings, changes context, or contacts cloud storage," and it exits 1 for a required failure and 2 when a required check comes back unknown. Testing is split into three steps for the same reason. 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 a test, and test run is the only command that builds and runs them, under a deadline. The announcement lists limitations on that last step. In the pull request that added the extension, author Riley Evans goes further: native SDK test code is trusted rather than sandboxed, and the agent bootstrap command does not exist yet.
Sagar Sharma, a Microsoft MVP, wrote on LinkedIn that this is deliberate. The CLI is "literally pitched as adding determinism to local AI-assisted coding": an agent validates, runs, inspects and tests, then repeats until the run is green, and secrets reach it through stdin rather than on the command line. Sharma had already called the CLI the sleeper hit of Microsoft's recent Logic Apps announcements in an earlier write-up, on the grounds that an agent without a deterministic way to validate and run a workflow is guessing. Named contexts, capability discovery and the handling of secrets were his evidence that someone had designed for that case.
Sonny Gillissen, also a Microsoft MVP, put the same point in terms of a team's week. A new hire clones a repository and has a local runtime up "in minutes, instead of hours." A coding assistant drafting a workflow from a business requirement works "with an authoritative shell instead of assumptions." Integration flows get tested from the CI/CD pipeline instead of by hand. He called the CLI a bridge from today's development process to a fully automated one and, in passing, said an agent could test a workflow locally "without ever touching Azure at all."
That passing remark is the one Christos Panagiotidis, a 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 straight 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 has remote effects, whatever the terminal suggests.
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 designer stays in VS Code. The CLI edits workflow.json directly; it cannot change the state of a running local app, and the pull request's own limits section concedes that Linux CI results prove neither native SDK execution nor execution against live Azure.