Skip to content

Commit b18e5f5

Browse files
authored
Update configure-managed-network.md
clarified byo vnet support
1 parent 64d7b9e commit b18e5f5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/ai-studio/how-to/configure-managed-network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ Before following the steps in this article, make sure you have the following pre
135135

136136
## Limitations
137137

138-
* Azure AI Foundry currently doesn't support bringing your own virtual network, it only supports managed virtual network isolation.
138+
* Azure AI Foundry supports managed virtual network isolation for securing your compute resources. Azure AI Foundry does not support bring your own virtual network for securing compute resources. Please note bring your own virtual network for securing computes is different than your Azure virtual network that is required to access Azure AI Foundry from your on-premises network.
139139
* Once you enable managed virtual network isolation of your Azure AI, you can't disable it.
140140
* Managed virtual network 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.
141141
* The managed virtual network is deleted when the Azure AI is deleted.

0 commit comments

Comments
 (0)