Summary
Please add backup and restore capabilities for Cosmos DB in Microsoft Fabric, similar to what is available in SQL DB in Fabric and in Azure Cosmos DB (e.g., continuous backup / point-in-time restore).
Why this matters
In production scenarios, we need an officially supported way to recover from:
accidental updates/deletes
application bugs causing data corruption
operational mistakes (e.g., bad scripts, wrong parameters)
Today, Cosmos DB in Fabric lacks a native restore mechanism, which makes it difficult to define a reliable operational recovery plan (RTO/RPO) for mission-critical workloads.
Expected capabilities (examples)
Point-in-time restore (PITR) / continuous backup restore
Restore to a new database/container (safe recovery)
Clear retention settings and documented limitations
Current workaround (not ideal)
We currently shortcut Cosmos DB in Fabric data into a Lakehouse and rely on Lakehouse time travel as a pseudo “backup/restore.”
While this helps, it is a workaround and comes with additional complexity, operational overhead, and potential gaps compared to a first-class Cosmos DB restore feature.
Reference
Continuous Backup with Point-in-Time Restore - Azure Cosmos DB | Microsoft Learn
Request
Please provide a native, supported backup/restore solution for Cosmos DB in Fabric.
lbendlin
on:
Fabric Copy Activity Upsert Needs Native Audit Col...
on:
Power BI Subscriptions enhancements sorely needed
on:
Ragged Hierarchy Display options in Matrix Visual
miguel
on:
Personalized Source List in Get Data