Azure SDK Release (November 2025)

Thank you for your interest in the new Azure SDKs! We release new features, improvements, and bug fixes every month. Subscribe to our Azure SDK Blog RSS Feed to get notified when a new release is available.

You can find links to packages, code, and docs on our Azure SDK Releases page.

Release highlights

Azure Storage updates across multiple languages

This month brings significant stable updates to Azure Storage libraries across multiple languages and services, all adding support for the new service version 2025-11-05. The .NET Storage Blobs library (12.26.0) and Java Storage Blobs library (12.32.0) now return enhanced error information (CopySourceStatusCode, CopySourceErrorCode, and CopySourceErrorMessage) from copy operations, along with improved x-ms-version mismatch error messages. The .NET Storage Queues (12.24.0) and Java Storage Queues (12.27.0) stable releases add ApproximateMessagesCountLong to correctly handle message counts greater than max int. The .NET Files Shares (12.24.0) and Java Files Shares (12.28.0) stable releases add bearer token challenge support and fix bugs with exists methods. The C++ SDK also released stable updates for Blobs (12.15.0), Files Shares (12.15.0), Files Data Lake (12.13.0), and Queues (12.5.0). The Go SDK also updated to service version 2025-11-05 with azblob (1.6.3), azfile (1.5.3), azdatalake (1.4.3), and azqueue (2.0.0).

Identity Binding now supported in the Azure Identity libraries

The existing workload identity feature for Azure Kubernetes Service (AKS) has scale limitations because a single user-assigned managed identity (UAMI) can’t have more than 20 federated identity credentials (FICs). Large Kubernetes platform deployments might span more than 20 clusters (each cluster has a unique issuer) or have many <namespace, service-account> combinations that require mapping to the same UAMI, exhausting the FIC quota.

Identity Binding is an evolution of workload identity on AKS focused on scalability and operational simplicity. For workloads that require Microsoft Entra authentication from AKS, Identity Binding is recommended when you need to reuse the same UAMI across multiple clusters while staying within the FIC limit.

You can now use Identity Binding with your application workloads via one of the following packages:

Language	Package	Minimum version	How to enable
.NET	Azure.Identity	v1.18.0-beta.2 or later	`WorkloadIdentityCredential` identity binding mode is disabled by default. Set `WorkloadIdentityCredentialOptions.IsAzureKubernetesTokenProxyEnabled` to `true`.
Go	azidentity	v1.14.0-beta.2 or later	Set `WorkloadIdentityCredentialOptions.EnableAzureTokenProxy` to `true`.
Java	azure-identity	v1.19.0-beta.1 or later	Call `enableAzureTokenProxy()` on `WorkloadIdentityCredentialBuilder`.
JavaScript	@azure/identity	4.14.0-beta.1 or later	Set `enableAzureKubernetesTokenProxy` to `true` in `WorkloadIdentityCredentialOptions`.
Python	azure-identity	1.26.0b1 or later	Set `use_token_proxy=True` in `WorkloadIdentityCredential`.

Azure Cosmos DB performance and feature enhancements

The stable Java Cosmos DB SDK (4.75.0) now supports per-partition automatic failover dynamically without requiring application restart. This version also includes improvements to the Change Feed Processor with better exception logging and fixes for NullPointerException issues. The stable Python Cosmos DB SDK (4.14.0) adds semantic reranking as a preview feature and the ability to return database/container proxies with properties through a new return_properties parameter.