User Account not shwoing in Azure Metaverse - Azure Sync Issues

 Issue:

One user was not syncing to Azure AD from AD.
 
Outcome:
Found that the user had been joined in the MV to another user and had to have their immutableID corrected to get the AD user matched back to their AAD object.
 
Troubleshooting:

  • User had previously been synced to AAD, so the matching AAD object still existed in AAD, but was no longer connected to the AD object for that user. The AAD object for this user had become orphaned.
  • Sync Server Manager Metaverse search showed that users's account had become synced with another user's account and the affected user's immutableID (msDS-ConsinstencyGuid) had been changed in AD to match the wrong AAD user.
  • In order to separate the user's AD object from the incorrect user in AAD, we first pulled the user out of their syncing OU, ran a sync, and then put them back into their original OU and ran another sync; this was to un-sync the user from the incorrect user in AAD, so that we could then re-sync them to the correct object in AAD.
  • Then, in order to re-match the user to the correct AAD user object, we pulled the immutableID from the AAD user object, converted it to hex, then cleared the msDS-ConsistencyGuid from the user object in AD and added the hex from the immutableID of the correct AAD Object to the msDS-ConsistencyGuid attribute of the AD user object.
  • We then ran another sync and confirmed that the user's AD object had successfully re-matched up with the same user's AAD object.

Please let us know how things progress after updating AD and discussing with your HR Team. Let us know if you have any further issues or questions and we'd be happy to help.

 

Comments

Post a Comment

Popular posts from this blog

Could not communicate with the VM agent for snapshot status.

  A Backup failure alert has been activated Description Could not communicate with the VM agent for snapshot status. Steps to resolve the issues : 1. first disable the backup of machine which has issues. 2. then flow the below steps. In Azure VM --> C:\Packages\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot found that required metadata and other files were removed. Steps Performed to resolve the issue: Rename the Folder "Microsoft.Azure.RecoveryServices.VMSnapshot" available in C:\Packages\Plugins Copy the "Microsoft.Azure.RecoveryServices.VMSnapshot" folder from working machine Take Registry backup 4.Run registry key command one by one REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgent" /v IsProviderInstalled /t REG_SZ /d False /f REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgentPersistentKeys" /v IsCommonProviderInstalled /t REG_SZ /d False /f Restart Windows Azure guest ag...
Read more

Hidden or corrupted Outlook inbox Rule

Image
  Clearing Hidden or corrupted Outlook inbox Rule 1.   Overview This document is used as a guideline to delete corrupted, hidden inbox rules from a mailbox using MFCMAPI. 2.   Procedure 1.      Export all rules from your Outlook so that you may import them back after deleting all rules via MFCMAPI.   On your Outlook client, go to “File”> “ManageRules & Alerts”.     2.       Under E-mail Rules > go to “Options” > Export Rules > “Ok”.   3.       Download the latest version of MFCMAPI from the link below   (Please make sure you download the correct release for your Outlook client e.g. 32bit or 64bit version).        https://mfcmapi.codeplex.com/ 4.       Start MFCMAPI.EXE as Administrator.     5.       Go to “Tools” > “Options”.             6. ...
Read more