Forum Discussion
Synchronization errors in your directory
Seeking some assistance with below.
Long story short, at our company, when we create new users, their user names are created based on their first name and last name initials followed by a four digit number (their employee number). For example XY1234, where 1234 is the employee number.
We created a user with and it had already synched from On premise AD to Entra. Then we were advised that the employee number of the user changed. We went ahead and deleted the user previously created on premise AD and created a new user(with new employee number) which then synced to Entra.
Now we are getting a sync error indicating that the proxy address needs to be unique and it provides the duplicate values.
How can I update the value of the user account that was deleted in on Prem AD since its no longer there.
I found the error message in Synchronization Service Manager. Is this where i can fix this? If so, some guidance would be greatly appreciated.
- EricStarker
Community Manager
Hello! You've posted your question in the Tech Community Discussion space, which is intended for discussion around the Tech Community website itself, not product questions. I'm moving your question to the Microsoft Entra space - please post Microsoft Entra questions here in the future. (You can find this and other product discussion spaces in the future through the Community Hubs page.)
None of the solutions mentioned in the article were able to resolve the issue unfortunately. My issue is the proxyAddresses. Its currently in use by two user accounts. The only place i can see the old user account is in Synchronization Service Manager.
If you're absolutely certain the object no longer exists in Azure AD - including the recycle bin (aka the object is still in its soft-deleted state) then there's only two possibilities as to why it's showing in miisclient.exe:
- Exists as a new projected addition to Azure AD;
- The connector space is no longer in sync with Azure AD.
If you select the Azure AD connector under the Connectors tab, it states near the top if the operation type is "Add", and the attributes themselves will be a dead giveaway since all their change types will also be "Add".
I'm not expecting it will be an add meaning I won't go into this scenario further, but let us know if it is.
If it's the second issue - which is also quite unusual, you will need to run a "Full Import" operation on the Azure AD connector to remove any orphaned connector space objects.
Cheers,
Lain
- Yes, it has been permanently removed from Entra ID
