In this article, we will go through the steps to setup and configure ADFS 2.0. If you have missed the first part, read it here. ADFS is required for single sign-on access to Office 365 services.
ADFS for Office 365 is NOT about enabling the ADFS role from Server Manager. ADFS Version 2 is required for our scenario. Download ADFS v2.0 from here depending on the OS. A dedicated ADFS server is not required for small environments, the recommendation is to have it running on atleast two domain controllers. I will be installing it only on one domain controller as it is a test lab.
After downloading ADFS v2, run the setup. Click Next on the welcome screen.
Accept the license and click Next. Select “Federation Server” and click Next
The wizard shows the pre-reqs and if it is not present, the setup will install it for you. Click Next
The pre-reqs get installed and the setup finishes. The “completed” setup wizard will have a tick box selected which will launch the ADFS management snap-in. Click Finish.
Install Update Rollup1 for ADFS v2, request the rollup from here. It is a standard install, click next and finish.
After the rollup is installed, launch ADFS 2.0 Management from Start –> Administrative tools. Click on “ADFS 2.0 Federation Server Configuration Wizard”.
Select “Create a new Federation Service” and click Next.
Select “New Federation Server Farm” and click Next.
A new certificate will be already there, created by the ADFS setup. Select the cert and the federation service name, which will be the taken from the subject field of the cert.
A service account is required, a normal domain user will do. Make sure you select “password never expires” while creating the account. Select the service account in the wizard & type in the password.
Click Next on the summary wizard.
Make sure everything is green and click close.
To verify that everything has been configured properly, open up a browser from a client and navigate to https://adfsserverfqdn/adfs/fs/federationserverservice.asmx. Continue to the website and you should see an xml output.
That is it for part 2, stay tuned for part 3!