Skip to content

Commit 97d4d29

Browse files
author
Larry Franks
committed
note on image builds & no public IP
1 parent 53c98d9 commit 97d4d29

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

articles/machine-learning/how-to-secure-training-vnet.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
99
ms.reviewer: larryfr
1010
ms.author: jhirono
1111
author: jhirono
12-
ms.date: 01/06/2022
12+
ms.date: 03/01/2022
1313
ms.custom: contperf-fy20q4, tracking-python, contperf-fy21q1, references_regions, devx-track-azurecli
1414
ms.devlang: azurecli
1515

@@ -107,6 +107,8 @@ In this article you learn how to secure the following training compute resources
107107
108108
* If you create a compute instance and plan to use the no public IP address configuration, your Azure Machine Learning workspace's managed identity must be assigned the __Reader__ role for the virtual network that contains the workspace. For more information on assigning roles, see [Steps to assign an Azure role](/azure/role-based-access-control/role-assignments-steps).
109109

110+
* If you create a compute cluster with the no public IP address configuration, you can't use it as the [image build cluster](how-to-secure-workspace-vnet.md#configure-image-builds) for your workspace.
111+
110112
* If the Azure Storage Accounts for the workspace are also in the virtual network, use the following guidance on subnet limitations:
111113

112114
* If you plan to use Azure Machine Learning __studio__ to visualize data or use designer, the storage account must be __in the same subnet as the compute instance or cluster__.

articles/machine-learning/how-to-secure-workspace-vnet.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.subservice: enterprise-readiness
88
ms.reviewer: larryfr
99
ms.author: jhirono
1010
author: jhirono
11-
ms.date: 02/28/2022
11+
ms.date: 03/01/2022
1212
ms.topic: how-to
1313
ms.custom: contperf-fy20q4, tracking-python, contperf-fy21q1, security
1414

@@ -248,7 +248,9 @@ Azure Container Registry can be configured to use a private endpoint. Use the fo
248248
1. Use one of the following methods to configure the workspace to build Docker images using the compute cluster.
249249
250250
> [!IMPORTANT]
251-
> When using a compute cluster for image builds, only a CPU SKU is supported.
251+
> The following limitations apply When using a compute cluster for image builds:
252+
> * Only a CPU SKU is supported.
253+
> * You can't use a compute cluster configured for no public IP address.
252254
253255
# [Azure CLI](#tab/cli)
254256

0 commit comments

Comments
 (0)