By ByteBot
The Azure SDK for Rust hit 1.0 stable on May 14, closing out a beta phase that came with an honest warning in the README: “large breaking changes may happen.” Seven crates now ship with semver guarantees at v1.0.0. If you have been holding off on Rust for Azure workloads until the foundations were solid, they are now.
What Is Stable
Seven crates graduated to 1.0 in this release:
azure_core— HTTP client, error types, core primitivesazure_identity— Authentication, including the newDeveloperToolsCredentialazure_security_keyvault_secretsazure_security_keyvault_keysazure_security_keyvault_certificatesazure_storage_blobazure_storage_queue
Core, Identity, Key Vault in three flavors, Blob Storage, Queue Storage. That covers the majority of backend workloads: secrets management, file storage, message queuing, and secure authentication. Not comprehensive yet — more on what is still missing below — but enough to build real systems on.
The Credential Story
The most practical addition is DeveloperToolsCredential. In local development, it tries Azure CLI first, then Azure Developer CLI, until one returns a token. If you already run az login as part of your workflow, you need zero additional configuration.
For production, swap it out for ManagedIdentityCredential — same interface, different credential chain. The pattern mirrors the AWS SDK credential chain familiar to developers migrating from AWS. One swap in one line, and local development and production environments are handled cleanly.
Quick Start
Add the dependencies:
cargo add azure_identity azure_storage_blob futures tokio --features tokio/fullList blobs in a container:
use azure_identity::DeveloperToolsCredential;
use azure_storage_blob::BlobContainerClient;
use futures::TryStreamExt;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let credential = DeveloperToolsCredential::new(None)?;
let container = BlobContainerClient::new(
"https://<your-storage-account>.blob.core.windows.net/",
"my-container",
Some(credential),
None,
)?;
let mut pager = container.list_blobs(None)?;
while let Some(blob) = pager.try_next().await? {
println!("{}", blob.name.unwrap_or_default());
}
Ok(())
}That is the full working example. The pager now yields items directly — no manual page management, no index arithmetic. TryStreamExt::try_next() handles the async stream. For full API details, see the azure_storage_blob docs.rs reference.
What Changed from Beta
The Pager API was redesigned between beta and 1.0. The old pattern required manual pagination management. The new one yields items via try_next().await? in a standard Rust async stream pattern. If you were using the beta Pager, you will need to update that code — but you will end up with less of it.
The Poller for long-running operations is now directly awaitable. The MSRV also moved from 1.85 to 1.88 in the pre-GA February release, so check your toolchain if you are upgrading from early beta crates. The official Microsoft Learn docs cover every stable crate with migration context.
What Is Still Missing
Two gaps matter depending on what you are building:
Event Hubs (azure_messaging_eventhubs) is the top priority for the next stable wave. Streaming pipeline work on Azure is waiting on this one.
Cosmos DB (azure_data_cosmos) is in active development and expected to reach stable later in 2026. Teams relying on Azure’s primary NoSQL offering are not fully covered yet.
The roadmap is community-driven — GitHub upvotes determine which services get prioritized. If you need something not yet stable, file or upvote a feature request in the repo.
Bottom Line
Seven crates at 1.0 with semver guarantees is the threshold where serious Rust projects can take a dependency on the Azure SDK without worrying about churn. The credential design is clean. The storage API is idiomatic. The beta warnings are gone.
If you are building on Azure and evaluating Rust — or you have been using the beta crates and waiting for stability — now is the right time to commit. The gaps are known and on the roadmap. For everything in this release, the foundation is solid. Read the full GA announcement on the Azure SDK Blog for the complete list of API changes.
