DFdom@fradley
← ~/writing
$ cat virtual-wan-vs-hub-and-spoke.md

Virtual WAN vs hub-and-spoke: a cost-of-management decision

Azure Virtual WAN often gets chosen because it sounds like the grown-up option. Sometimes that's justified, and sometimes a team pays a managed premium before it needs to.

Both patterns connect spoke networks, on-premises sites and shared services so traffic flows where it should and nowhere else. The main difference is who operates the hub.

With hub-and-spoke you own the hub network. You run the firewall, the route tables, the gateways and every peering. You get total control, and when something routes oddly at 2am it's yours to fix.

With Virtual WAN Microsoft runs the transit core. Routing, scale and branch connectivity become a managed service. You give up some fine-grained control and pay for the convenience, billed per hub, per connection and for the data processed.

HUB AND SPOKE you own the hub and every peering Corp prod VNet Online VNet Hub VNet you build it firewall, route tables, gateways, peering: all yours to run On-premises ExpressRoute / VPN peering peering VIRTUAL WAN Microsoft owns the transit core Corp prod VNet Online VNet Virtual hub Microsoft runs it routing and scale: managed, metered per hub and connection On-premises ExpressRoute / VPN connection connection
The shape is nearly identical, which is why the choice often gets made on instinct. The difference is the box in the middle: who runs it, and who bills per hour for it.

Three questions

How much network will you run in the next two years? Count the real regions and branches, not the roadmap. Two regions and a handful of spokes rarely justify the managed transit of Virtual WAN. Thirty branches across continents almost always do.

Who manages the routing? A capable network team that wants that control will find hub-and-spoke cheaper and clearer. A small team with better things to do is making a rational trade by paying Microsoft to run the hard part.

What does the traffic look like? If most of it goes through a central hub to shared services and the internet, hub-and-spoke fits. If you need any-to-any connectivity between many sites, the transit in Virtual WAN earns its price quickly.

Don't pick vWAN because it sounds more enterprise. Model both against your real topology and expected growth, put the run cost beside the staff time, and take the lower total.

Next: why identity, not the firewall, is your real security perimeter now.

discuss on linkedin → more writing