APPLIES TO: 
NoSQL
Throughput buckets in Azure Cosmos DB allow users to control the throughput available for different workloads within a container. By configuring buckets and setting a maximum throughput allocation, users can ensure workload isolation. If a bucket exceeds its assigned throughput limit, subsequent requests are throttled to prevent impact on other workloads.
How many throughput buckets can be configured per container?
You can configure up to five (5) throughput buckets per container.
Can I assign custom names to throughput buckets?
No, throughput buckets can't be named. They're automatically assigned an ID ranging from 1 to 5.
What happens if a bucket exceeds its configured maximum throughput?
Subsequent requests sent to that bucket receive an HTTP 429 status code with substatus code 3212.
What happens if I delete an existing bucket?
Requests sent with a deleted bucket ID (1-5) won't fail, however they consume throughput from the overall container.
What if I assign a bucket ID lower than 1 or higher than 5 to a request?
Requests with an invalid bucket ID (less than 1 or greater than 5) results in an error, as only bucket IDs 1 to 5 are valid.
Is there any minimum throughput limit for a throughput buckets?
There's no minimum limit for throughput buckets. Throughput isn't reserved for any bucket, and the total throughput of the container is shared among all buckets.
How often can throughput buckets be modified?
Throughput bucket configurations can be changed once every 10 minutes, otherwise the request is throttled with an HTTP 429 status code and substatus code 3213.
Next steps
- Learn more about Throughput buckets