Azure Cosmos DB Provisioned Throughput Rightsizing
Provisioned RU/s are billed hourly whether or not requests consume them.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Lower provisioned throughput on the Cosmos DB account. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Cosmos DB on Azure
- The fix, by hand
- Open Portal → Azure Cosmos DB → the resource → Metrics → Normalized RU Consumption, capture P95 over 14 days.
- Open Settings → Scale, switch to Autoscale or lower the manual RU/s to ~120% of observed P95.
- Review Data Explorer → Indexing policy and exclude paths your queries never filter on.
- Monitor 429 throttle count for one week and tune up if visible.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-247- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.