The Azure extended network is a bit more complex and more
of an Edge technology, pun intended.
Absolutely,
I intend that pun. This is something else that you configure through Windows
Admin Center. And the use case here is where in your on‑premises network you
have a subnet that needs to be eventually migrated into Azure and you're
going to do that via subnet extension.
You see the bottom part of this diagram? So the idea is
you're migrating VM 1 into Azure, that's your goal.
But the restriction is when it's in Azure,
the VM's in Azure, it has to have the same IP address.
It's admittedly kind of an Edge scenario because Microsoft's
recommendation would normally be recreate your IP ranges in
Azure and what does it really matter what the VMs private IP is.
But you may have dependencies,
compliance requirements, or applications that have a hard
requirement on that private IP. So in that case, we're
performing what's called a subnet extension.
So you're going to create an Azure Virtual Network that contains a
workload subnet with that same subnet ID. You'll also need a
persistent Layer 3 connection between your on‑premises network and
the Azure Virtual Network. That would mean either a site‑to‑site VPN
or an ExpressRoute circuit.
Lastly, you'll need to deploy a couple extra virtual machines. You'll have a
network virtual appliance running on‑prem in its own subnet, as well as an Azure
network virtual appliance. There's some additional restrictions there that Azure
NVA has to be running the Azure Edition of Windows Server 2022. There's a bucket
load of constraints here that we don't need to worry about for the exam
objectives. But once again, to saying that refrain,
if you do want the step by step,
I'll point you in the Exercise files to the Microsoft docs.
In the demo, I'll just show you where to load up this extension in Windows Admin Center.