You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/how-to-setup-customer-managed-keys.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -715,9 +715,10 @@ The only operation possible when the encryption key has been revoked is account
715
715
716
716
### Assign a new managed-identity to the restored database account to continue accessing or recover access to the database account
717
717
718
-
- [Create a new user-assigned managed identity.](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md#create-a-user-assigned-managed-identity)
719
-
- [Grant KeyVault key access to this identity.](#choosing-the-preferred-security-model)
720
-
- [Assign this new identity to your restored database account.](/cli/azure/cosmosdb/identity#az-cosmosdb-identity-assign)
718
+
Steps to assign a new managed-identity:
719
+
1. [Create a new user-assigned managed identity.](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md#create-a-user-assigned-managed-identity)
720
+
2. [Grant KeyVault key access to this identity.](#choosing-the-preferred-security-model)
721
+
3. [Assign this new identity to your restored database account.](/cli/azure/cosmosdb/identity#az-cosmosdb-identity-assign)
0 commit comments