Skip to content

Commit b87c2fb

Browse files
authored
PE as a pre-requisite for disabling Public IP
Compute Instance in Azure AI Foundry can have its Public IP disabled only if AI Hub has a private endpoint configured.
1 parent 4912a73 commit b87c2fb

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,7 @@ Before following the steps in this article, make sure you have the following pre
142142
* 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.
143143
* Using FQDN outbound rules increases the cost of the managed virtual network because FQDN rules use Azure Firewall. For more information, see [Pricing](#pricing).
144144
* FQDN outbound rules only support ports 80 and 443.
145+
* If you want to disable compute instance's Public IP, you must add a private endpoint to a hub.
145146
* When using a compute instance with a managed network, use the `az ml compute connect-ssh` command to connect to the compute using SSH.
146147
* If your managed network is configured to __allow only approved outbound__, you can't use an FQDN rule to access Azure Storage Accounts. You must use a private endpoint instead.
147148

0 commit comments

Comments
 (0)