Skip to content

Commit 883e49c

Browse files
Merge pull request #252089 from dileepraotv-github/CMK_ID_UPDATE
Updated system-assigned identity support
2 parents eeae5a2 + 8cbf7ae commit 883e49c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/how-to-setup-customer-managed-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -704,7 +704,7 @@ The following conditions are necessary to successfully restore a periodic backup
704704
705705
### How do customer-managed keys affect continuous backups?
706706
707-
Azure Cosmos DB gives you the option to configure [continuous backups](./continuous-backup-restore-introduction.md) on your account. With continuous backups, you can restore your data to any point in time within the past 30 days. To use continuous backups on an account where customer-managed keys are enabled, you must use a user-assigned managed identity in the Key Vault access policy. Azure Cosmos DB first-party identities or system-assigned managed identities aren't currently supported on accounts using continuous backups.
707+
Azure Cosmos DB gives you the option to configure [continuous backups](./continuous-backup-restore-introduction.md) on your account. With continuous backups, you can restore your data to any point in time within the past 30 days. To use continuous backups on an account where customer-managed keys are enabled, you must use a system-assigned or user-assigned managed identity in the Key Vault access policy. Azure Cosmos DB first-party identities is not currently supported on accounts using continuous backups.
708708
709709
The following conditions are necessary to successfully perform a point-in-time restore:
710710

0 commit comments

Comments
 (0)