In this blog post I connect my Office 365 with my on premise Active Directory Based on the Azure AD Connect
Azure AD Connect allows you to quickly onboard to Azure AD and Office 365
Integrating your on-premises directories with Azure AD makes your users more productive by providing a common identity for accessing both cloud and on-premises resources. With this integration users and organizations can take advantage of the following:
- Organizations can provide users with a common hybrid identity across on-premises or cloud-based services leveraging Windows Server Active Directory and then connecting to Azure Active Directory.
- Administrators can provide conditional access based on application resource, device and user identity, network location and multifactor authentication.
- Users can leverage their common identity through accounts in Azure AD to Office 365, Intune, SaaS apps and third-party applications.
- Developers can build applications that leverage the common identity model, integrating applications into Active Directory on-premises or Azure for cloud-based applications
Azure AD Connect makes this integration easy and simplifies the management of your on-premises and cloud identity infrastructure.
As using the Office 365 domain the .Local are useless you can’t resolve them over the internet.
Installing Microsoft Azure Active Directory Connect
When Installing Microsoft Azure Active Directory Connect you will need the pre-requisite steps in Azure AD Connect: Hardware and prerequisites.
In the next steps you can customize the installation
I change the Default install Location
I use a dedicated SQL server that holds my Sync DB and this can be a my sql express DB.
I pre Created a Service Account that has the right amount of rights else you will see an account like MSOL_46396c1d8b6e.
I used my 356 account and the password and I use Password sync.
Connect my local Active Directory with my own local Account. Filling in the blanks and use Add Directory
In the next steps you can customize the sync properties and the OU that you want to sync. If you pick the whole AD then all objects are synced and Deletion in the Web is not real funny.
After I picked the OU for filtering we are ready for the first sync.
as you can choose sync right now or later
as you can see there is a new sync user created in Office 365
and on the server where you installed Microsoft Azure Active Directory Connect there is a troubleshooting tool
it can be found : C:\Program Files\Microsoft Azure AD Sync\UIShell\miisclient.exe
This is the installation on premise but you can also use the Office 365 Wizard to sync your AD.
Logon as an Office 365 Global Administrator and in the Admin Center Settings there is an Azure AD option
But Remember : When you are using a Free or trail subscription the usage of the Azure AD Free Version will not work you will need to use the Azure AD instead.
Connecting to the Dirsync wizard and starting the Readiness Wizard will guide you to 3 steps
Step 1 a new popup will do the checks
A little download will popup
The Tools are installed and will run. If not make sure you have admin rights on the machine that is running this assistant
Now that the scan is ready and completed we can see some details about the scan
my demo Ad is not that big
it also scans my Domains / UPC records and shows me what is suitable and what not
my domains in the O365 suite
After correcting the domain setup I can use the domains for O365.
A little clean up is needed in my AD
The next step is installing Azure AD Connect I already did this above and I’m running this on the same machine so no problem to go further.
the last step and the AD sync is working.
So this is all a lot of steps but basically it is al very simple when you have the right info and the domains setup up then you are good to go.
And remember don’t sync the entire AD just as test.
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w