Alright.
So lastly, we've got Virtual WAN, and to set the stage here,
let me go to my VNets, my virtual networks,
and recall that a virtual network can get pretty complicated
pretty quickly because you need to know IPv4,
you may need to know IPv6,
you've got the concept of peering virtual networks and the implications there,
there is laying out your subnets,
there is interacting with managed appliances like firewalls,
there is routing, there is custom DNS, there is a lot going on here.
So as I had mentioned,
the value proposition of the virtual WAN is that
you get a managed hub experience.
And the way this works from an object model perspective is that
you create a virtual WAN resource like I have,
and then you deploy one or more managed hubs.
So if we go to Connectivity, Hubs, I don't have any yet,
so you'd start by creating them, and then from then on,
you'll see that you can manage your unmanaged VNets the way you normally do,
and then you manage your managed hubs in the context of Virtual WAN.
So let me show you.
Let's create a new hub, I'll put it in my home region.
Now you can have multiple hubs, and you can link them together.
Again,
that's one of the value propositions here that you can design a pretty
complicated multi‑hub spoke network infrastructure environment.
Call this twaz800managedhub.
All you choose is the address space.
I'm going to do 10.98.0.0/16.
You don't get any control outside of that like you do
when you're doing unmanaged VNets,
you're delegating all of that management to Azure,
but watch this, it steps us through here the different kinds of connections,
and we can always create them after the fact,
this is just part of the creation workflow.
If we've got need to do site‑to‑site VPN,
we can just go ahead and choose what speed,
what bandwidth are we looking at, and go on from there.
If we want to do point‑to‑site, yes, you'll need to have a gateway,
and you just choose how many clients.
So the interface is different from what you see when you're
deploying these resources separately.
What kind of configuration are you looking for and create new configuration.
That's going to determine things like what kind of
authentication you're going to do, are you going to do certificate,
or radius, or Azure AD, so it's an abstraction really.
I want you to see that.
It's an abstraction over doing VNets and hub spokes and hybrid
networking that you otherwise would have to do manually.
So once you have the virtual hub, that can create quite a bit of time to create.
You then can go into the hub, and you can stand up additional VPNs,
ExpressRoute circuits,
and this virtual network connections allows you to create
VNet peerings and Virtual WAN parlance.
The network connection is the same thing as a virtual network peering.
And then also, it's not surfaced here at the Virtual WAN,
but once you're inside your hub,
you can work with the BGP routing and route table creation and propagation.
That becomes important if you're going to do things like laying in Azure
Firewall or third‑party network virtual appliances,
and you want to customize routing in your virtual network infrastructure. There you have it.