I'm exploring Bring Your Own Network for Azure AI Foundry. What networking and governance details are worth checking before setting it up?
What should I watch out for when setting up BYON in Azure AI Foundry?
Answers
Start with the outbound path for agent tool calls. If traffic needs to leave through a hub firewall, plan that egress explicitly rather than assuming the virtual network setup handles it for you.
Also map the Foundry resource dependencies and how each one is reached privately. The agent's network path and its dependencies deserve separate attention.
Reply to this answer
Don't count on virtual network flow logs to show every private agent dependency call. Foundry's Data Host Proxy affects what those logs can see, so a lack of traffic there doesn't necessarily mean the dependency isn't being used.
Reply to this answer
There's a governance piece too. Think through how Foundry accounts will be managed alongside the network resources, especially if you're deploying the setup with Bicep. The account model and the private networking dependencies both need to fit your deployment process.
Reply to this answer
If private Azure API Management is part of the plan, treat it as a separate integration to work through. Authentication, application roles, and rate limiting are all relevant policy questions, in addition to the private connectivity itself.
Reply to this answer
Add your answer
Answers are reviewed before publication.
jellybean.veto:
That makes the proxy path worth factoring into the monitoring plan, not just the network diagram.