Virtual WAN

Question

We have a current infrastructure with Servers, a few peered vnets, a virtual network gateway that that has a S2S connection to our on prem data center, and some vpn connected users. How difficult and impactful will it be to switchover to a virtual WAN? Can it be integrated to our existing infrastructure? Can we just utilized the virtual WAN vpn group abilities and have it connected to our current setup. We eventually plan on moving our on Prem Data Center to Azure but maintain a S2S connection to the office and P2S connections for all of your users. Not all of the users will have the same level of access, hence why we are exploring the group functionality. I would appreciate any thoughts and advice on the best way of achieving this. Thanks!

Answer 1

Hi @Jose Cintron , I understand that you plan to migrate from current hub-and-spoke to Virtual WAN.

Please review Virtual WAN - migrate from hub-and-spoke topology that details out migration path.

To answer your question - Can it be integrated to our existing infrastructure? Not entirely, Virtual WAN does not allow any vnet with vnet gateway (VPN gateway or Express Route gateway) to be peered to VWAN Hub. You can migrate any vnets without vnet gateway by peering them to VWAN Hub. You can still use your old Hub (in hub-and-spoke topology) and resources inside it if you remove all vnet gateways in it, so you can peer it with VWAN Hub, as another spoke (e.g. shared services spoke).

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.