I'm currently using a Virtual WAN setup with Site-to-Site (S2S) VPN, where multiple virtual networks (VNets) are peered to a hub. We're in the process of implementing an ExpressRoute circuit and I'm curious about the possibility of transitioning gradually. Specifically, I want to know if it's feasible to have only the development environment VNets utilize ExpressRoute for connecting to on-premise environments first. Since all Azure VNets connect to the same on-premise address spaces, simply advertising different prefixes through ExpressRoute or VPN may not work as expected. Any insights on how to handle this situation?
2 Answers
I’m in a similar situation, prepping to add ExpressRoute to my setup, but I'm not rushing into it just yet. Definitely keeping an eye on this for any tips!
One option could be to set up a secondary Virtual WAN with ExpressRoute specifically for your dev environment. I haven't tried this myself, so I can't say for sure, but it might be a way to make the transition smoother.
That sounds interesting! But can we manage that without any downtime? For dev environments, it's probably not a big deal, but production might face challenges.