Before we start to get into installing and configuring AD FS 2019, I want to talk a bit about my lab
environment.
I have a Windows ten physical machine that's running Hyper-V to host the VMs I'm using in this course.
You don't have to use Hyper-V.
You're free to use any hypervisor of your choice to run the guest VMs in my environment.
There's a Windows Server 2019 domain controller named DC and it has Active Directory domain services
installed.
I've called the network company Dot PRI, and that same DC machine also has DNS installed as well as
Active Directory certificates.
Services will need that in order to create the certificate for the ad fs service to use.
But you could also use a certificate purchased from a trusted third party certificate authority.
When we get into federating with Azure later in the course, I'll actually be using a certificate from
a third party trusted CAA.
There's a single Windows Server 2019 server that will be using for all our ADF's configuration and that's
called ADF's one.
Then there's a web server with IaaS installed that will be deploying a custom ASP.NET Core application
to later.
And it's that application that will be accessing using the different authentication methods and we'll
be able to see the claims returned by DFS.
There's also a Windows ten VM that I'll be using to do.
Most of the configuration from all of these VMs are on an internal network, which is just a Hyper-V
switch with a19 2.168.3 net network, which simulates these VMs being on an internal corporate network.
Then there's another network that's actually another virtual switch in Hyper-V that uses the external
network, my physical router controls, and that network has access to the internet, which will need
when we configure Federation with Azure later in the course.
But the real purpose of this network is to separate another server from the internal network, and that's
the Windows Server 2019 VM that will be installing Web Application Proxy onto.
So this server will accept incoming calls from VMs on this network when we test web application proxy.
The Web application proxy VM also has another network adapter that allows it to make calls into the
company's PRI network so it can publish applications to the Internet network as well as making ad fs
available externally.
That'll all make sense later in the course.
This is really the core of my test environment, but I will be making some additions throughout the
course.
When we federate with another organization.
I'll have another set of VMs to represent the other org and I'll be making some changes to the ADF's
service name when we federate with Azure AD later in the course.
I'll go through those changes in that module.
Next.
Let's talk about the certificates that ADF's uses before we create one to use with the ADF for a service
that will be installing.