
close
close
Chance to win $250 in Petri 2023 Audience Survey
Welcome back! In the first article of this series we began integrating and installing local Active Directory with Office 365. Verifying local account UPN suffixes was covered as well as downloading and installing Microsoft Active Directory Federation Services 2.0 (AD FS 2.0 for short). It’s time to complete federation and get everything ready for Single Sign-On.
Before putting the cart before the horse, it’s important to verify that some prep work has been completed. First, an SSL Certificate for the domain to be federated is bound to the default website of the server running AD FS 2.0. It’s great if you have an internal certificate authority, but if not I strongly recommend investing in an SSL cert from a commercial authority. They’re relatively cheap, and most importantly they’re easy to get up and going. Note: It’s also necessary to make sure the domain to be federated is added and verified within the Office 365 Admin Center. If either of these tasks is not completed then the instructions in this article will fail miserably.
In the third and final part of this series, I’ll go over how to activate local Active Directory synchronization with Office 365, assign licenses to select users, and test everything for proper operation,
Download and install the Microsoft Online Services Sign-In Assistant for IT Professionals. This software is used to facilitate Single Sign-On on client PCs, but it’s also a requirement for the Windows Azure Active Directory Module for Windows PowerShell, which is a tool we’ll be using.
Download and install the Windows Azure Active Directory Module for Windows PowerShell to the computer running Microsoft Active Directory Federation Services 2.0. This tool leverages the power of PowerShell to complete some of the necessary administration tasks.
The time has arrived to configure Active Directory Federation Services 2.0:
Now, it’s better to be safe than sorry. To avoid problems, verify that the domain added earlier to Office 365 Admin Center — in other words, the domain to be federated — is marked active.
Now that AD FS 2.0 is configured and the other prerequisites are in place, it’s time to convert the domain added to Office 365 into a federated domain.
Office 365 and the domain name awssol.com are now federated. Next up is to synchronize Active Directory with Office 365, assign licenses to select users, and test everything for proper operation. All this, along with a few extra tips for success, will be covered in the final article of this series. Until then, sit back, relax, and enjoy some of the other great articles here on Petri.co.il!
More in Active Directory
Microsoft Releases Update to Streamline Exchange Online License Assignments
Jan 24, 2023 | Rabia Noureen
How to Export Active Directory Users to CSV With PowerShell and ADUC
Jan 23, 2023 | Michael Reinders
ManageEngine ADSelfService Plus: Protect On-Premises and Cloud Services from Password Attacks with Multi-factor Authentication
Jan 12, 2023 | Michael Reinders
Microsoft 365 to Launch New $1.99/Month Basic Subscription with 100 GB of OneDrive Storage
Jan 11, 2023 | Rabia Noureen
Samsung Releases Server-Side Fixes for Microsoft Intune Android 13 Enrollment Issues
Dec 22, 2022 | Rabia Noureen
Most popular on petri