Skip to content

Commit 250dc1f

Browse files
author
Larry Franks
committed
feedback
1 parent 0ba2f9d commit 250dc1f

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,9 +85,11 @@ In this article you learn how to secure the following training compute resources
8585
* One network security group (NSG). This NSG contains the following rules, which are specific to compute cluster and compute instance:
8686

8787
> [!IMPORTANT]
88-
> Azure Machine Learning compute cluster and instance rely on Azure Batch. In addition to the subnet level NSGs, NSGs are also created at the network interface (NIC) level. When evaluating network traffic, it is evaluated against *union* of subnet and NIC level NSG.
88+
> Compute instance and compute cluster automatically create an NSG with the required rules.
89+
>
90+
> If you have another NSG at the subnet level, the rules in the subnet level NSG mustn't conflict with the rules in the automatically created NSG.
8991
>
90-
> Use caution when modifying these NSGs, as it is possible to break communication between the cluster/instance and Azure Batch. For more information, see [Network security groups: Batch default](/azure/batch/batch-virtual-network#network-security-groups-batch-default).
92+
> To learn how the NSGs filter your network traffic, see [How network security groups filter network traffic](/azure/virtual-network/network-security-group-how-it-works).
9193

9294
* Allow inbound TCP traffic on ports 29876-29877 from the `BatchNodeManagement` service tag.
9395
* Allow inbound TCP traffic on port 44224 from the `AzureMachineLearning` service tag.

0 commit comments

Comments
 (0)