Share via

Deploy and configure AD FS

  • Article

 

Applies To: Dynamics 365 (on-premises), Dynamics CRM 2016

A variety of identity providers can be used with Microsoft Dynamics 365 Server. This document uses Active Directory Federation Services (AD FS) for the security token service. For information on configuring identity federation deployment between AD FS and other identity providers, see: AD FS 2.0 Step-by-Step and How To Guides.

Important

If you are deploying on Windows Server 2012, and you are installing AD FS on the same server as Microsoft Dynamics 365, AD FS installs on the default website. Before installing AD FS, you must create a new website for Microsoft Dynamics 365 Server.

This does not apply to Windows Server 2012 R2 as AD FS in Windows Server 2012 R2 does not depend on IIS.

Deploy a federation server

For information on deploying an AD FS server, see AD FS Deployment.

Configure AD FS for Windows Server 2012 R2

To configure AD FS as a stand-alone federation server for Microsoft Dynamics 365 Server claims authentication, do the following:

  1. Open the Windows Server 2012 R2 Add Roles and Features Wizard and add the Active Directory Federation Services server role.

  2. Proceed through the wizard. Click Configure the federation service on this server.

  3. On the Welcome page in the Active Directory Federation Services Configuration Wizard, choose an option for a federation server, and then click Next.

  4. Proceed through the wizard. On the Specify Service Properties page, select your TLS/SSL certificate, enter a Federation Service Name, and then enter a Federation Service Display Name.

    Note

    You only add the federation service name if you are using a wildcard certificate for the AD FS website.

    If you install AD FS and Microsoft Dynamics 365 Server on the same server, do not use the same URL for the Federation Service name and internal claims access to Microsoft Dynamics 365 Server. For example, if you use sts1.contoso.com for the Federation Service name, do not use https://sts1.contoso.com for internal Microsoft Dynamics 365 data access.

    AD FS: Specify Service Properties

  5. Proceed through and complete the Active Directory Federation Services Configuration Wizard. Close the Add Roles and Features Wizard.

  6. If you have not created a host record in DNS for the federation server name you specified in Step 4 previously, do so now.

For more information, see Configure a Federation Server.

Verifying AD FS installation

Use the following steps to verify the AD FS installation:

  1. On the AD FS server, open Internet Explorer.

  2. Browse to the URL of the federation metadata. For example, https://sts1.contoso.com/federationmetadata/2007-06/federationmetadata.xml

    You may need to turn on Compatibility View in Internet Explorer.

  3. Verify that no certificate-related warnings appear. If necessary, check your certificate and DNS settings.

URL of federation metadata

See Also

Implement claims-based authentication: internal access

© 2016 Microsoft. All rights reserved. Copyright