InfoQ Counts 64 Commands in Azure's Logic Apps Standard CLI Preview; the Extension's Notes Say 59, and Learn's Command Table Marks Them GA

InfoQ reports the logicapp Azure CLI extension preview adds 19 groups and 64 commands; its README and release history say 59, and Microsoft Learn's table marks them GA.

Verified pipeline

Sources: 8 Publisher: signed Contributor: signed Hash: 69d2032a25 View

Editor's Note · November 13, 2026

Correction:

The article says "Of 94 rows" on the Learn az logicapp command reference, 78 are typed Extension and 16 typed Core. The table has 95 rows: 78 Extension, 16 Core and one typed "Core and Extension" (az logicapp deployment, status GA, a group that contains the extension's deployment package command). Its statement that the 19 groups match InfoQ's figure holds only for rows typed Extension; counting every row with commands beneath it, including the shared deployment row, gives 20 groups that contain extension commands.

Clarification:

The article reports that the extension's README says 59. The same README also refers once, in its testing section, to "55-command extension surface" remaining independently asserted, a third figure the article does not mention and does not explain. The README's 59 appears in the sentence "The complete extension contributes 59 leaves"; the release history gives only 59.

Overview

InfoQ reports, in an article dated November 12, 2026, that “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.” The stated purpose is that a Standard workflow “can be created, run, and tested without Visual Studio Code.” The sources the Herald read give different command counts for the extension: InfoQ says 64, while the extension’s own README and release history say 59. Microsoft Learn’s command table labels the extension’s commands GA, while Learn’s extension list labels the extension Preview.

What InfoQ Describes

According to InfoQ, the extension “adds 19 command groups with 64 commands beside the thirteen existing cloud-management commands, which it leaves untouched.” The article lists project creation, workflow authoring, a local runtime, connector and connection management, run inspection and test scaffolding. It says runtime start, stop and show manage a local host on port 7071 and launch the Azurite storage emulator when a project uses development storage.

InfoQ says the runtime doctor command only reads local state and “never installs, downloads, starts, stops, repairs, decrypts settings, changes context, or contacts cloud storage.” Of the test commands, it says test run is “the only command that builds and runs them, under a deadline.” Microsoft’s Learn page for the az logicapp project group says the extension “will automatically install the first time you run an az logicapp project command,” which fits InfoQ’s description of automatic installation.

InfoQ discusses the views of three people it describes as Microsoft MVPs. It says Sagar Sharma wrote on LinkedIn that this is deliberate, and in its account of his post the CLI is “literally pitched as adding determinism to local AI-assisted coding.” It says Sonny Gillissen described a new hire getting a local runtime up “in minutes, instead of hours” and a coding assistant working “with an authoritative shell instead of assumptions.” Of Christos Panagiotidis, InfoQ says “His pilot plan is explicitly a proposal rather than a report of a run,” and that his cautions come from Microsoft’s own walkthrough, which uses live Azure and Microsoft 365 resources and includes commands that change deployed connections, “so a local run has remote effects, whatever the terminal suggests.”

InfoQ also reports limits: 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.”

Where the Sources Differ

Command count. InfoQ says 19 groups and 64 commands. The extension’s README says the complete extension contributes “59 leaves,” and the release history for version 1.0.0b1 describes the “complete 59-command Logic Apps Standard preview.” The pull request that added the extension, which GitHub’s API shows merged at 2026-10-22 00:38 UTC, says “59 extension leaves” and refers to “the original 38-command extension.”

The Herald counted rows on the Learn command reference for az logicapp on November 13 (the Herald’s own count). Of 94 rows, 78 are typed Extension; of those, 19 have other rows listed beneath them and 59 do not. Of the 16 rows typed Core, 13 have none beneath them. Those figures match InfoQ’s 19 groups and thirteen existing commands if a group is a row with commands beneath it, a definition InfoQ does not give, and they match the 59 in the repository. None of the other cited pages gives 64 as a command count, and none explains InfoQ’s figure. The Herald does not reconcile the two counts.

Status. The README calls the extension a “Preview Azure CLI extension,” and says “Production readiness has not been established,” advising non-production resources for evaluation. Learn’s extension list shows logicapp with the status Preview and 1.0.0b2 in its release-notes column. The Learn command table, by the Herald’s count, gives every one of the 78 extension rows the status GA. The same pattern appears for another extension: Learn’s list marks acat Preview, and the Herald counted 17 rows on its az acat report page, all typed Extension with the status GA. None of the Learn pages cited here explains the difference between the table and the list.

What the Sources Do Not Say

None of the cited sources gives a general-availability date for the extension. InfoQ says “Microsoft has said a broader command surface will follow soon,” without saying where or when Microsoft said it.
InfoQ does not say how it arrived at 64 commands.