A blue illustration depicts encrypted cloud data flowing into a secure vault above a connected global network.
Azure Backup for Azure Cosmos DB is now generally available. Microsoft's Azure Updates feed marks it "Launched" with a November 17, 2026 timestamp. That label means fully released, production-ready status for all Azure customers, not a limited rollout. The details below come from Microsoft's own documentation.

Cosmos DB backup has had a gap for a while. The database is built for globally distributed, high-throughput workloads. Its native backups are designed for short-term operational recovery, not for compliance retention or for surviving a compromised account. This release is aimed at that gap.

A blue illustration depicts encrypted cloud data flowing into a secure vault above a connected global network. From preview to GA​

Microsoft's Cosmos DB engineering blog says the public preview was announced on June 2, 2026. Microsoft's Azure Backup "What's new" page lists vaulted backup support for Cosmos DB as generally available, and it keeps the earlier preview entry. That page excerpt doesn't give a date for the GA entry. The November 17 date therefore rests on the Azure Updates timestamp alone.

I couldn't read the Azure Updates item body. The page rendered only a generic listing. Everything below is therefore from the Learn documentation, not from the announcement text.

What the service does​

Microsoft's overview says Azure Backup integrates with Cosmos DB's transactionally consistent backup streams and transfers scheduled backups into a Backup vault, guided by a backup policy. Practical details:

  • Scope: Backups are taken at the account level and include all databases and containers in the account.
  • Schedule: A typical policy takes one full backup per week and an incremental backup on each remaining day. That gives a one-day recovery point objective (RPO).
  • Policy rule: Every policy must include a weekly full backup. Incremental-only policies aren't supported.
  • Retention: Microsoft documents long-term retention of up to 10 years.
  • Reliability: If a scheduled backup fails because of a transient issue, Azure Backup retries it automatically (auto-heal). The retried jobs show up in the Backup jobs view.

The auto-heal behavior has limits. The support matrix says it covers scheduled backups only, and only for specific transient errors. On-demand backups aren't retried.

Why a vault matters​

The backup data sits in a Backup vault, separate from the source account. Microsoft lists these protections:

  • Logical and administrative isolation from the source account.
  • Microsoft-managed storage that the source account can't reach.
  • Configurable redundancy: LRS, ZRS or GRS.
  • WORM immutable storage.
  • Soft delete, Azure RBAC, multi-user authorization for critical actions, and encryption at rest and in transit.

Microsoft's stated rationale is that Azure Backup functions in parallel with the native Cosmos DB backup capabilities and doesn't replace them. Native continuous or periodic backups cover up to 35 days of operational recovery. Vaulted backups cover audit, compliance and ransomware scenarios.

Immutability has a caveat for admins. Microsoft's immutable vault documentation says that where WORM storage isn't yet available for a region or workload, the backup service still enforces locked immutability. Backups then move to WORM-backed storage automatically once it becomes available. Cosmos DB is listed among the Backup vault workloads that support immutability.

Check eligibility before you plan around it​

GA doesn't mean every Cosmos DB account qualifies. Microsoft's support matrix sets these boundaries.

AreaDocumented position
CloudsAll Azure public regions. National clouds and sovereign regions aren't supported.
API and throughputNoSQL or MongoDB API accounts using provisioned Request Units.
Backup modeOnly accounts in continuous (PITR) backup mode.
SizeUp to 2,500 partitions, roughly 125 TB.
Region alignmentThe primary write region must match the Backup vault region. It must also match the account's deployment region.
Unsupported configurationsNetwork Security Perimeter, hierarchical partition keys, and Per-Partition Automatic Failover.
Restore targetEmpty, single-region account with the same API type. It can't be Serverless and can't have a throughput limit configured.
Restore reachCross-subscription restore, and cross-region restore to an Azure paired region.
GranularityNo item-level restore of individual databases or containers. Recovery is at account scope.

Two further constraints:

  • Restoring an incremental recovery point needs an intact chain: the parent full backup plus all intervening incrementals.
  • On-demand backups are full backups only.

Account-level recovery is the limit I'd raise first with application owners. If one container is corrupted, you can't pull back just that container from the vault. You restore the whole account to a new, empty target, then work out how to reconcile the data. Plan that runbook before you need it.

If your account uses periodic backup, Microsoft's Cosmos DB documentation says long-term protection requires continuous backup (PITR). It advises migrating the account to continuous mode before enabling it.

Setting it up in the Azure portal​

Microsoft's guide starts with prerequisites:

  1. Review the supported scenarios and limitations.
  2. Identify or create a Backup vault in the same region as the account.
  3. Identify or create a backup policy for Cosmos DB.
  4. Review the permissions needed to assign the Cosmos DB Long Term Retention Backup Role over the source account to the vault.

The portal steps are:

  1. Go to Resiliency, then Overview > Configure protection. Alternatively, go to Backup vault > Overview and select Backup.
  2. Set Resource managed by to Azure, Datasource type to Azure Cosmos DB and Solution to Azure Backup. Select Continue.
  3. On the Basics tab, choose the vault, then select Next.
  4. On the Backup policy tab, choose the policy that sets schedule and retention, then select Next.
  5. On the Datasources tab, select the datasource name and pick the Cosmos DB account.
  6. Confirm the account's primary write region matches the vault region.
  7. Let Azure Backup validate permissions. When validation shows success, select Next, then Configure backup on the Review + configure tab.

When validation finds missing permissions, you get one of two messages:

  • User cannot assign roles means you lack write access on the Cosmos DB account. Download the role assignment template (an ARM template) and have an administrator run it.
  • Role assignment not done means you do have write access. Select Assign missing roles to grant permissions inline.

Success looks like a protected item being created. Microsoft's tutorial also covers running an on-demand backup from Protected items. It covers tracking jobs on the Jobs pane, filtered by Azure Cosmos DB as the datasource type.

Common failure points​

Microsoft's Cosmos DB documentation lists error codes with fixes. Examples:

  • Account not online: the account isn't in the Online state, so the operation can't run.
  • Region mismatch: the write region doesn't match the account's ARM location. Cross-region backups from such an account aren't supported, so align the regions before retrying.
  • Empty account: no databases or collections were found at the backup timestamp. Microsoft says to contact Azure Support.
  • Periodic backup mode: migrate to continuous backup first.
  • Restore API mismatch: the target account's API type doesn't match the backup source.

What it costs​

Microsoft says Cosmos DB vaulted backup incurs charges from July 1, 2026, in three parts:

  • A fixed Protected Instance fee per protected account, based on the size of the source data.
  • A backup storage fee per GB per month.
  • A restore fee based on the volume of data restored.

I haven't verified current rates. Use the Azure Backup pricing page and the pricing calculator for estimates. Remember that restore fees only appear during an incident, so include them in your worst-case budget.

Who should care​

If you run business-critical Cosmos DB accounts, particularly ones covered by retention rules, this fills a real gap. It also helps teams that already use Azure Backup for VMs, blobs, AKS or PostgreSQL. They can now put Cosmos DB under the same vault, policy and governance model.

Before you enable it, work through this list:

  • Confirm the account is in continuous backup mode.
  • Verify the API type, the RU model and the region alignment.
  • Check for unsupported features such as NSP, hierarchical partition keys and PPAF.
  • Decide who holds MUA authority and whether to lock the vault's immutability.
  • Rehearse an account-level restore to an empty target.
  • Model the storage and restore costs.

The documentation pages I used were updated between August and October 2026. Microsoft may change support boundaries, so recheck the live support matrix before you design around any of them.

 

References

  1. (Launched) Generally Available: Azure Backup for Azure Cosmos DB Azure Updates 2026-11-17T20:00:32Z
  2. Azure Backup for Azure Cosmos DB Public Preview Adds Immutable Backups and Long-Term Retention - Azure Cosmos DB Blog devblogs.microsoft.com
  3. About Azure Cosmos DB vaulted backup learn.microsoft.com