Microsoft Releases Azure SDK for June 2026, Rust Hits GA
Microsoft has shipped the Azure SDK for June 2026, and this month's update carries more weight than usual. The headline is straightforward: the Azure SDK for Rust finally reaches version 1.0.0. Alongside it, Python gets its first stable AI Transcription client, Planetary Computer Pro lands at GA, and the Azure Functions MCP extension rounds out its native primitive set.
Rust developers have been waiting for this milestone. The new 1.0.0 release stabilizes seven crates: azure_core, azure_identity, three Key Vault packages, and the Storage Blob and Queue clients. The API surface is locked in with semver guarantees now, Microsoft says. Since the beta window, the team redesigned the Pager and Poller patterns, added ManagedIdentityCredential, and bolted on OpenTelemetry observability. Pluggable async runtimes made it in, too.
Python Libraries Cross the Finish Line
The Python side of the release is practical rather than flashy. azure-ai-transcription hits 1.0.0 (GA), giving developers a fully supported SDK for the transcription service without the usual preview-label uncertainty. Microsoft Planetary Computer Pro lands at 1.0.0 alongside it, introducing richer response models like AssetStatisticsResponse and QueryableDefinitionsResponse. Keep in mind that one breaking change carried straight through to stability: StacOperations.list_collections is now get_collections. If your CI already pinned the old name, you'll want to patch it before you redeploy.
The MCP ecosystem around Azure Functions is finally shipping the complete primitive set. Tools, resources, and prompts are all native triggers now, and the extension supports .NET, Java, Python, TypeScript, and JavaScript. Authentication wires up through Microsoft Entra ID with one-click portal configuration. There's a fluent builder API in .NET, structured content fields for JSON alongside text responses, and the ability to return rich HTML directly from tool outputs. It's clearly aimed at developers building remote MCP servers that actually need enterprise auth.
The Azure Developer CLI has been on a tear. Nine releases between May and June, including a new azd tool command for discovering and managing language SDKs, Bicep, Docker, and VS Code extensions. azd exec lets scripts inherit the full provisioned environment, including Key Vault secret resolution. Multi-layer provisioning got explicit dependsOn support, and Go Functions are now deployable via azd up. A self-contained extension packing system landed too, which should finally make sharing custom azd workflows less clunky.
On the infrastructure side, direct streaming from Azure Blob Storage straight into GPU memory is getting serious. Integrated into vLLM and SGLang, the Run:AI Model Streamer cuts load times dramatically. On an 8x H100 setup, a 122B parameter model dropped from 225 seconds to 37. That's a 6x speedup. No disk hop means fewer bottlenecks when spinning up inference servers. Auth uses DefaultAzureCredential, which tracks with the rest of the SDK's identity patterns.
Security updates rolled in quietly. The Java Cosmos DB client (azure-cosmos 4.79.0) patches a critical remote code execution vulnerability caused by unsafe deserialization. Microsoft swapped it for JSON serialization. Also, Node.js 20.x hits end-of-support on July 9. After that date, the minimum engine requirement for official Azure SDK packages moves to Node.js 22.x. Old libraries will likely keep working, but you won't get support tickets filed against EOL runtimes.
Azure SDK Release (June 2026)
Azure SDK releases every month. This post includes the June 2026's highlights and release notes.
