Microsoft Office Tutorials and References
In Depth Information
Installing and configuring AD FS 2.0
INSIDE OUT Leveraging Windows Azure
Many decision makers in organizations realize the benefits of AD FS and regard it as a
requirement rather than an optional component. At the same time, they are concerned
that introducing AD FS adds a single point of weakness in the implementation of Office
365 because the 99.9 percent service level agreement (SLA) for Office 365 is
meaningless if AD FS is unavailable. This is where an Infrastructure as a Service (IaaS) solution
such as Windows Azure can make a difference. By implementing AD FS in Windows
Azure, organizations without the ability to create geo-redundant networks can take
advantage of a different type of cloud service to minimize the risk of an on-premises AD
FS environment becoming unavailable and thereby affecting the availability of Office
AD FS database
When deploying AD FS 2.0, you have the opportunity to use either the Windows Internal
Database (WID) that comes with AD FS, which is the default, or a dedicated SQL server. The
first AD FS server in the farm is known as the primary federation server , and subsequent AD
FS servers are known as secondary federation servers .
The AD FS database, regardless of whether you choose to deploy WID or SQL, is used to
store configuration information. The information in the database is replicated across the AD
FS servers in the farm. The database on the primary federation server is a read-write
database, while the ones on the secondary federation servers are read-only. In the event that
the primary federation server becomes permanently unavailable, you will need to promote
a secondary federation server to a primary federation server. There can be only one
primary federation server in the farm.
Deciding whether to use WID or a dedicated SQL server requires you to be aware of the
limitations of using WID. Using WID limits your AD FS farm to five servers. For most
organizations, except the largest of enterprises, this is usually not a problem. There are other
limitations when using WID that are not applicable to Office 365, such as being limited to
only 100 trust relationships. This limitation might become an issue if you are planning to
leverage your AD FS farm for other purposes besides Office 365.
Installing and configuring AD FS 2.0
Before starting the installation for AD FS 2.0, make sure you have completed all the
preceding tasks. At this point, you already should have completed the following:
Search JabSto ::

Custom Search