Az cosmosdb sql container throughput migrate
← Back to DP-420 Terminology Reference
Category: Throughput & Scaling
Summary: CLI: switches a container between manual and autoscale throughput.
Overview
The Azure CLI command 'az cosmosdb sql container throughput migrate' switches a container's throughput mode between manual Provisioned Throughput and Autoscale Throughput (in either direction), without any downtime or data movement. This is the CLI equivalent of the 'Switch to autoscale' or 'switch to manual throughput' option in the Azure portal's Scale tab.
More Info & Links
DP-420 Style Practice Questions
Q1. What does 'az cosmosdb sql container throughput migrate' do?
- A. Switches a container's throughput mode between manual (Provisioned Throughput) and Autoscale Throughput
- B. Redistributes RU/s unevenly across physical partitions
- C. Deletes and recreates the container with new throughput
- D. Migrates data from one container to another
Q2. Does migrating throughput mode with this command cause downtime or data loss?
- A. No, the migration happens without downtime or data movement
- B. Yes, the container must be recreated
- C. Yes, all data must be manually re-imported
- D. Only if the account uses multi-region writes
Answer Key
Answers are listed at the very end so you can attempt the questions first.
- Q1 (az cosmosdb sql container throughput migrate): A. Switches a container's throughput mode between manual (Provisioned Throughput) and Autoscale Throughput — This command migrates the throughput mode itself (manual vs. autoscale), not the container's data.
- Q2 (az cosmosdb sql container throughput migrate): A. No, the migration happens without downtime or data movement — Throughput mode migration is a live, in-place operation and does not require downtime or moving data.
DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page
