How To Set Up ADFS for Office 365 for Single Sign-On
Active Directory Federation Service (ADFS) may be a software component developed by Microsoft to supply Single Sign-On (SSO)
authorization to users on Windows Server Operating Systems(WSOS). ADFS allows users across organizational boundaries to access applications on Windows Server Operating Systems employing a single set of login credentials.
ADFS makes use of claims-based Access Control Authorization model to make sure security across applications using federated identity. Claims-based authentication may be a process during which a user is identified by a group of claims associated with their identity.
Step 1: Install Active Directory Federation Services
Add Active Directory Federation Service (ADFS) by using Add Roles and Features Wizard.
Notes for ADFS 2.0
If you're using Windows Server 2008, you want to download and install ADFS 2.0 to be ready to work with Office 365. You can obtain ADFS 2.0 from the subsequent Microsoft Download Center website:
Active Directory Federation Services 2.0 RTW
After the Installation, use Windows Update to download and install all Coming updates.
Step 2: Request a certificate from a third-party certification authority(CA) for the Federation server name
Office 365 requires a trusted certificate on your Active Directory Federation Service (ADFS) server. Therefore, you want to obtain a certificate from a third-party certification authority (CA).
When you customize the certificate request, confirm that you simply add the Federation server name within the Common name field.
In this video, we explain only the way to generate a certificate signing request (CSR). You must send the CSR file to a third-party certification authority (CA). The certification authority (CA) will return a signed certificate to you. Then, follow these Following steps to import the certificate to your computer certificate store:
Run Certlm.msc and open the local computer's certificate store.
In the navigation pane, Expand Personal, expand Certificate, right click the Certificate folder, then click Import.
About the Federation server name
The Federation Service name is that the Internet-facing name of your ADFS server. The Office 365 user are going to be redirected to the present domain for authentication. Therefore, confirm that you simply add a public A record for the name .
Step 3: Configure ADFS
You cannot manually A name because the Federation server name. The name is decided by the topic name (Common name) of a certificate within the local computer's certificate store.
Notes for ADFS 2.0
In ADFS 2.0, the Federation server name is decided by the certificate that binds to "Default Web Site" in Internet Information Services (IIS). You must bind the new certificate to the Default website before you configure Active Directory Federation Service (ADFS).
You can use any account because the service account. If the service account's password is expired, ADFS will pack up . Therefore, confirm that the password of the account is about to never expire.
Step 4: Download Office 365 tools
Windows Azure Active Directory Module (WAADM) for Windows PowerShell and Azure Active Directory sync appliance are available in Office 365 portal. To obtain the tools, click Active Users, then click Single sign-on: found out .
Step 5: Add your domain to Office 365
The video doesn't explain the way to add and verify your domain to Office 365. For more information that procedure, see Verify your domain in Office 365.
Step 6: Connect ADFS to Office 365
To connect ADFS to Office 365, run the subsequent commands in Windows Azure Directory Module for Windows PowerShell.
Note within the Set-MsolADFSContext command, specify the FQDN of the ADFS server in your internal domain rather than the Federation server name.
PowerShell
Copy
Enable-PSRemoting
Connect-MsolService
Set-MsolADFSContext –computer
Convert-MsolDomainToFederated –domain
If the commands run successfully, you should see the following:
A "Microsoft Office 365 Identify Platform" Relying Party Trust is added to your Active Directory Federation Service (ADFS) server.
Users who use the custom name as an email address suffix to log in to the Office 365 portal are redirected to your ADFS server.
Step 7: Sync local Active Directory user to Office 365
If your internal name differs from the external name that's used as an email address suffix, you've got to feature the external name as an alternate UPN suffix in the local Active Directory domain. For example, the interior name is "company.local" but the external name is "company.com." during this situation, you've got to feature "company.com" as an alternate UPN suffix.
Sync the user accounts to Office 365 by using Directory Sync Tool (DST)
Notes for ADFS 2.0
If you're using ADFS 2.0, you want to change the UPN of the user account from "company.local" to "company.com" before you sync the account to Office 365. Otherwise, the user will not be validated on the ADFS server.
Step 8: Configure the client Desktop for Single Sign-On
After you add the Federation server name to the local Intranet zone in Internet Explorer, the NTLM authentication is employed when users attempt to authenticate on the ADFS server. Therefore, they're not prompted to enter their credentials.
Administrators can implement Group Policy settings to configure one Sign-On solution on client computers that are joined to the domain.
For More Information : https://officecomsetup-msofficesetup.com/
: +1-800-795-0713
Comments
Post a Comment