Azure SDK Release (November 2025): New Storage Enhancements & Identity Improvements
Azure continues its steady pace of development with another update cycle for its Software Development Kit (SDK). This latest release, focusing on November 2025 service versions, brings several important updates across different languages and services.
The big news in the Storage library is support for Azure Storage's newest API version: 2025-11-05. This isn't just a minor point; it means developers working with .NET or Java can now handle data transfers more reliably as they leverage Azure Storage features. They've also fixed some long-standing issues, particularly concerning copy operations and errors related to mismatched versions (those pesky x-ms-version things). These fixes result in much clearer error messages overall, which is a huge win for diagnosing problems quickly.
Beyond the Storage Blobs updates, other services got solid new releases too. .NET's Storage Queues jumped to version 12.24.0, and Java followed suit with 12.27.0. These bring benefits like a better ApproximateMessagesCountLong option for managing large message queues, support for handling bearer tokens securely, plus various bug fixes smoothed the development path.
Looking at C++, the release offers stable updates for Blobs (12.15.0), Files Shares (12.15.0), and Queues (12.5.0). Go developers saw improvements too with packages like azblob, azfile, and azqueue hitting version 2025-11-05.
One of the most significant updates this time is called Identity Binding, specifically within Azure Kubernetes Service (AKS). This comes right after addressing limitations in workload identity – a feature that helps securely authenticate workloads running on AKS. Workload identity currently has a major drawback: it limits you to 20 federated identity credentials per user-assigned managed identity (UAMI).
Identity Binding tackles that specific issue head-on. It's designed as an improvement over the existing workload identity setup, making operations simpler and boosting scalability significantly.
To use Identity Binding properly, developers need to update their Azure.Identity package depending on which language they're using, and then adjust some configuration settings accordingly:
- For .NET users: Update Azure.Identity to version v1.18.0-beta.2 or later, and explicitly enable the token proxy feature by setting WorkloadIdentityCredentialOptions.IsAzureKubernetesTokenProxyEnabled to true.
- Go developers should update azidentity (v1.14.0-beta.2 or later) and set EnableAzureTokenProxy.
- Java users need azure-identity (v1.19.0-beta.1 or later) with the appropriate call to enable token proxy via enableAzureTokenProxy().
- JavaScript requires @azure/identity at 4.14.0-beta.1 or later, where you simply set enableAzureKubernetesTokenProxy in the options.
- Python developers require azure-identity (1.26.0b1 or later) and must activate it by setting use_token_proxy.
Finally, the stable Cosmos DB SDK also received attention: Java version 4.75.0 now includes dynamic automatic failover configuration across partitions – a useful tool for building resilient apps without downtime during Azure maintenance events. Python's stable release (4.14.0) adds a preview feature called semantic reranking and offers new control over proxy properties with the return_properties flag.
Azure SDK Release (November 2025)
Azure SDK releases every month. This post includes the November 2025's highlights and release notes.
