Has anyone here had any luck with the Microsoft Foundry sample deployment that allows you to bring your own virtual network? I'm following this guide on creating a fully private Foundry environment, and I've set up express routes and private DNS using a private resolver, which are all working seamlessly. The deployment finished successfully, but I'm facing issues when trying to access the agents page, resulting in a timeout error. Additionally, I'm encountering errors while connecting blob stores through the AI Search deployment. I've checked the RBAC configurations, and everything seems fine. Does anyone have experience with this setup?
1 Answer
Honestly, the private networking setup in Foundry can be quite a hassle. It’s poorly documented and tricky to manage, with some unexpected quirks. My advice would be to avoid it if you can. Even though it’s now generally available for both classic and new Foundry agents, it’s still quite a mess. Personally, I’m just waiting for Microsoft to roll out their managed virtual network option instead.
What are you doing for your private requirements then? Just relying on public endpoints?