AD FS deployment topologies
There are a few different deployment models we can consider on planning AD FS deployment. In this section, let's look into different topologies and their characteristics.
Single Federation Server
This is the simple AD FS deployment using single AD FS server with WID. It will not have high availability (unless in host level). This is ideal for a lab environment or staging environment:

In the preceding example, we have web application, myapp.rebeladmin.com
, which needs to allow access via AD FS. We have one AD FS server in the setup with WID. It is behind the firewall and there is NAT and access rules setup to do the following:
- Map external IP address to
myapp.rebeladmin.com
, so users can make initial request from external networks. It is recommended to use TCP 443. - Map external IP address to
secure.rebeladmin.com
, map it to the IP address ofadfs1.rebeladmin.com
, and open TCP 443 from the external to allow access.
It should also have relevant external DNS records set...