Azure Developer CLI 1.25.5 Enhances AI Connection Management and Authentication

The Azure Developer CLI (azd) has received a crucial update with the release of version 1.25.5 on June 5, 2026. This new iteration focuses on enhancing the developer experience by addressing several critical issues and introducing valuable new capabilities. A primary concern resolved in this release pertains to memory exhaustion and slow model catalog loading, particularly when developers utilize Azure CLI delegated authentication. The `azd` team has implemented an in-process token caching mechanism to mitigate the performance impact of concurrent token requests, leading to a more responsive and efficient development workflow. Another significant bug fix targets authentication reporting within the Azure Cloud Shell environment. Previously, the `azd auth status` command would occasionally misreport an unauthenticated state, which could disrupt operations like `azd provision` and `azd ai agent init` that rely on ambient Cloud Shell credentials. Version 1.25.5 rectifies this, ensuring that authentication statuses are accurately reflected, thereby streamlining command execution in Cloud Shell. Beyond these essential bug fixes, the update also brings a notable enhancement to the management of AI connections. Developers can now leverage a new, repeatable `--metadata key=value` flag with the `azd ai connection update` command. This feature provides the flexibility to set or merge metadata on existing AI connections without requiring their complete recreation. This granular control over metadata is vital for better organization, tagging, and programmatic management of AI resources within the Azure ecosystem. Furthermore, the release specifically improves the update process for OAuth2 connections. Prior to this update, attempts to modify OAuth2 connections could result in HTTP 400 errors, often accompanied by the message "Credentials Property can't be empty for auth type OAuth2." Version 1.25.5 addresses this by ensuring that the credentials object is correctly included in the PUT body during update operations. Importantly, it also preserves existing OAuth2 fields, such as `connectorName`, `authorizationUrl`, `tokenUrl`, and `scopes`, when performing target or metadata-only updates, preventing unintended data loss or configuration resets. These collective improvements make the Azure Developer CLI a more robust and reliable tool for modern cloud-native and AI-driven development.