Azure Developer CLI extension framework reaches general availability

The Azure Developer CLI (azd) extension framework has reached general availability, providing engineering platform teams and product vendors a stable base for adding custom commands and lifecycle hooks. The framework was introduced in beta; the GA release stabilizes the extension interfaces, adds project-level extension requirements with version constraints, and expands authoring and publishing tooling through the azd x developer extension.

Extensions are modular components that attach to the azd CLI. They can introduce command namespaces, automate multistep workflows, connect to Azure or third-party services, and run logic during lifecycle events such as provisioning, packaging, and deployment. The goal is to consolidate workflows that currently span scripts, documentation, and manual handoffs into guided CLI commands. For example, an extension could scaffold a project with approved infrastructure defaults, register a service in an internal catalog, run validation checks before provisioning, and report deployment metadata after azd deploy. Projects can declare required extensions in azure.yaml with version constraints, and azd installs or verifies them during azd init and before commands like azd up.

Distribution follows a package-registry model. The official extension source is preconfigured with azd, and authors can add private, development, or nightly sources for internal or experimental builds. Extensions can also be packaged as portable .zip bundles for one-off installation from a file path or URL. This model parallels common package registries such as npm or NuGet.

The GA release also includes custom service targets, provisioning providers that can replace Bicep or Terraform, validation checks that can warn or block risky deployments, and MCP server capabilities that expose extension tools to agents and developer tools. Other features in the release include extension management commands, metadata and IntelliSense support, access to azd project and environment context, and lifecycle event handlers.

Microsoft Foundry serves as a working example of the customer-facing model. Its extension suite spans the azd ai namespace, covering project context, hosted agent deployment, connections, tool collections, skills, routines, and an inspector for locally running agents. A fine-tuning extension handles job submission and deployment of fine-tuned models. The suite is modular: developers can install individual extensions or the microsoft.foundry meta-extension, and versions are pinned independently.

The GA milestone applies to the framework itself, not to every extension built on it. Microsoft notes that extension owners release and version features on their own schedules, and some Foundry capabilities remain in preview. Development and nightly sources continue to be intended for experimental builds. This separation keeps the framework stable while individual extensions evolve independently; teams evaluating the framework should check the status of any specific extension they plan to depend on.