Update articles/cosmos-db/migrate-continuous-backup.md

Thomas Weiss · kavskalyan · web-flow · commit 6b5d1a8e99ca · 2022-02-22T17:27:35.000-08:00
Co-authored-by: kavskalyan &lt;kavs.kalyan@gmail.com&gt;
diff --git a/articles/cosmos-db/migrate-continuous-backup.md b/articles/cosmos-db/migrate-continuous-backup.md
@@ -32,7 +32,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.
+> 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.
 
 ## Permissions
 

Original file line number	Diff line number	Diff line change
`@@ -32,7 +32,7 @@ The following are the key reasons to migrate into continuous mode:`
`32`	`32`	`> * If the account has a single write region.`
`33`	`33`	`> * If the account isn't enabled with analytical store.`
`34`	`34`	`>`
`35`		`-> 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.`
	`35`	`+> 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.`
`36`	`36`
`37`	`37`	`## Permissions`
`38`	`38`