How To Setup Azure Active Directory Connect For Your Office 365 Tenancy
You want to synchronize an On-Premises Active Directory environment with your Office 365 / Azure AD to simplify your licensing and provisioning process, as well as utilize Password Synchronization. In this Snip you’ll learn where to download, how to install, and how to perform an initial configuration of your Azure AD Connect Synchronization Server. We will also learn to utilize the ADSync PowerShell Module to trigger a new Sync Cycle to Azure AD at will. Your local and Azure Active Directory instances will be communicating and synchronizing all of their data in no time!
Prerequisites Include: Office 365 Tenancy (Licensed or Trial), Microsoft Active Directory Domain, Non-Domain Controller Server for AD Connect to reside on.
Prerequisites include: Office 365 Tenancy (Licensed or Trial), Microsoft Active Directory Domain, Non-Domain Controller Server for AD Connect to reside on.
In this video we're going to show you how to set up Azure AD connect for your Office 365 tenants as you can see here. I do have a blank Office 365 tenant see where only my global administrator is currently set up from here in the Office 365 tenancy to begin the process of synchronizing your local on Prem AD. You're going to want to download the Office 365 AD connect package from Microsoft. The package from Microsoft can be found at the link that I'm providing here in the description of this video as well as. Right here on screen you should be able to find AD connect to the MSI package from any web browser an any search engine just by looking for it. After clicking on the link. This would be the download page that you would view and then download Azure Active Directory Connect. We are now going to proceed with the installation. The installation is fairly straightforward. I'm not going to go into too much detail but you do want to agree to their license terms. Here you have the option to synchronize using their express settings, which is what Microsoft recommends or you can customize it. If you have a very particular environment. I'm going to use express here for our test lab. After clicking on expressed settings here is we're going to put in your global administrator account. That's going to be the first one, that you create in your Office 365 tenant see so every account has 1. And this is going to be the account that you use to sign into your local Active Directory. This is so that the synchronization service can go retrieve all of those user objects and security group objects and then bring those into Office 365 for you. One thing to note is this account does need to be in the enterprise administrator group that's the built in Enterprise Administrator Group of your local AD. The built in administrator of your local Active Directory will be in this group by default. If you're like me and use a test lab with a sub domain prefix then go ahead and click on the UPN suffix was will not match this way. You could still sync. All of your objects and you can come and clean up the suffix a little bit later in your Office 365 maturity. Here you have the option to start an initial synchronization as soon as this installation finishes. I'm going to Uncheck. This box because I want to show you how to use PowerShell. To actually trigger. This initial synchronization and any other Delta or change based synchronizations later on this installation will take a moment. With our configuration complete we're going to hit exit and get out of here right now. And we do want to use PowerShell to initialize that first synchronization to Office 365 because right now. No objects from our local on Prem have been synced if after the installation of your AD sync synchronization service. PowerShell will have a newly installed module that module was going to be the AD sync module. You could check if it's installed by running the following command. And right here near the bottom you can see that there are a couple of different modules that are installed the one that we're going to focus on is the AD sync module. You have a couple of different options. With this command, let it's the start AD sync sync cycle. You're going to get a little redundant. When you say it out loud. The policy type is going to be the type of synchronization that you want to run the initial is going to be a full synchronization full cycle of that and then there's also a Delta option, which would be only the changes. You've made to your local Active Directory since the last synchronization. We're going to do the initial since we did not complete that as part of our installation process. We could check that this policy is running an has run by looking at the synchronization service logs here in our logs. You could see that the full synchronization that we just kicked off with PowerShell is showing as it has successfully completed as well as the new exported attributes and here you can see in the ads section of the export statistics that we added 15 new objects to our Office 365 tenancy. Let's check out our work if we come here to our Office 365 Admin Center and refresh. The page you can now see that all of these additional newly synched objects are available for licensing for use in Office 365. I hope that this video is help you with your synchronization of your local AD in cloud and thank you for watching.