Merge pull request #252632 from dileepraotv-github/User_assigned_identity_update

Updated prerequisite steps.

Author: prmerger-automator[bot]

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

@@ -539,7 +539,7 @@ Not available
 
 ## Restore a continuous account that is configured with managed identity
 
-A user-assigned identity is required in the restore request because the source account managed identity (User-assigned and System-assigned identities) cannot be carried over automatically to the target database account.
+A user-assigned identity is required in the restore request because the source account managed identity (User-assigned and System-assigned identities) can't be carried over automatically to the target database account.
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -576,7 +576,7 @@ Use the Azure CLI to restore a continuous account that is already configured usi
         --default-identity "UserAssignedIdentity=$identityId" \
     ```
 
-1. Once the restore has completed, the target (restored) account will have the user-assigned identity.  If desired, user can update the account to use System-Assigned managed identity.
+1. Once the restore has completed, the target (restored) account has the user-assigned identity.  If desired, user can update the account to use System-Assigned managed identity.
 
 
 ### [PowerShell / Azure Resource Manager template / Azure portal](#tab/azure-powershell+arm-template+azure-portal)
@@ -704,7 +704,16 @@ The following conditions are necessary to successfully restore a periodic backup
 
 ### How do customer-managed keys affect continuous backups?
 
-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.
+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 are not currently supported on accounts using continuous backups.
+
+Prerequisite steps for Customer Managed Keys enabled accounts to update user assigned identity.
+
+- Add a user-assigned identity to the Cosmos DB account, and grant permissions in key vault access policy.
+- Set the user-assigned as default identity via Azure CLI or ARM.
+
+```azurecli
+az cosmosdb update --resource-group MyResourceGroup --name MyAccountName --default-identity UserAssignedIdentity=/subscriptions/MySubscriptionId/resourcegroups/MyResourceGroup/providers/Microsoft.ManagedIdentity/userAssignedIdentities/MyUserAssignedIdentity
+```
 
 The following conditions are necessary to successfully perform a point-in-time restore: