Azure Developer CLI October 2026 Release Introduces Deployment Previews
The October 2026 updates for the Azure Developer CLI cover releases 1.35.0 through 1.37.2, introducing deployment previews, environment variable management changes, and extension API stabilizations. The release also includes multiple bug fixes, dependency updates, and security improvements.
What changed From the source
The October 2026 updates for the Azure Developer CLI encompass versions 1.35.0, 1.35.1, 1.36.0, 1.37.1, and 1.37.2. A major feature introduced this month is the azd deploy --preview command, allowing developers to inspect deployment targets for App Service, Container Apps, Functions, Static Web Apps, Azure Kubernetes Service, and AI endpoints prior to execution, providing structured target and host details in JSON format.
Container image deployments are now supported for Azure Container Apps express environments via the containerapp host, which uses an image-based strategy without setting custom revision suffixes or traffic weights. Environment management gains a beta azd env unset command for removing case-sensitive stored keys while safeguarding AZURE_ENV_NAME, requiring the --force flag for non-interactive execution. Pipeline configuration commands can now generate GitHub Actions and Azure Pipelines definitions that install necessary extension-defined infrastructure providers.
For extension authors, deployment preview contracts and SDK APIs graduate to stable v1 in version 1.37.0. Stable v1 APIs are also introduced for extension usage telemetry and Azure principal lookups. A breaking change for Go developers involves the environment and state path APIs, where exported functions now return errors that must be checked and propagated, and state.NewStateCacheManager now requires an *azdcontext.AzdContext instead of an environment-directory string.
Numerous bug fixes address extension installation rollbacks, Ctrl+C cancellation propagation, process exit code preservation, and incorrect progress line repetitions. Workflow fixes improve provisioning permission checks, Deployment Stacks deny-list validation, and shell expression evaluations in azd exec --shell. Core dependencies were updated, including gRPC v1.84.0, OpenTelemetry v1.47.0, GitHub CLI v2.102.0, Microsoft Authentication Library for Go v1.10.1, and Bicep CLI v0.48.1.
- Preview deployments via azd deploy --preview across multiple target services.
- Deploy to Container Apps express environments using containerapp host.
- Remove stored environment configuration using the beta azd env unset command.
- Stable v1 extension SDK support for service-target deployment previews, telemetry, and principal lookup.
- Environment and state Go API updates returning explicit errors.
At a glance · Azure
What changedWhy it mattersWho should careUpgrade and migration considerations
Why it matters Analysis
The addition of deployment previews significantly improves confidence when pushing changes to production or staging environments by letting developers verify resolved targets beforehand. Container Apps express support streamlines application delivery for lightweight architectures. Meanwhile, the stabilization of extension SDK APIs and telemetry contracts offers extension authors a reliable foundation for building custom tooling without facing abrupt breaking changes in core integration points.
- Greater visibility into infrastructure changes before deployment execution.
- Stronger API contracts for extension creators building third-party tooling.
- Enhanced environment variable safety through explicit removal commands and strict Go API error propagation.
Who should care Analysis
Professional .NET and general cloud developers utilizing the Azure Developer CLI for CI/CD pipelines and local terminal workflows will benefit from safer deployment workflows and cleaner environment variable controls. Extension developers writing custom plugins must review the updated SDK contracts and stable v1 namespaces. Additionally, Go developers maintaining custom tooling or extensions built on top of azd internal packages need to address the breaking environment and state path API changes.
- Developers and DevOps engineers utilizing azd for cloud deployments.
- Authors and maintainers of azd extensions and custom plugins.
- Go developers consuming internal azd context, state, or environment path APIs.
Upgrade and migration considerations Analysis
Teams upgrading to the latest azd releases must account for Go API changes regarding environment and state paths. Custom implementations and mocks must be updated to check and propagate returned errors. Furthermore, calls to state.NewStateCacheManager must pass an *azdcontext.AzdContext constructed from the project directory rather than the .azure directory.
The source material notes that this release includes security improvements and encourages users to upgrade, though specific migration timelines or automated migration tooling are not detailed.
- Update custom Go code and mocks to handle path API error returns.
- Pass *azdcontext.AzdContext instead of directory strings to state.NewStateCacheManager.
- Review non-interactive scripting that utilizes azd env unset to ensure the --force flag is included where necessary.
Sources and further reading
- Original post on Azure SDK Blog (original source)
Original: “Everything released in October 2026 for Azure Developer CLI”, Azure SDK Blog, published 30 Oct 2026, retrieved 30 Oct 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.