Azure Cosmos DB Backup Policy Not Configured
Recovery depends on defaults nobody chose, so the retention you actually have may be far shorter than you assume.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Configure a backup policy on Cosmos DB account.
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 → Backup and Restore.
- Decide between Periodic (cheaper, 8h RPO default) and Continuous (PITR, irreversible).
- If Periodic: tune the backup interval (1-24h) and retention (8-720h) for your RPO.
- If Continuous: pick tier1 (7 day PITR) or tier2 (30 day PITR). Acknowledge the one-way switch.
- Save.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1336- Full reference
Related checks
See the compliance findings 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.