Forum Discussion

rahul2275's avatar
rahul2275
Copper Contributor
Mar 25, 2020

Hard Match when Source Anchor Attribute = sAMAccountName got changed in AD

Hello,

 

One of my client has configured sAMAccountName as a source anchor attribute in Azure AD Connect.

 

Unfortunately an user was created with wrong sAMAccountName and now we have changed the sAMAccountName which causes the user not getting synced with AD.

 

In order to perform the hard match could you please let me know what steps I have to follow where source anchor attribute is set to sAMAccountName.

 

Thank you,

Rahul.

Azure Active Directory (AAD)
  • Moe_Kinani's avatar
    Moe_Kinani
    Bronze Contributor
    Mar 25, 2020

    Hi rahul2275,

     

    1. Check PrincipleName, Mail, ProxyAddress and sAMAccount in attribute editor (AD) for that user.

     

    2. Run the CMDLET below DC PowerShell/ Change the path

    ldifde -f C:\Users\username\Desktop\export.txt -r "(Userprincipalname=*)" -l "objectGuid, userPrincipalName,sAMAcocountName"

     

    3. Get the Object Guid for the target user from exported file.

    Run the PS in ADConnect server as Admin

    Connect-MSOLService

    Run the CMDLET below:

    Set-MsolUser -UserPrincipalName username -ImmutableId ObjectGUID_VALUE_From_Step2

     

    4. Force Initial

    Sync.Start-ADSyncSyncCycle -PolicyType Initial

     

    Hope this helps!

    Moe

     

     

    • rahul2275's avatar
      rahul2275
      Copper Contributor
      Jul 01, 2020
      Source Anchor attribute is samaccountname not ObjectGUID...

Resources