Skip to content

Commit 81f885d

Browse files
authored
Update how-to-setup-customer-managed-keys.md
1 parent c0fc040 commit 81f885d

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

articles/machine-learning/how-to-setup-customer-managed-keys.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,6 @@ In the [customer-managed keys concepts article](concept-customer-managed-keys.md
4747
* You can't delete Microsoft-managed resources used for customer-managed keys without also deleting your workspace.
4848
* The key vault that contains your customer-managed key must be in the same Azure subscription as the Azure Machine Learning workspace.
4949
* OS disk of machine learning compute can't be encrypted with customer-managed key, but can be encrypted with Microsoft-managed key if the workspace is created with `hbi_workspace` parameter set to `TRUE`. For more details, see [Data encryption](concept-data-encryption.md#machine-learning-compute).
50-
* Workspace with customer-managed key doesn't currently support v2 batch endpoint.
5150

5251
> [!IMPORTANT]
5352
> When using a customer-managed key, the costs for your subscription will be higher because of the additional resources in your subscription. To estimate the cost, use the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).

0 commit comments

Comments
 (0)