Windows Integration Errors

Fix Azure AD Connect Invalid Matching Property and ImmutableID Errors

Bushra ParveenBushra Parveen Nov 3, 2026 869 views

Question details

Azure AD Connect skips user synchronization because the on-premises objectGUID does not match the Microsoft 365 ImmutableID.

How to Fix Azure AD Connect Invalid Matching Property and ImmutableID Errors
Product
Azure AD Connect
Device & OS
not provided
Scenario
Synchronizing on-premises Active Directory users with Microsoft 365.
Observed behavior
User synchronization fails or is skipped due to conflicting ImmutableID properties, even when the user principal name (UPN) is correct.
Before you start

Ensure you have Global Administrator privileges in Microsoft 365 and domain administrator access to run the required Active Directory PowerShell modules.

Solution 1Recommended

Update the ImmutableID via PowerShell

Use PowerShell to convert the local Active Directory objectGUID to Base64 and update the Microsoft 365 user's ImmutableID to align the accounts.

When Azure AD Connect synchronizes user accounts, it relies on a strict hardware match between the on-premises AD objectGUID and the cloud-based ImmutableID. If these values misalign, synchronization will halt to prevent directory corruption.

1
Retrieve the on-premises objectGUID

Open Windows PowerShell as an Administrator on your domain controller and use the Get-ADUser cmdlet to find the local objectGUID for the affected user.

2
Convert the objectGUID to Base64

Run a PowerShell script block to convert the retrieved GUID into a Base64 string, as Azure Active Directory requires the ImmutableID to be formatted this way.

3
Connect to Microsoft 365 services

Run the Connect-MsolService command and enter your Global Administrator credentials to authenticate with your Microsoft 365 tenant.

4
Update the cloud ImmutableID

Use the Set-MsolUser cmdlet with the -UserPrincipalName and -ImmutableId parameters to apply the newly converted Base64 string to the cloud account.

5
Force a directory sync cycle

Run Start-ADSyncSyncCycle -PolicyType Delta on your Azure AD Connect server to trigger an immediate synchronization and resolve the matching error.

Update the ImmutableID via PowerShell
Verify existing account links: Before updating the ImmutableID, double-check that the Microsoft 365 cloud user is not already actively synchronized with a different on-premises Active Directory account.
Free Microsoft Office alternative

Looking for a Reliable Alternative to Microsoft 365? Try WPS Office

Managing complex Azure AD Connect synchronizations and Microsoft 365 licenses can be time-consuming. WPS Office provides a lightweight, hassle-free alternative that works seamlessly offline and online without complicated directory setups.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
  2. 2. Install the application: Run the lightweight installer and follow the on-screen prompts to complete the setup in minutes.
  3. 3. Open existing Office files: Launch WPS Office and directly open your Microsoft Office files with perfect formatting compatibility.
100% compatible with Microsoft Word, Excel, and PowerPoint formats.No complex Azure AD synchronization required for robust local document management.Free to download and use with a highly familiar user interface.Lightweight installation that runs smoothly on almost any device.
microsoft office alternative - wps office

Frequently Asked Questions

What is an ImmutableID in Azure AD?

An ImmutableID is a unique string identifier used by Azure Active Directory to link a cloud-based user account with a specific on-premises Active Directory user account. It is typically derived directly from the local objectGUID.

How do I clear an incorrect ImmutableID?

You can clear an existing ImmutableID by connecting to MSOnline via PowerShell and running the Set-MsolUser cmdlet with the -ImmutableId parameter set to "$null".

Why does the invalid matching property error occur even with a correct UPN?

Azure AD Connect prioritizes the ImmutableID (a hard match) over the User Principal Name (a soft match). If the ImmutableID is populated but does not match the incoming objectGUID, the sync will fail regardless of whether the UPN is correct.