Skip to content

Commit 57d44e3

Browse files
author
Dileep Rao
committed
Updated Choosing the preferred security model
1 parent 54c9005 commit 57d44e3

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,15 @@ Using customer-managed keys with Azure Cosmos DB requires you to set two propert
5858

5959
1. Once these settings have been enabled, on the access policy tab, you can choose your preferred permission model to use. Access policies are set by default, but Azure role-based access control is supported as well.
6060

61+
### Choosing the preferred security model 
62+
63+
Once purge protection and soft-delete have been enabled, on the access policy tab, you can choose your preferred permission model to use. Access policies are set by default, but Azure role-based access control is supported as well.
64+
6165
The necessary permissions must be given for allowing Cosmos DB to use your encryption key. This step varies depending on whether the Azure Key Vault is using either Access policies or role-based access control.
6266

67+
> [!NOTE]
68+
> It is important to note that only one security model can be active at a time, so there is no need to seed the role based access control if the Azure Key Vault is set to use access policies and vice versa)
69+
6370
### Add an access policy
6471

6572
In this variation, use the Azure Cosmos DB principal to create an access policy with the appropriate permissions.

0 commit comments

Comments
 (0)