Azure Cosmos DB Dev/Test with Multi-Region Replication
Every additional region multiplies provisioned throughput cost, because the same RU/s must be provisioned in each, a duplication a dev/test account does not need.
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: Disable multi-region writes on the non-production 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
- Confirm this is a non-production Cosmos DB account (dev/test/staging tag, lower-environment subscription) that does not need geo-replication.
- Open Portal → Azure Cosmos DB → the resource → Replicate data globally.
- Remove the additional replica regions, collapsing the account to a single region. The saving comes from dropping the replicated regions (each replicated region multiplies the provisioned-RU cost). NOT from toggling multi-region writes while keeping the replicas.
- Keep only the primary write region; Save and wait for the topology change to complete.
- Confirm the application connection-string / preferred-regions list still targets the remaining region.
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-1337- 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.