Sharon provides an overview of Azure Active Directory Connect Health, which allows you to monitor your on-premises health and synchronize from on the premises to Azure Active Directory.
- [Instructor] Now that we have Azure Active Directory Connect installed on our server, we can go ahead and actually monitor the health of that server and the synchronization. As you can see, I've already logged into Azure. I'm going to click on Azure Active Directory. And we'll go ahead and click in Azure Active Directory Connect. One thing I do want to point out, you will notice that sync is now enabled. It took a few minutes after the Azure Active Directory Connect install for it to be registered within Azure. We can see now our sync status has been enabled.
We can see the last sync was 13 hours ago. And that is because the servers were shut down in the evening. Next I'm going to go ahead and click on Azure Active Directory Connect Health. I'm going to scroll over just a little bit. Give us a little more real estate. And right from here we can see that we have an issue, right off the top. We can see here that we have an unhealthy status for our sync. I'm going to go ahead and click in it. Now we can drill down into our server a little bit.
Here it's on our on-premise server. We can tell the issue is on OnPremiseDC, and it is unhealthy. Let's drill down a little bit more. And here we can get a little bit more information. So we have some alerts. Something's been resolved in the last 24 hours. And we can drill into these as we require. From here you'll notice that our health service data is not up to date, so this is why we're triggering the error. We can see when the issue was reported and last detected. For our active alerts, we can see it's not resolved yet.
And that's because the server itself is still booting up. Once the server is up and running and sync starts kicking in, this will move to resolved, as it did in the one below. We had an issue last night, the health service data was not up to date, it was a warning. And we can see that it resolved itself. And we can drill in a little bit more and find out a little bit more details on that error. Going to go ahead and close these. We can also see when the last export to Azure Active Directory was.
And this occurred yesterday. And based on the date, we know the last time that data was exported from our on-premise active directory into Azure Active Directory was on February 9th, at 5:30 a.m. We can also see the profile latency as well. I'm going to go ahead and close this blade. I'm going to go ahead and click on settings. And here I have the option to turn off uploading all the error logs. It'll be up to you. By default this is set to on. I'm going to leave it as on, I just wanted to show it to you.
I'm going to go ahead and close this. One thing I want to point out is I have Active Directory for Domain Services Health installed. I click in here, I can actually see our domains themselves. And we can click on these domains and or the sites and get additional information from those domains. I'm going to go ahead and click on one. On our Domain Controller we can see the FSMO roles as well as the site and the status. Keep in mind that Azure Active Directory Domain Services is in preview right now.
In order to have the Active Directory Domain Services module up and running here I actually had to install it on my server itself. It is a quick little install. All it is is just a PowerShell script. In order to find that install, you're going to click in Quick Start and you'll go ahead and download the Azure Active Directory Connect Health Agent for AD DS. Similarly, if you are running Active Directory Federation Services, you could download the Azure AD Connect Health Agent for AD FS, and install those on your servers as required.
The Azure Active Directory Connect Agent itself is already installed when you install Azure Active Directory Connect. Last thing I want to point out here is configure. Down at the bottom and I'm going to click on Configure. By default, your Azure Active Directory Connect Health Agent will always be updated to the most current version. And you do have the option to allow Microsoft to access your tenant's health for troubleshooting. Again, this will be totally up to you whether or not you want to allow Microsoft to use that data to help improve their processes.
I'm going to leave these as is. And that's all there is to it for Azure Active Directory Connect Health.
- Azure AD
- Adding company branding
- Adding a custom domain
- AD Connect configuration
- AD Connect Health
- Administering users and groups
- Configuring SaaS applications
- Granting conditional access
- Revoking access
- Application proxy and discovery
- Integrating web and desktop applications
- Creating an Azure AD B2C directory
- Registering an application
- Creating a Microsoft identity