Skip to content

Commit e21fc14

Browse files
authored
Update data-residency.md
1 parent 62b2f3f commit e21fc14

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/cosmos-db/data-residency.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,11 @@ In Azure Cosmos DB, you must explicitly configure the cross-region data replicat
2525

2626
**Periodic mode Backups**: By default, periodic mode account backups will be stored in geo-redundant storage. For periodic backup modes, you can configure data redundancy at the account level. There are three redundancy options for the backup storage. They are local redundancy, zone redundancy, or geo redundancy. For more information, see [periodic backup/restore](periodic-backup-restore-introduction.md).
2727

28+
## Residency requirements for analytical store
29+
30+
Analytical store is resident by default as it is stored in either locally redundant or zone redundant storage. To learn more, see the [analytical store](analytical-store-introduction.md) article.
31+
32+
2833
## Use Azure Policy to enforce the residency requirements
2934

3035
If you have data residency requirements that require you to keep all your data in a single Azure region, you can enforce zone-redundant or locally redundant backups for your account by using an Azure Policy. You can also enforce a policy that the Azure Cosmos DB accounts are not geo-replicated to other regions.

0 commit comments

Comments
 (0)