Skip to content

Commit 6e12b79

Browse files
Update how to managed network
Added limitation for compute resources in managed vnet.
1 parent 522289e commit 6e12b79

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1111,6 +1111,7 @@ The Azure Machine Learning managed VNet feature is free. However, you're charged
11111111
* Using FQDN outbound rules increases the cost of the managed VNet because FQDN rules use Azure Firewall. For more information, see [Pricing](#pricing).
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.
1114+
* When using Managed Vnet, you can't deploy compute resources inside your custom Vnet. Compute resources can only be created inside the managed Vnet.
11141115

11151116
### Migration of compute resources
11161117

0 commit comments

Comments
 (0)