Skip to content

Commit 12d5d4f

Browse files
author
Larry Franks
committed
updating image and text for cosmos db customer-managed key
1 parent f57a6e1 commit 12d5d4f

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

articles/machine-learning/concept-enterprise-security.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In this article, you'll learn about security features available for Azure Machin
1919
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.
2020

2121
> [!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.
2323
2424
## Authentication
2525

@@ -129,7 +129,9 @@ To use your own (customer-managed) keys to encrypt the Azure Cosmos DB instance,
129129
130130
To enable provisioning a Cosmos DB instance in your subscription with customer-managed keys, perform the following actions:
131131

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).
133135

134136
* Authorize the Machine Learning App (in Identity and Access Management) with contributor permissions on your subscription.
135137

@@ -210,7 +212,7 @@ Microsoft may collect non-user identifying information like resource names (for
210212

211213
Microsoft also recommends not storing sensitive information (such as account key secrets) in environment variables. Environment variables are logged, encrypted, and stored by us.
212214

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.
214216

215217
### Microsoft-generated data
216218

110 KB
Loading

0 commit comments

Comments
 (0)