Skip to content

Commit 75e8304

Browse files
Merge pull request #221211 from vijetajo/patch-111
Update how-to-secure-training-vnet.md
2 parents 845b7e9 + f13d33d commit 75e8304

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,7 @@ In this article you learn how to secure the following training compute resources
7474
* To create a compute cluster or instance without a public IP address (a preview feature), your workspace must use a private endpoint to connect to the VNet. For more information, see [Configure a private endpoint for Azure Machine Learning workspace](how-to-configure-private-link.md).
7575
* If you plan to secure the virtual network by restricting traffic, see the [Required public internet access](#required-public-internet-access) section.
7676
* The subnet used to deploy compute cluster/instance shouldn't be delegated to any other service. For example, it shouldn't be delegated to ACI.
77+
* Compute cluster/instance deployment in virtual network is not supported with Azure Lighthouse
7778

7879
### Azure Databricks
7980

@@ -320,4 +321,4 @@ This article is part of a series on securing an Azure Machine Learning workflow.
320321
* [Secure the inference environment](how-to-secure-inferencing-vnet.md)
321322
* [Enable studio functionality](how-to-enable-studio-virtual-network.md)
322323
* [Use custom DNS](how-to-custom-dns.md)
323-
* [Use a firewall](how-to-access-azureml-behind-firewall.md)
324+
* [Use a firewall](how-to-access-azureml-behind-firewall.md)

0 commit comments

Comments
 (0)