Skip to content

Commit 2501e5d

Browse files
author
Larry Franks
committed
writing
1 parent 6327a50 commit 2501e5d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -127,14 +127,14 @@ To use your own (customer-managed) keys to encrypt the Azure Cosmos DB instance,
127127
> [!NOTE]
128128
> This feature is currently available only in US East, US West 2, US South Central.
129129
130-
To enable provisioning a Cosmos DB instance in your subscription with customer-managed keys, perform the following actions:
130+
To enable provisioning a Cosmos DB instance in your subscription with customer-managed keys, perform the following actions:
131+
132+
* Configure customer-managed keys for Cosmos-DB. For more information, see
131133

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

134136
![Authorize the 'Azure Machine Learning App' in Identity and Access Management in the portal](./media/concept-enterprise-security/authorize-azure-machine-learning.png)
135137

136-
* Raise a support ticket with Azure Cosmos DB to enable your subscription to support customer-managed keys for encrypting a Cosmos DB instance for that region. For more information read LINK TBD
137-
138138
* Use the following parameters when creating the Azure Machine Learning workspace. Both parameters are mandatory and supported in SDK, CLI, REST APIs, and Resource Manager templates.
139139

140140
* `resource_cmk_uri`: This parameter is the full resource URI of the customer managed key in your key vault, including the [version information for the key](../key-vault/about-keys-secrets-and-certificates.md#objects-identifiers-and-versioning).

0 commit comments

Comments
 (0)