Planifier et déployer les services Active Directory Federation 2.0 pour une utilisation avec un seul abonnement

Plan for and deploy Active Directory Federation Services 2.0 for use with single sign-on

This article provides streamlined planning and deployment instructions for Microsoft Office 365 for enterprises administrators who have determined that they require single sign-on access and who currently do not have an Active Directory Federation Services 2.0 infrastructure deployed in their organization.

If you currently have an AD FS 2.0 production environment and are interested in providing your users with single sign-on access to Office 365 services, you can go directly to the next step: Install and configure the Microsoft Online Services Module for Windows PowerShell for single sign-on.

For additional overview and configuration information about AD FS 2.0, see the Next step and additional references section in this article.

Overview of the AD FS 2.0 for Office 365 single sign-on solution

You can deploy a new AD FS 2.0 infrastructure to provide your Active Directory users, who are logged on to computers located physically on the corporate network or that are logged on remotely to the corporate network, with single sign-on access to Office 365 services using their corporate domain credentials.

Once you have deployed your AD FS 2.0 production environment on-premises, you will need to establish a relying party trust relationship between the AD FS 2.0 federation server farm and Office 365. This relying party trust acts as a secure channel where authentication tokens can safely pass between your organization and Office 365 in order to facilitate single sign-on access to Office 365.

The following image illustrates how local Active Directory users can obtain the necessary authentication tokens from on-premises AD FS 2.0 federation servers that can redirect the user’s requests through the relying party trust to allow them single sign-on access to Office

...