Skip to content

Commit 37b0818

Browse files
authored
Update configure-managed-network.md
Add note on private storage + public AI Foundry does not depend on managed vnet being set up.
1 parent a1eac44 commit 37b0818

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,9 @@ The following diagram shows a managed virtual network configured to __allow only
5858
5959
:::image type="content" source="../media/how-to/network/only-approved-outbound.svg" alt-text="Diagram of managed virtual network isolation configured for allow only approved outbound." lightbox="../media/how-to/network/only-approved-outbound.png":::
6060

61+
> [!NOTE]
62+
> When you are accessing a private storage account from a public AI Foundry hub, ensure you are accessing AI Foundry from within the virtual network of your storage account. This ensures you can call actions such as upload files to a private storage account, which is independent of your AI Foundry hub's networking settings. For more on setting your private storage accounts virtual network, see [Configure Azure Storage firewalls and virtual networks](https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal).
63+
6164
## Prerequisites
6265

6366
Before following the steps in this article, make sure you have the following prerequisites:

0 commit comments

Comments
 (0)