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/machine-learning/how-to-manage-rest.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ The response should provide an access token good for one hour:
72
72
}
73
73
```
74
74
75
-
Make note of the token, as you'll use it to authenticate all additional administrative requests. You'll do so by setting an Authorization header in all requests:
75
+
Make note of the token, as you'll use it to authenticate all administrative requests. You'll do so by setting an Authorization header in all requests:
## Create a workspace using customer-managed encryption keys
343
343
344
-
By default, metadata for the workspace is stored in an Azure Cosmos DB instance that Microsoft maintains. This data is encrypted using Microsoft-managed keys. Instead of using the Microsoft-managed key, you can also provide your own key. Doing so creates an [additional set of resources](./concept-data-encryption.md#azure-cosmos-db) in your Azure subscription to store your data.
344
+
By default, metadata for the workspace is stored in an Azure Cosmos DB instance that Microsoft maintains. This data is encrypted using Microsoft-managed keys. Instead of using the Microsoft-managed key, you can also provide your own key. Doing so creates an [another set of resources](./concept-data-encryption.md#azure-cosmos-db) in your Azure subscription to store your data.
345
345
346
-
To create a workspaces that uses your keys for encryption, you need to meet the following prerequisites:
346
+
To create a workspace that uses your keys for encryption, you need to meet the following prerequisites:
347
347
348
348
* The Azure Machine Learning service principal must have contributor access to your Azure subscription.
349
349
* You must have an existing Azure Key Vault that contains an encryption key.
350
-
* The Azure Key Vault must exist in the same Azure region where you will create the Azure Machine Learning workspace.
351
-
* The Azure Key Vault must have soft delete and purge protection enabled to protect against data loss in case of accidental deletion.
350
+
* The Azure Key Vault must exist in the same Azure region where you'll create the Azure Machine Learning workspace.
351
+
* The Azure Key Vault must have soft delete and purge protection enabled to protect against data loss if there was accidental deletion.
352
352
* You must have an access policy in Azure Key Vault that grants get, wrap, and unwrap access to the Azure Cosmos DB application.
353
353
354
-
To create a workspaces that uses a user-assigned managed identity and customer-managed keys for encryption, use the below request body. When using an user-assigned managed identity for the workspace, also set the `userAssignedIdentity` property to the resource ID of the managed identity.
354
+
To create a workspace that uses a user-assigned managed identity and customer-managed keys for encryption, use the below request body. When using a user-assigned managed identity for the workspace, also set the `userAssignedIdentity` property to the resource ID of the managed identity.
0 commit comments