Fixing Office 365 DirSync account matching issues

Published: 01 March 2016 | Written by some jerk | Print | Email | Hits: 271

Recently I had to fix some issues with DirSync. For some reason (there were some cloud users created before DirSync was enabled) there were duplicate users, because DirSync failed to match the already present cloud user and the corresponding AD (Active Directory) user. There were also accounts that failed to sync and thus failed to sync all attributes properly.

If there is already a cloud account and there is need for a synced account, you can create an AD account in DirSynced OU’s. But be sure to create the user with a full UPN matching the one in Office 365 and SMTP addresses that are present on the Cloud account. With the next sync it should match both accounts. If not, it fails matching and you end up with either duplicate accounts (one cloud user and a DirSynced user with the same name/lastname/displayname) or get an InvalidSoftMatch.

When UPN/SMTP matching failed you can merge those accounts again by setting the ImmutableID on the Office 365 account (MsolUser) which is derived from the AD user’s ObjectGuid. You can only add this attribute to Office 365 accounts. After this is set, DirSync should match the accounts correctly.

So, how did I resolve this? See below:

When there are duplicates:

Remove user from DirSync (move to OU which is not synced, will only work when OU Filtering is used. If not, disable DirSync…).
Perform DirSync.
Remove duplicate synced user (NOT cloud user):
- Remove-MSOLuser -UserPrincipalName <UPN> -RemoveFromRecycleBin
- Add ImmutableID from AD user to Cloud user
  - $guid = (get-Aduser <username>).ObjectGuid
    $immutableID = [System.Convert]::ToBase64String($guid.tobytearray())
  - Connect to AD Azure (Connect-MSOLService when AD Azure Powershell Module is installed).
  - Set-MSOLuser -UserPrincipalName <clouduserUPN> -ImmutableID $immutableID
  - It’s possible that the clouduserUPN must be changed to the <tenant>.onmicrosoft.com format. It should be changed by DirSync to correspond with the AD UPN.
  - See also http://www.joseph-streeter.com/?p=423
Place account back in correct (synced) AD OU.
Manually kick off a sync on the DirSync Server if you don’t want to wait (up to 3 hours with default settings):
- C:\Program Files\Windows Azure Directory Sync\DirSyncConfigShell.psc1
- Start-OnlineCoexistenceSync

In my case it didn’t always match the accounts and was required to perform a Full DirSync (on DirSync server):

Via MIISClient, Management Agents:
- C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell\missclient.exe
Be sure to be member of local group “FIMSyncAdmins”
Names might be different depending on DirSync version
On the Windows Azure Active Directory Connector:
- Properties>Run>Full Import Delta Sync
on the Active Directory Connector:
- Properties>Run>Full Import Full Sync

Note that a Full Sync can take a long time if you have a lot of objects. Furthermore, changes can take a while to propagate in Office 365.
It might be necessary to edit an attribute (Description, office etc. Something that is synced), and then perform a (normal) sync.

When you have an InvalidSoftMatch (SMTP Address matching doesn’t work because SMTP address already exists in Cloud):

Within the MIISClient.exe on the DirSync server, you can check for errors. In this case the account wasn’t properly matched:

Add ImmutableID from AD user to Cloud user:
- $guid = (get-Aduser <username>).ObjectGuid
- $immutableID = [System.Convert]::ToBase64String($guid.tobytearray())
- Connect to AD Azure (Connect-MSOLService when AD Azure Powershell Module is installed)
- Set-MSOLuser -UserPrincipalName <clouduserUPN> -ImmutableID $immutableID
- It’s possible that the clouduserUPN must be changed to the <tenant>.onmicrosoft.com format. It should be changed by DirSync to correspond with the AD UPN.
- See also http://www.joseph-streeter.com/?p=423
Then perform a sync as described in the previous section.

In my case these procedures resolved my issues. But as always, use this information at your own risk. Best to make sure that you don’t end up in a situation like this Winking smile