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.
Important
The following installation instructions assume that all the prerequisites were met.
Note
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 more 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
Sign in to the domain joined server with enterprise admin permissions.
Open a web browser and sign-in to the Azure portal using cloud-only global admin credentials.
On the left menu, select Azure Active Directory.
Select Azure AD Connect, and then select Manage Azure AD cloud sync.

Select Download agent, and select Accept terms & download.
Once the Azure AD Connect Provisioning Agent Package has completed downloading, run the AADConnectProvisioningAgentSetup.exe installation file from your downloads folder.
On the splash screen, select I agree to the license and conditions, and then select Install.

Once the installation operation completes, the configuration wizard will launch. Select Next to start the configuration.

Sign in with your Azure AD global administrator account. If you have Internet Explorer enhanced security enabled, it will block the sign-in. If so, close the installation, disable Internet Explorer enhanced security, and restart the Azure AD Connect Provisioning Agent Package installation.

On the Configure Service Account screen, select a group Managed Service Account (gMSA). This account is used to run the agent service. If a managed service account is already configured in your domain, you might skip this screen. If prompted, choose either:
- Create gMSA which lets the agent create the provAgentgMSA$ managed service account for you. The group managed service account (for example, CONTOSO\provAgentgMSA$) will be created in the same Active Directory domain where the host server has joined. To use this option, enter the Active Directory domain administrator credentials.
- Use custom gMSA and provide the name of the managed service account.

To continue, select Next.
On the Connect Active Directory screen, if your domain name appears under Configured domains, skip to the next step. Otherwise, type your Active Directory domain name, and select Add directory.

Sign in with your Active Directory domain administrator account. The domain administrator account shouldn't have password change requirements. In case the password expires or changes, you'll need to reconfigure the agent with the new credentials. This operation will add your on-premises directory. Select OK, then select Next to continue.

The following screenshot shows an example of contoso.com configured domain. Select Next to continue.

On the Configuration complete screen, select Confirm. This operation will register and restart the agent.

Once this operation completes, you should be notified that Your agent configuration was successfully verified. You can select Exit.

If you still get the initial splash screen, select Close.
Verify agent installation
Agent verification occurs in the Azure portal and on the local server that is running the agent.
Azure portal agent verification
To verify the agent is being registered by Azure AD, follow these steps:
Sign in to the Azure portal.
On the left menu, select Azure Active Directory.
Select Azure AD Connect and then select Manage Azure AD cloud sync.
On the Azure AD Connect cloud sync screen, select Review all agents.
On the On-premises provisioning agents screen, you'll see the agents you've installed. Verify that the agent in question is there and is marked active.
On the local server
To verify that the agent is running, follow these steps:
Sign in the server with an administrator account
Open Services by either navigating to it or by going to Start/Run/Services.msc.
Under Services, make sure Microsoft Azure AD Connect Agent Updater and Microsoft Azure AD Connect Provisioning Agent are present and the status is Running.
Important
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.
Enable password writeback in Azure AD Connect cloud sync
To use password writeback and enable the self-service password reset (SSPR) service to detect the cloud sync agent, you need to use the Set-AADCloudSyncPasswordWritebackConfiguration cmdlet and tenant’s global administrator credentials:
Import-Module "C:\\Program Files\\Microsoft Azure AD Connect Provisioning Agent\\Microsoft.CloudSync.Powershell.dll"
Set-AADCloudSyncPasswordWritebackConfiguration -Enable $true -Credential $(Get-Credential)
For more information on using password writeback with Azure AD Connect cloud sync, see Tutorial: Enable cloud sync self-service password reset writeback to an on-premises environment (preview).
Installing against US government cloud
By default, the Azure Active Directory (Azure AD) Connect provisioning agent installs against the default Azure cloud environment. If you're installing the agent for use in the US government, follow these steps:
In step #7 above, instead of select Open file, go to start run and navigate to the AADConnectProvisioningAgentSetup.exe file. In the run box, after the executable, enter ENVIRONMENTNAME=AzureUSGovernment and select Ok.
Password hash synchronization and FIPS with cloud sync
If your server has been locked down according to Federal Information Processing Standard (FIPS), then MD5 is disabled.
To enable MD5 for password hash synchronization, perform the following steps:
- Go to %programfiles%\Microsoft Azure AD Connect Provisioning Agent.
- Open AADConnectProvisioningAgent.exe.config.
- Go to the configuration/runtime node at the top of the file.
- Add the following node:
<enforceFIPSPolicy enabled="false"/> - Save your changes.
For reference, this snippet is what it should look like:
<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>
</configuration>
For information about security and FIPS, see Azure AD password hash sync, encryption, and FIPS compliance.





