> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Enable Autoscale on Azure Cosmos DB Container

> Switch Cosmos DB databases or containers with spiky traffic from fixed throughput to autoscale.

With standard (manual) provisioned throughput, Cosmos DB bills the RU/s you set for every hour, however little is used. With autoscale, throughput scales between 10% and 100% of a maximum and you are billed for what it scales to. Azure Advisor recommends autoscale for databases and containers whose usage would cost less that way, and nOps shows these recommendations with the estimated monthly saving.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Database |
| **Service** | Azure Cosmos DB |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | Azure Advisor |

## Why it matters

Throughput is usually set for the busiest hour. When most hours are quiet, autoscale stops you paying for the peak all day.

## How nOps finds it

This recommendation comes from Azure Advisor, which compares the container's past throughput use with what autoscale would cost and suggests a maximum RU/s. nOps imports Advisor's recommendations daily and checks each one against your own Azure bill for the last 7 complete days: the resource must still be billed in the last 3 days of that window, and Advisor's estimate is capped at what the Cosmos DB account actually cost (Advisor prices at pay-as-you-go rates, so you may pay less through discounts, reservations or savings plans). Recommendations worth less than \$1 a month are left out.

## Before you start

Permission to change throughput on the Cosmos DB account.

## How to implement

1. In the Azure portal, open the Cosmos DB account, then **Data Explorer**, and select the database or container.
2. Open **Scale & Settings** (or **Scale**), choose **Autoscale**, and set the maximum RU/s shown in the recommendation. Save.
3. Or use the Azure CLI, for example `az cosmosdb sql container throughput migrate --throughput-type autoscale ...` and then set the maximum with `az cosmosdb sql container throughput update --max-throughput MAX_RU ...`.
4. Update Terraform, Bicep or ARM templates (`autoscale_settings` with `max_throughput`) so a later deployment does not switch it back.

## Risks and considerations

* Each autoscale RU/s costs more than a standard RU/s, so autoscale only saves money when usage is often well below the peak.
* Autoscale never goes below 10% of the maximum.
* Reserved capacity bought for standard throughput applies differently to autoscale.
* To roll back, migrate the throughput back to manual.

## Related

* [Remove Unneeded Regions from Cosmos DB Accounts](https://help.nops.io/inform/supported-recommendations/remove-unneeded-regions-from-cosmos-db-accounts)
* [Reduce Cosmos DB Periodic Backup Copies to the Free Two](https://help.nops.io/inform/supported-recommendations/reduce-cosmos-db-periodic-backup-copies-to-the-free-two)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.