A developer codes a cloud database SDK as a diagram highlights partition routing, security, and an SDK release.
Rust developers who use Azure Cosmos DB for NoSQL now have a stable, production-ready native client. Microsoft's Azure Updates feed lists the Azure Cosmos DB SDK for Rust as "Launched" on November 17, 2026. Microsoft uses that label for a fully released, production-ready product available to all Azure customers. Preview crates are common in Rust, and so is the risk of building on one. This release removes that risk for teams that wanted to use Cosmos DB from Rust.

A developer codes a cloud database SDK as a diagram highlights partition routing, security, and an SDK release. What Microsoft announced​

The Cosmos DB team's Ignite 2026 roundup, dated November 17, describes the SDK as a native Rust client for Azure Cosmos DB for NoSQL. The same post says built-in retries, partition-level failover, circuit breaking and efficient binary encoding are meant to reduce the custom resilience code applications need. That feature list comes from Microsoft's announcement, and I haven't tested it myself.

The scope is Azure Cosmos DB for NoSQL. Nothing I reviewed extends this SDK to the MongoDB, Cassandra, Gremlin or Table APIs.

The Cosmos DB post also cites a customer example. OpenAI reportedly moved its Habitat storage service from Python to Rust and saw 6x better CPU efficiency and 15x better memory efficiency. That is Microsoft's account of one customer's rewrite. It does not predict what your own workload will gain from the SDK.

The release trail​

The GA label follows a stable release made a few weeks earlier. The monthly Azure SDK release post for October 28, 2026 lists Cosmos DB 1.0.0 for Rust, with the Cosmos DB Client Driver and the SDK Macros crates, as its first stable release. The crates are:

  • azure_data_cosmos 1.0.0
  • azure_data_cosmos_driver 1.0.0
  • azure_data_cosmos_macros 1.0.0

The 1.0.0-beta.1 builds of the same crates are listed alongside them. The registry entry for azure_data_cosmos shows a minimum Rust version of v1.88.0. The updated Microsoft Learn quickstart agrees and lists Rust 1.88 or later. An older quickstart version said Rust 1.80, so check which one you are reading.

Upgrading from preview​

Microsoft's release notes list several breaking changes for anyone on a preview build:

  • Feature flags. The preview_dtx, preview_patch and preview_opentelemetry flags are renamed unstable_dtx, unstable_patch and unstable_opentelemetry.
  • Credentials. CosmosCredential::MasterKey becomes CosmosCredential::AccountKey.
  • User-Agent. The header format changed to azsdk-rust-cosmos/{sdk-version} (drv=…; os; arch; rustc …). If you filter or parse this header in logs or proxies, check your rules.
  • Error mapping. Terminal service errors 404/1002, 403/3 and 403/1008 now surface as synthetic 503/20310, 503/20311 and 503/20312 errors. The original wire error stays available through source(). Retry and alerting logic that matches on status codes may need updating.
  • Partition topology cache. The cache can no longer be disabled. A Lazy mode keeps the earlier first-use loading behavior. By default, container resolution now loads the full topology and fails if it can't get a valid routing map.
  • Public API changes. Several types were removed or reshaped. ConsistencyLevel and CosmosClientOptions are gone, so use ReadConsistencyStrategy and typed operation options. Some duration accessors now return Option<Duration>. Throughput values use u64, so RU/s figures above 4 billion fit.

Not everything is stable. The updated quickstart says OpenTelemetry support and patch operations remain in preview and aren't recommended for production. The unstable_ prefix on those flags is a signal to take seriously. The 1.0.0 label covers the default feature set, not every flag.

Getting started​

The updated quickstart, last updated November 17, builds against 1.0.0 and covers these steps:

  1. Create a project with cargo new.
  2. Add [email][email protected][/email] and [email][email protected][/email] with cargo add.
  3. Add serde, tokio and futures for serialization, async execution and query iteration.
  4. Authenticate with DeveloperToolsCredential and set AZURE_COSMOS_ENDPOINT and AZURE_COSMOS_REGION. For Azure-hosted production apps, the quickstart recommends a managed identity instead.
  5. Build a CosmosClient and get a DatabaseClient and ContainerClient.
  6. Upsert an item with a partition key, point-read it by ID and partition key, and run a parameterized query.

The quickstart assumes a cosmicworks database and a products container partitioned on /category. Those are only sample names. It also assumes an identity with the Cosmos DB Built-in Data Contributor role. A successful run prints the item you read back and the query results.

Caveats​

  • Stale documentation. Search snapshots of the Learn quickstart can still show an older version. That version calls the SDK a public preview and warns against production use. The page Microsoft updated on November 17 describes 1.0.0 as generally available. If you see the preview warning, check the page's last-updated date.
  • Scope of "GA". It describes the release state. It doesn't establish region-by-region availability or support for every platform and runtime.
  • Older crates. The Azure SDK for Rust repository says the current project succeeds the azure_sdk* crates from MindFlavor's community project. It says the renamed older crates should be considered fully deprecated. The sources I reviewed don't document a migration path between the two.

Why it matters​

Rust has been an Azure SDK second-class citizen for a while. The azure_data_cosmos crate went through dozens of breaking versions, and a March-era SDK release table listed its next stable as Q2-2026. A 1.0.0 release with a stability commitment, plus a quickstart written for it, lets teams adopt it with more confidence.

Before upgrading, pin versions, read the changelog, and test the retry and error-handling paths against the new synthetic 503 mapping. Preview users should expect to edit Cargo.toml and a few call sites. The stability promise that comes with 1.0.0 is likely to be worth the effort.

 

References

  1. (Launched) Generally Available: Azure Cosmos DB SDK for Rust Azure Updates 2026-11-17T20:00:32Z
  2. Azure Cosmos DB SDK for Rust. crates.io
  3. Azure SDK for Rust (October 2026) | Azure SDKs azure.github.io