Azure, in particular, extends upon what we can do.
I think Microsoft attempts to make up for the fact that when
you're doing software‑defined networking in Azure,
you're not going to be able to touch the hardware or get the
degree of depth that you are necessarily on‑premises when you
can walk into your server closets, where you can walk into switch closets,
you can actually feel the cables and the
terminations and all of that kind of stuff.
In the Azure portal for your Azure VMs,
you can inspect at the network‑interface level the routing table for each VM.
And this has an advantage.
Again, we don't need to get too far into the weeds here,
but we have an advantage of integration with all of Azure Resource Manager.
This particular route table, you can see the next hop type,
there are these friendly labels called service tags.
So instead of having next hop being a single,
discrete IP address, like a default gateway address,
you can be much more expansive.
So there's in this example,
the bottom two options are saying if we're trying to
get to any of those IP ranges, go through a VirtualNetworkServiceEndpoint.
So these service tags provide a way to notate potentially a
lot of addresses with a single label.
We see these service tags manifested throughout the Azure networking stack. I'll show you more about this effective route stuff in the demo.