Install the Azure AD Connect provisioning agent
This article walks you through the installation process for the Azure Active Directory (Azure AD) Connect provisioning agent and how to initially configure it in the Azure portal.
The following installation instructions assume that all the prerequisites were met.
This article deals with installing the provisioning agent by using the wizard. For information on installing the Azure AD Connect provisioning agent by using a command-line interface (CLI), see Install the Azure AD Connect provisioning agent by using a CLI and PowerShell.
For additional information and an example, see the following video.
Group Managed Service Accounts
A group Managed Service Account (gMSA) is a managed domain account that provides automatic password management, simplified service principal name (SPN) management, and the ability to delegate the management to other administrators. It also extends this functionality over multiple servers. Azure AD Connect cloud sync supports and recommends the use of a group Managed Service Account for running the agent. For more information on a group Managed Service Account, see Group Managed Service Accounts.
Upgrade an existing agent to use the gMSA
To upgrade an existing agent to use the group Managed Service Account created during installation, update the agent service to the latest version by running AADConnectProvisioningAgent.msi. Now run through the installation wizard again and provide the credentials to create the account when prompted.
Install the agent
To install the agent:
Sign in to the server you'll use with enterprise admin permissions.
Sign in to the Azure portal, and then go to Azure Active Directory.
On the menu on the left, select Azure AD Connect.
Select Manage cloud sync > Review all agents.
Download the Azure AD Connect provisioning agent from the Azure portal.
Accept the terms and select Download.
Run the Azure AD Connect provisioning installer AADConnectProvisioningAgentSetup.msi.
On the Microsoft Azure AD Connect Provisioning Agent Package screen, accept the licensing terms and select Install.
After this operation finishes, the configuration wizard starts. Sign in with your Azure AD global administrator account.
On the Configure Service Account screen, select either Create gMSA or Use custom gMSA. If you allow the agent to create the account, it will be named provAgentgMSA$. If you specify Use custom gMSA, you're prompted to provide this account.
Enter the domain admin credentials to create the group Managed Service account that will be used to run the agent service. Select Next.
On the Connect Active Directory screen, select Add Directory. Then sign in with your Active Directory administrator account. This operation adds your on-premises directory.
Optionally, you can manage the preference of domain controllers the agent will use by selecting the Select domain controller priority checkbox and ordering the list of domain controllers. Select OK.
On the Agent installation screen, confirm settings and the account that will be created and select Confirm.
After this operation finishes, you should see Your agent installation is complete. Select Exit.
If you still see the initial Microsoft Azure AD Connect Provisioning Agent Package screen, select Close.
Verify agent installation
Agent verification occurs in the Azure portal and on the local server that's running the agent.
Azure portal agent verification
To verify the agent is being seen by Azure:
Sign in to the Azure portal.
On the left, select Azure Active Directory > Azure AD Connect. In the center, select Manage cloud sync.
On the Azure AD Connect cloud sync screen, select Review all agents.
On the On-premises provisioning agents screen, you see the agents you installed. Verify that the agent in question is there and is marked active.
On the local server
To verify that the agent is running:
Sign in to the server with an administrator account.
Open Services by going to it or by selecting Start > Run > Services.msc.
Under Services, make sure Microsoft Azure AD Connect Agent Updater and Microsoft Azure AD Connect Provisioning Agent are there and their status is Running.
The agent has been installed, but it must be configured and enabled before it will start synchronizing users. To configure a new agent, see Create a new configuration for Azure AD Connect cloud sync.