Microsoft Updates Azure Developer CLI Tools

The latest software releases introduce preview deployment options and critical reliability fixes for developers.

Updated on Oct. 30, 2026 in Software

Isometric editorial illustration of clean, modular server hardware blocks arranged in a grid, representing cloud infrastructure development. — Microsoft has released updates to the Azure Developer CLI, introducing new deployment preview options and reliability fixes for cloud environment management. AI Illustration. Upload story photo >

Live Poll

Do you plan to use pre-deployment inspection tools for your cloud service updates?

Microsoft has released a series of updates for the Azure Developer CLI, covering versions 1.35.0 through 1.37.2. These updates provide new capabilities for inspecting deployment operations and improving environment management.

Why it matters

These tools allow developers to streamline their cloud workflows by verifying deployment plans before committing changes to Azure. The updates also address stability by restoring metadata integrity after interrupted upgrades.

The release includes versions 1.35.0, 1.35.1, 1.36.0, 1.37.0, 1.37.1, and 1.37.2. It features a breaking migration for Go APIs that now requires custom implementations for error checking.

The players

Microsoft

A global technology company that develops and maintains the Azure cloud computing platform and associated developer tools.

The details

Developers can now use the azd deploy --preview command to inspect target configurations for services like App Service, Container Apps, and Azure Kubernetes Service without executing the deployment. Additionally, the new azd env unset command allows for the removal of environment keys, provided the --force flag is used for noninteractive operations.

Microsoft released these Azure Developer CLI updates on October 30, 2026.

The Tech Race

This release follows the ongoing development of the Azure Developer CLI as it matures into a comprehensive tool for managing cloud-native application lifecycles. It positions Microsoft to better compete with other infrastructure-as-code providers by emphasizing developer safety and verification.

Developers can now avoid costly deployment errors by using the preview flag to check their target configurations before running live jobs. Users of the Go API should prepare to update their custom error-handling logic to maintain compatibility with the new version requirements.

The takeaway

Developers should prioritize testing the preview command on non-production environments to understand how it interprets their specific service configurations. It is also recommended to review existing Go codebases for potential breaking changes introduced by the new API migration requirements.