Azure AD Connect Sync Error 114 after removing AD user and restoring as cloud only

Marc Laflamme 26 Reputation points
2021-11-01T22:43:49.257+00:00

We removed two users (moved them to an un-synced OU in AD on-prem) and waited for them to show up as Deleted Users in 365 Admin page. Both accounts were restored as Cloud Only users but now we are seeing Error 114 in AD Connect Sync.

I tried following the Options found here (https://learn.microsoft.com/en-us/answers/questions/595446/other-error-on-azure-ad-connect-sync.html) but neither work because the ObjectID for both objects cannot be found.

I can see the export errors in the Synchronization Service Manager but I'm not sure how to remove them.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,389 questions
0 comments
Accepted answer
  1. Siva-kumar-selvaraj 15,546 Reputation points
    2021-11-02T09:57:25.7+00:00

    Hello @Marc Laflamme ,

    Thanks for reaching out.

    I would recommend you to use UserPrincipalName instead, if you couldn't find ObjectID of those two users to set ImmutableId as $null such as Set-MsolUser -UserPrincipalName testuser5@domain.com -ImmutableId "$null" which should fix the issue.

    This would need AzureAD MSOL module to execute these cmdlets. if not installed already then install Msol module as per this guidance also the following cmdlet would help you with list out all attributes of given user Get-MsolUser -UserPrincipalName testuser5@domain.com | fl including ObjectID.

    Essentially these manual work doesn't require and since our product team has already rolled out fix for all AzureAD tenants so if you still experience similar issue ( specific to cloud user restore scenario) even after setting ImmutableId as Null then I would recommend you to reach out to MS support who can help with isolate the issue.

    If you don't have MS support plan then I can help you with one-time free support. Hope this helps.

    ------
    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Marc Laflamme 26 Reputation points
    2021-11-02T13:33:08.43+00:00

    Thanks @sikumars-msft for the reply. I was successful with setting it to null using the UPN. I was confused because I thought I needed to make the setting on the on-prem AD object, not the cloud object. But now I realize that the ImmutableId is set on an object that exists in both on-prem and cloud and because we restored the objects to cloud only and they retained the Id, that's what was causing the issue.