Implementing password synchronization with Azure AD Connect sync

This topic provides you with the information you need to synchronize your user passwords from an on-premises Active Directory (AD) to a cloud-based Azure Active Directory (Azure AD).

What is password synchronization

The probability that you are blocked from getting your work done due to a forgotten password is related to the number of different passwords you need to remember. The more passwords you need to remember, the higher the probability to forget one. Questions and calls about password resets and other password-related issues demand the most helpdesk resources.

Password synchronization is a feature to synchronize user passwords from an on-premises Active Directory to a cloud-based Azure Active Directory (Azure AD). This feature enables you to sign in to Azure Active Directory services (such as Office 365, Microsoft Intune, CRM Online, and Azure AD Domain Services) using the same password you are using to sign in to your on-premises Active Directory.

What is Azure AD Connect

By reducing the number of passwords your users need to maintain to just one, password synchronization helps you to:

  • Improve the productivity of your users
  • Reduce your helpdesk costs

Also, if you select to use Federation with AD FS, you can optionally enable password synchronization as a backup in case your AD FS infrastructure fails.

Password synchronization is an extension to the directory synchronization feature implemented by Azure AD Connect sync. To use password synchronization in your environment, you need to:

  • Install Azure AD Connect
  • Configure directory synchronization between your on-premises AD and your Azure Active Directory
  • Enable password synchronization

For more details, see Integrating your on-premises identities with Azure Active Directory


For more details about Active Directory Domain Services that are configured for FIPS and password synchronization, see Password Sync and FIPS.

How password synchronization works

The Active Directory domain service stores passwords in form of a hash value representation of the actual user password. A hash value is a result of a one-way mathematical function (the "hashing algorithm"). There is no method to revert the result of a one-way function to the plain text version of a password. You cannot use a password hash to sign in to your on-premises network.

To synchronize your password, Azure AD Connect sync extracts your password hash from the on-premises Active Directory. Extra security processing is applied to the password hash before it is synchronized to the Azure Active Directory authentication service. Passwords are synchronized on a per-user basis and in chronological order.

The actual data flow of the password synchronization process is similar to the synchronization of user data such as DisplayName or Email Addresses. However, passwords are synchronized more frequently than the standard directory synchronization window for other attributes. The password synchronization process runs every 2 minutes. You cannot modify the frequency of this process. When you synchronize a password, it overwrites the existing cloud password.

The first time, you enable the password synchronization feature, it performs an initial synchronization of the passwords of all in-scope users. You cannot explicitly define a subset of user passwords you want to synchronize.

When you change an on-premises password, the updated password is synchronized, most often in a matter of minutes. The password synchronization feature automatically retries failed synchronization attempts. If an error occurs during an attempt to synchronize a password, an error is logged in your event viewer.

The synchronization of a password has no impact on the currently logged on user. Your current cloud service session is not immediately affected by a synchronized password change that occurs while you are signed in to a cloud service. However, when the cloud service requires you to authenticate again, you need to provide your new password.


Password sync is only supported for the object type user in Active Directory. It is not supported for the iNetOrgPerson object type.

How password synchronization works with Azure AD Domain Services

You can also use the password synchronization feature to synchronize your on-premises passwords to the Azure AD Domain Services. This scenario allows the Azure AD Domain Services to authenticate your users in the cloud with all the methods available in your on-premises AD. The experience of this scenario is similar to using the Active Directory Migration Tool (ADMT) in an on-premises environment.

Security considerations

When synchronizing passwords, the plain-text version of your password is not exposed to the password synchronization feature, to Azure AD, or any of the associated services.

Also, there is no requirement on the on-premises Active Directory to store the password in a reversibly encrypted format. A digest of the Active Directory password hash is used for the transmission between the on-premises AD and Azure Active Directory. The digest of the password hash cannot be used to access resources in your on-premises environment.

Password policy considerations

There are two types of password policies that are affected by enabling password synchronization:

  1. Password Complexity Policy
  2. Password Expiration Policy

Password complexity policy
When you enable password synchronization, the password complexity policies in your on-premises Active Directory override complexity policies in the cloud for synchronized users. You can use all valid passwords of your on-premises Active Directory to access Azure AD services.


Passwords for users that are created directly in the cloud are still subject to password policies as defined in the cloud.

Password expiration policy
If a user is in the scope of password synchronization, the cloud account password is set to "Never Expire". You can continue to sign in to your cloud services using a synchronized password that has been expired in your on-premises environment. Your cloud password is updated the next time you change the password in the on-premises environment.

Overwriting synchronized passwords

An administrator can manually reset your password using Windows PowerShell.

In this case, the new password overrides your synchronized password and all password policies defined in the cloud are applied to the new password.

If you change your on-premises password again, the new password is synchronized to the cloud, and overrides the manually updated password.

Enabling password synchronization

Password synchronization is automatically enabled, when you install Azure AD Connect using the Express Settings. For more details, see Getting started with Azure AD Connect using express settings.

If you use custom settings when you install Azure AD Connect, you enable password synchronization on the user sign-in page. For more details, see Custom installation of Azure AD Connect.

Enabling password synchronization

Password synchronization and FIPS

If your server has been locked down according to Federal Information Processing Standard (FIPS), then MD5 has been disabled.

To enable MD5 for password synchronization, perform the following steps:

  1. Go to %programfiles%\Azure AD Sync\Bin.
  2. Open miiserver.exe.config.
  3. Go to the configuration/runtime node (at the end of the file).
  4. Add the following node: <enforceFIPSPolicy enabled="false"/>
  5. Save your changes.

For reference, this snip is how it should look like:

            <enforceFIPSPolicy enabled="false"/>

For information about security and FIPS see AAD Password Sync, Encryption and FIPS compliance

Troubleshooting password synchronization

If passwords are not synchronizing as expected, it can either be for a subset of users or for all users.

Troubleshoot one object that is not synchronizing passwords

You can easily troubleshoot password synchronization issues by reviewing the status of an object.

Start in Active Directory Users and Computers. Find the user and verify that User must change password at next logon is unselected.

Active Directory productive passwords

If it is selected, then ask the user to sign in and change the password. Temporary passwords are not synchronized to Azure AD.

If it looks correct in Active Directory, then the next step is to follow the user in the sync engine. By following the user from on-premises Active Directory to Azure AD, you can see if there is a descriptive error on the object.

  1. Start the Synchronization Service Manager.
  2. Click Connectors.
  3. Select the Active Directory Connector the user is located in.
  4. Select Search Connector Space.
  5. Locate the user you are looking for.
  6. Select the lineage tab and make sure that at least one Sync Rule shows Password Sync as True. In the default configuration, the name of the Sync Rule is In from AD - User AccountEnabled.
    Lineage information about a user
  7. Then follow the user through the metaverse to the Azure AD Connector space. The connector space object should have an outbound rule with Password Sync set to True. In the default configuration, the name of the sync rule is Out to AAD - User Join.
    Connector space properties of a user
  8. To see the password sync details of the object for the past week, click Log....
    Object log details
    If the object log is empty, then Azure AD Connect has not been able to read the password hash from Active Directory. Look into the eventlog for errors.

The status column can have the following values:

Status Description
Success Password has been successfully synchronized.
FilteredByTarget Password is set to User must change password at next logon. Password has not been synchronized.
NoTargetConnection No object in the metaverse or in the Azure AD connector space.
SourceConnectorNotPresent No object found in the on-premises Active Directory connector space.
TargetNotExportedToDirectory The object in the Azure AD connector space has not yet been exported.
MigratedCheckDetailsForMoreInfo Log entry was created before build 1.0.9125.0 and is shown in its legacy state.

Troubleshoot issues where no passwords are synchronized

Start by running the script in the section Get the status of password sync settings. It gives you an overview of the password sync configuration.
PowerShell script output from password sync settings
If the feature is not enabled in Azure AD or if the sync channel status is not enabled, then run the Connect installation wizard. Select Customize synchronization options and unselect password sync. This change temporarily disables the feature. Then run the wizard again and re-enable password sync. Run the script again to verify that the configuration is correct.

If the script shows that there is no heartbeat, then run the script in Trigger a full sync of all passwords. This script can also be used for other scenarios where the configuration is correct but passwords are not synchronized.

If you installed Azure AD Connect with customized settings, make sure you have granted the account used by the AD Connector the permissions "Replicate Directory Changes" and "Replicate Directory Changes All". See accounts and permissions for all permissions needed by this account. Without those permissions, the account will not have permissions to read password hashes in Active Directory.

Then look into the application eventlog. If there is a global problem with password synchronization and the service is operational, as verified by the previous steps, there should be an error with more details.

Get the status of password sync settings

Import-Module ADSync
$connectors = Get-ADSyncConnector
$aadConnectors = $connectors | Where-Object {$_.SubType -eq "Windows Azure Active Directory (Microsoft)"}
$adConnectors = $connectors | Where-Object {$_.ConnectorTypeName -eq "AD"}
if ($aadConnectors -ne $null -and $adConnectors -ne $null)
    if ($aadConnectors.Count -eq 1)
        $features = Get-ADSyncAADCompanyFeature -ConnectorName $aadConnectors[0].Name
        Write-Host "Password sync feature enabled in your Azure AD directory: "  $features.PasswordHashSync
        foreach ($adConnector in $adConnectors)
            Write-Host "Password sync channel status BEGIN ------------------------------------------------------- "
            Get-ADSyncAADPasswordSyncConfiguration -SourceConnector $adConnector.Name
            $pingEvents =
                Get-EventLog -LogName "Application" -Source "Directory Synchronization" -InstanceId 654  -After (Get-Date).AddHours(-3) |
                    Where-Object { $_.Message.ToUpperInvariant().Contains($adConnector.Identifier.ToString("D").ToUpperInvariant()) } |
                    Sort-Object { $_.Time } -Descending
            if ($pingEvents -ne $null)
                Write-Host "Latest heart beat event (within last 3 hours). Time " $pingEvents[0].TimeWritten
                Write-Warning "No ping event found within last 3 hours."
            Write-Host "Password sync channel status END ------------------------------------------------------- "
        Write-Warning "More than one Azure AD Connectors found. Please update the script to use the appropriate Connector."
if ($aadConnectors -eq $null)
    Write-Warning "No Azure AD Connector was found."
if ($adConnectors -eq $null)
    Write-Warning "No AD DS Connector was found."

Trigger a full sync of all passwords

You can trigger a full sync of all passwords using the following script:

Import-Module adsync
$c = Get-ADSyncConnector -Name $adConnector
$p = New-Object Microsoft.IdentityManagement.PowerShell.ObjectModel.ConfigurationParameter "Microsoft.Synchronize.ForceFullPasswordSync", String, ConnectorGlobal, $null, $null, $null
$p.Value = 1
$c = Add-ADSyncConnector -Connector $c
Set-ADSyncAADPasswordSyncConfiguration -SourceConnector $adConnector -TargetConnector $aadConnector -Enable $false
Set-ADSyncAADPasswordSyncConfiguration -SourceConnector $adConnector -TargetConnector $aadConnector -Enable $true

Next steps