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
Data stored in your Azure Cosmos account is automatically and seamlessly encrypted. Azure Cosmos DB offers two options to manage the keys used to encrypt the data at rest:
18
18
@@ -95,7 +95,7 @@ When creating a new Azure Cosmos DB account with PowerShell,
95
95
- Use **2019-12-12** as the API version.
96
96
97
97
> [!IMPORTANT]
98
-
> You should set the `Location` parameter explicitly for the account to be successfully created with customer-managed keys.
98
+
> You must set the `Location` parameter explicitly for the account to be successfully created with customer-managed keys.
99
99
100
100
```powershell
101
101
$resourceGroupName = "myResourceGroup"
@@ -126,7 +126,7 @@ When creating a new Azure Cosmos account through an Azure Resource Manager templ
126
126
- Use **2019-12-12** as the API version.
127
127
128
128
> [!IMPORTANT]
129
-
> You should set the `Location` parameter explicitly for the account to be successfully created with customer-managed keys.
129
+
> You must set the `Location` parameter explicitly for the account to be successfully created with customer-managed keys.
130
130
131
131
```json
132
132
{
@@ -200,7 +200,7 @@ All the data stored in your Azure Cosmos account is encrypted with the customer-
200
200
201
201
- The property paths declared in your [indexing policies](./index-policy.md)
202
202
203
-
- The values of your container's[partition key](./partitioning-overview.md)
203
+
- The values of your containers'[partition key](./partitioning-overview.md)
204
204
205
205
### Are customer-managed keys supported for existing Azure Cosmos accounts?
0 commit comments