![]() I am now ready to configure the pre-requisites for ADFS which is the Windows Web Server role and an SSL certificate. I have also added a separate member server (called CIAOPS365-ADFS) to this domain that will function as the ADFS server. I have also assigned the appropriate Office 365 licenses for active users. This ensures that the UPN of the local AD matches those in Office 365. I have also installed and configured the custom domain into my Office 365 tenant. I am successfully synchronising user information from the local Active Directory (AD) to Office 365 via Azure AD Connect. The local domain is called I have already successfully installed and configured Azure AD Connect on this DC. Prior to the steps here, I already have established a domain controller (DC) on the network. This means installing the Windows Server Web Server role and assigning a certificate to this Windows Web Server. This post will take you through the initial process of configuring the pre-requisites on the ADFS server. ![]() I’ll break these down into a number of posts and then bring everything together as a single point of reference at the end. What I plan to cover in upcoming articles is how to establish federated identities (i.e. I’ve also detailed how to install Azure AD Connect (which replaces both Azure AD Sync and DIRSYNC) and why it is necessary for both synchronised and federated Office 365 identities. I’ve detailed the different Office 365 Identity options previously.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |