I will show you how to find Azure AD Connect in your environment using Active Directory Users and Computers. I visited a customer who needed to force a delta sync using Azure AD Connect. The person responsible was absent, which meant that nobody knew where it was installed.
I found a simple method of finding the server after some research, but it depends on the service account. It turns out that the installer writes the servername to the description field of the GMSA account during installation.
Azure AD Connect is the engine that synchronizes the identities from your Active Directory catalog to Azure Active Directory. You install it on a server and then connect it to you Azure AD.
This application enables you to use a concept called Hybrid Identity, which means that you can use the same account in your on-premises environment as in Azure. This includes using the same username and password, using your email address as username, and also giving you the option to use Single Sign-On (SSO) to Office 365 services.
You can read more about Azure AD Connect here and you can download the latest version here.
Open Active Directory Users and Computers for your domain and search for “MSOL”. This will return all the accounts starting with that word.
Right-click this account and go Properties. The description field will contain the information we need. For example it includes servername, installation identifier and the tenant name that you are using.
Account created by Microsoft Azure Active Directory Connect with installation identifier 9caea38d84j24bcc8d4a724r9e296c77 running on computer SERVERNAME configured to synchronize to tenant domain.onmicrosoft.com. This account must have directory replication permissions in the local Active Directory and write permission on certain attributes to enable Hybrid Deployment.
Using this method is very simple and will save you alot of time instead of digging through all servers.
Give me a shout if you need help or if this doesn’t work for you.