Intermittent Network Access to Azure AI Foundry v2

[Messatsu92]

Description

Accessing Foundry v2 is not possible without explicitly whitelisting the client's public IP in the resource's network settings. This applies even from internal network environments. The behavior is intermittent — some users can access Foundry while others cannot, despite being on the same logical network. The issue does not reproduce on Foundry v1.

Observed Behavior

• Access fails without manual IP whitelisting
• Affects some users but not others on the same network
• No equivalent issue observed on Foundry v1

Suspected Cause
Different users appear to egress through different public IPs depending on their VPN client or routing path, causing inconsistent access when only specific IPs are whitelisted in the Foundry network settings.

Questions :

1. What is the expected network configuration for Foundry v2 to support users accessing from a corporate VPN with dynamic egress IPs?
2. Is there a difference in default network access settings between Foundry v1 and v2 that would explain why v1 does not require IP whitelisting?
3. What is the recommended approach, Private Endpoint or Selected Networks, for a corporate environment with multiple egress paths, and what are the DNS/VNet requirements for each?

Thanks for your help!