Skip to content

Commit 4331d26

Browse files
committed
add section for azure advisor
1 parent 406a6bb commit 4331d26

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -713,6 +713,12 @@ Alternatively, to revoke all keys from an Azure Key Vault instance, you can dele
713713
714714
The only operation possible when the encryption key has been revoked is account deletion.
715715
716+
### Assign a new managed-identity to the restored database account to continue accessing or recover access to the database account
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.](https://learn.microsoft.com/cli/azure/cosmosdb/identity?view=azure-cli-latest#az-cosmosdb-identity-assign)
721+
716722
## Next steps
717723
718724
- Learn more about [data encryption in Azure Cosmos DB](database-encryption-at-rest.md).

0 commit comments

Comments
 (0)