Skip to content

Commit d1df7c6

Browse files
authored
Merge pull request #123745 from AhmadAbdullah91/patch-4
Update how-to-managed-network.md
2 parents abf4415 + 0e3e6dd commit d1df7c6

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/machine-learning/how-to-managed-network.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1112,6 +1112,8 @@ The Azure Machine Learning managed VNet feature is free. However, you're charged
11121112
* FQDN outbound rules only support ports 80 and 443.
11131113
* If your compute instance is in a managed network and is configured for no public IP, use the `az ml compute connect-ssh` command to connect to it using SSH.
11141114
* When using Managed Vnet, you can't deploy compute resources inside your custom Vnet. Compute resources can only be created inside the managed Vnet.
1115+
* Managed network isolation cannot establish a private connection from the managed virtual network to a user's on-premises resources.
1116+
For the list of supported private connections, see [Private Endpoints](/azure/machine-learning/how-to-managed-network?view=azureml-api-2&tabs=azure-cli&preserve-view=true#private-endpoints).
11151117

11161118
### Migration of compute resources
11171119

0 commit comments

Comments
 (0)