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/concept-enterprise-security.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ In this article, you'll learn about security features available for Azure Machin
19
19
When you use a cloud service, a best practice is to restrict access to only the users who need it. Start by understanding the authentication and authorization model used by the service. You might also want to restrict network access or securely join resources in your on-premises network with the cloud. Data encryption is also vital, both at rest and while data moves between services. Finally, you need to be able to monitor the service and produce an audit log of all activity.
20
20
21
21
> [!NOTE]
22
-
> The information in this article works with the Azure Machine Learning SDK version 1.0.83.1 or higher.
22
+
> The information in this article works with the Azure Machine Learning Python SDK version 1.0.83.1 or higher.
23
23
24
24
## Authentication
25
25
@@ -129,7 +129,9 @@ To use your own (customer-managed) keys to encrypt the Azure Cosmos DB instance,
129
129
130
130
To enable provisioning a Cosmos DB instance in your subscription with customer-managed keys, perform the following actions:
131
131
132
-
* Configure customer-managed keys for Cosmos-DB. For more information, see
132
+
* Enable customer-managed key capabilities for Cosmos DB. At this time, you must request access to use this capability. To do so, please contact [[email protected]](mailto:[email protected]).
133
+
134
+
For more information, see [Configure customer-managed keys for your Azure Cosmos DB account](../cosmos-db/how-to-setup-cmk.md).
133
135
134
136
* Authorize the Machine Learning App (in Identity and Access Management) with contributor permissions on your subscription.
135
137
@@ -210,7 +212,7 @@ Microsoft may collect non-user identifying information like resource names (for
210
212
211
213
Microsoft also recommends not storing sensitive information (such as account key secrets) in environment variables. Environment variables are logged, encrypted, and stored by us.
212
214
213
-
You may opt out from diagnostic data being collected by setting the `hbi_workspace` parameter to `TRUE` while provisioning the workspace. This functionality is supported when using the AzureML SDK, CLI, REST APIs, or Azure Resource Manager templates.
215
+
You may opt out from diagnostic data being collected by setting the `hbi_workspace` parameter to `TRUE` while provisioning the workspace. This functionality is supported when using the AzureML Python SDK, CLI, REST APIs, or Azure Resource Manager templates.
0 commit comments