documentdb-storage
/documentdb-storage
Storage configuration guidance for Azure DocumentDB — when and how to use Premium SSD v2 high-performance storage, IOPS/bandwidth caps that are gated by compute tier (not disk size), Premium SSD v2 limitations (no CMK, migration paths, disk-hydration sequencing), and storage capacity change limits. Use when picking a storage type at cluster creation, sizing for I/O-intensive workloads, migrating from Premium SSD to Premium SSD v2, or sequencing compute/storage/HA changes on a Premium SSD v2 cluster.
- Author
- azure ↗
- Repository
- documentdb-agent-kit ↗
- Licence
- MIT
- Last repository change
- 01.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Storage configuration guidance for Azure DocumentDB — when and how to use Premium SSD v2 high-performance storage, IOPS/bandwidth caps that are gated by compute tier (not disk size), Premium SSD v2 limitations (no CMK, migration paths, disk-hydration sequencing), and storage capacity change limits. Use when picking a storage type at cluster creation, sizing for I/O-intensive workloads, migrating from Premium SSD to Premium SSD v2, or sequencing compute/storage/HA changes on a Premium SSD v2 cluster.
Original author description
Storage configuration guidance for Azure DocumentDB — when and how to use Premium SSD v2 high-performance storage, IOPS/bandwidth caps that are gated by compute tier (not disk size), Premium SSD v2 limitations (no CMK, migration paths, disk-hydration sequencing), and storage capacity change limits. Use when picking a storage type at cluster creation, sizing for I/O-intensive workloads, migrating from Premium SSD to Premium SSD v2, or sequencing compute/storage/HA changes on a Premium SSD v2 cluster.
How it works
- How Premium SSD v2 changes sizing
- Rules
- References
SKILL.md preview
--- name: documentdb-storage description: Storage configuration guidance for Azure DocumentDB — when and how to use Premium SSD v2 high-performance storage, IOPS/bandwidth caps that are gated by compute tier (not disk size), Premium SSD v2 limitations (no CMK, migration paths, disk-hydration sequencing), and storage capacity change limits. Use when picking a storage type at cluster creation, sizing for I/O-intensive workloads, migrating from Premium SSD to Premium SSD v2, or sequencing compute/storage/HA changes on a Premium SSD v2 cluster. license: MIT --- # Storage — Azure DocumentDB Azure DocumentDB clusters use **remote premium SSD storage**. Two disk types are offered: | Storage type | IOPS / bandwidth scaling | Max IOPS | CMK | Use it for | |---|---|---|---|---| | **Premium SSD** (v1) | Scales with **disk capacity** — bigger disk → higher IOPS | 20,000 | ✔️ | Legacy clusters, scenarios that require CMK | | **Premium SSD v2** | **Decoupled** from disk size — IOPS/bandwidth gated by **compute tier** | 80,000 | ❌ | New production clusters; any I/O-intensive workload | **Premium SSD v2 is the default recommendation for new clusters.** It delivers up to a **12× performance boost at no added cost** by removing the disk-size lever from the IOPS equation — you size storage for *capacity* and size compute for *throughput*, independently. ## How Premium SSD v2 changes sizing On Premium SSD v1, hitting 20,000 IOPS required provisioning a 20 TB disk even when only ~1 TB of data was stored. On Premium SSD v2, the **highest achievable IOPS and bandwidth for the chosen compute tier are auto-configured** regardless of disk size: - Choose storage size based on **how much data** the cluster will hold. - Choose compute tier based on **how much IOPS / MBps** the workload needs (see [storage-tier-iops-caps](storage-tier-iops-caps.md)). - No knobs to tune — the upper-bound IOPS/bandwidth for the tier are applied automatically at no extra cost. ## Rules - [storage-choose-premium-ssdv2](storage-choose-premium-ssdv2.md) — When to pick Premium SSD v2 vs Premium SSD; the CMK trade-off. - [storage-tier-iops-caps](storage-tier-iops-caps.md) — Compute-tier → max IOPS / MBps table; size compute for throughput, not disk for IOPS. - [storage-premium-ssdv2-limitations](storage-premium-ssdv2-limitations.md) — Known limits: no CMK, capacity-change cap, replication restrictions, no online v1→v2 migration. - [storage-disk-hydration-sequencing](storage-disk-hydration-sequencing.md) — Space out compute scale / storage scale / HA-enable operations while the disk is hydrating. ## References - [Premium SSD v2 disks — Azure DocumentDB](https://learn.microsoft.com/azure/documentdb/high-performance-storage)
Files in this package (5)
- SKILL.md 3 KB
- storage-choose-premium-ssdv2.md 3 KB
- storage-disk-hydration-sequencing.md 4 KB
- storage-premium-ssdv2-limitations.md 3 KB
- storage-tier-iops-caps.md 2 KB
Versions
The database has no other skills named documentdb-storage.
Database snapshot: 13.11.2026 · package version 291d2d0103d1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95documentdb-azure-deployment
Deploy an Azure DocumentDB cluster (`Microsoft.DocumentDB/mongoClusters`) end-to-end — Bicep (primary), Azure CLI one-shot, Terraform, or portal. Covers resource-group creation, cluster parameters (tier, storage, server version, sharding, HA), firewall rule configuration,… - 85azure-documentdb
Expert knowledge for Azure DocumentDB development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Mongo-compatible APIs, vector… - 85azure-quotas
Expert knowledge for Azure Quotas development including limits & quotas. Use when checking storage account capacity, IOPS, throughput, portal views, or CLI-based quota increase requests, and other Azure Quotas related development tasks. Not for Azure Monitor (use azure-monitor),… - 95documentdb-high-availability
High availability, business-continuity, and disaster-recovery best practices for Azure DocumentDB — enabling in-region HA with availability zones (99.99% SLA), adding active-passive cross-region replica clusters (99.995% SLA), and understanding automatic backup retention. Use… - 85azure-documentdb
Expert knowledge for Azure DocumentDB development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using DocumentDB vector search,… - 91lsdsk
Use when inspecting or diagnosing storage hardware - which disk hangs off which controller, whether a SATA, SAS or NVMe link runs at the speed both ends support, whether a controller sits in a slot worthy of it, how worn an SSD is, whether reallocated or pending sectors are…