Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
The first step in planning a deployment of Active Directory Federation Services (AD FS) is to determine the right deployment topology to meet the single sign-on (SSO) needs of your organization. The topics in this section describe the various deployment topologies that you can use with AD FS. They also describe the benefits and limitations associated with each deployment topology so that you can select the most appropriate topology for your specific business needs.
Before you read this deployment topology topic, we recommend that you first complete the tasks in the order shown in the following table.
|Review how AD FS data is stored and replicated to other federation servers in a federation server farm.||Understand the purpose of and the replication methods that can be used for the underlying data that is stored in the AD FS configuration database. This topic introduces the concepts of the configuration database and describes the two database types: Windows Internal Database (WID) and Microsoft SQL Server.||The Role of the AD FS Configuration Database|
|Select the type of AD FS configuration database that you will deploy in your organization.||Review the various benefits and limitations that are associated with using either WID or SQL Server as the AD FS configuration database, along with the various application scenarios that they support.||AD FS Deployment Topology Considerations|
To implement basic redundancy, load balancing, and the option to scale the Federation Service (if required), we recommend that you deploy at least two federation servers per federation server farm for all production environments, regardless of the type of database that you will use.
When you have reviewed the content in the previous table, proceed to the following topics in this section:
After you finish selecting your AD FS deployment topology, we recommend that you review the topic Planning for AD FS Server Capacity to determine the recommended number of servers that you will need to deploy to support this topology.