Skip to content

Commit ad8121b

Browse files
Merge pull request #280871 from Blackmist/ent-bug03
updates per feedback
2 parents e396376 + e18e30c commit ad8121b

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1102,7 +1102,8 @@ The Azure Machine Learning managed VNet feature is free. However, you're charged
11021102

11031103
## Limitations
11041104

1105-
* Once you enable managed VNet isolation of your workspace, you can't disable it.
1105+
* Azure AI Studio doesn't support using your own Azure Virtual Network to secure the hub, project, or compute resources. You can only use the managed network feature to secure these resources.
1106+
* Once you enable managed VNet isolation of your workspace (either allow internet outbound or allow only approved outbound), you can't disable it.
11061107
* Managed VNet uses private endpoint connection to access your private resources. You can't have a private endpoint and a service endpoint at the same time for your Azure resources, such as a storage account. We recommend using private endpoints in all scenarios.
11071108
* The managed VNet is deleted when the workspace is deleted.
11081109
* Data exfiltration protection is automatically enabled for the only approved outbound mode. If you add other outbound rules, such as to FQDNs, Microsoft can't guarantee that you're protected from data exfiltration to those outbound destinations.

0 commit comments

Comments
 (0)