Merge pull request #228148 from dileepraotv-github/migrate_continuous

prmerger-automator[bot] · web-flow · commit 8e873b4f3147 · 2023-02-22T05:49:34.000Z
Added more clarity
diff --git a/articles/cosmos-db/migrate-continuous-backup.md b/articles/cosmos-db/migrate-continuous-backup.md
@@ -38,7 +38,7 @@ The following are the key reasons to migrate into continuous mode:
 > * If the account has a single write region.
 > * If the account isn't enabled with analytical store.
 >
-> If the account is using [customer-managed keys](./how-to-setup-cmk.md), a user-assigned managed identity must be declared in the Key Vault access policy and must be set as the default identity on the account.
+> If the account is using [customer-managed keys](./how-to-setup-cmk.md), a managed identity (System-assigned or User-assigned) must be declared in the Key Vault access policy and must be set as the default identity on the account.
 
 ## Permissions
 

Original file line number	Diff line number	Diff line change
`@@ -38,7 +38,7 @@ The following are the key reasons to migrate into continuous mode:`
`38`	`38`	`> * If the account has a single write region.`
`39`	`39`	`> * If the account isn't enabled with analytical store.`
`40`	`40`	`>`
`41`		`-> If the account is using [customer-managed keys](./how-to-setup-cmk.md), a user-assigned managed identity must be declared in the Key Vault access policy and must be set as the default identity on the account.`
	`41`	`+> If the account is using [customer-managed keys](./how-to-setup-cmk.md), a managed identity (System-assigned or User-assigned) must be declared in the Key Vault access policy and must be set as the default identity on the account.`
`42`	`42`
`43`	`43`	`## Permissions`
`44`	`44`