Forum Discussion
Solved
Azure AD Connect - Dealing with incorrectly created users post-sync
We have a single domain in windows AD, not the same as our verified domain in Azure AD (through 365). If a user was not set up to use the "verified" suffix in their user principal name, Azure AD Con...
You don't need to disable the sync, simply delete the "duplicate" account. As for avoiding such issues in the future, add the "verified" suffix as additional UPN suffix on-premises and update any such accounts.
When creating the accounts, Azure AD looks at the UPN value and if its populated, it will use it to create the corresponding account in O365. If the UPN doesn't match a verified domain, it will be replaced with the default @tenant.onmicrosoft.com value. If the UPN is empty, the SamAccountName attribute will be used instead, with the default domain. Similar rules apply to SMTP addresses: https://support.microsoft.com/en-us/help/3190357/how-the-proxyaddresses-attribute-is-populated-in-azure-ad
You can also use the so-called soft-matching mechanism to make sure the on-premises object "links" correctly to an already created cloud one: http://support.microsoft.com/kb/2641663
You don't need to disable the sync, simply delete the "duplicate" account. As for avoiding such issues in the future, add the "verified" suffix as additional UPN suffix on-premises and update any such accounts.
When creating the accounts, Azure AD looks at the UPN value and if its populated, it will use it to create the corresponding account in O365. If the UPN doesn't match a verified domain, it will be replaced with the default @tenant.onmicrosoft.com value. If the UPN is empty, the SamAccountName attribute will be used instead, with the default domain. Similar rules apply to SMTP addresses: https://support.microsoft.com/en-us/help/3190357/how-the-proxyaddresses-attribute-is-populated-in-azure-ad
You can also use the so-called soft-matching mechanism to make sure the on-premises object "links" correctly to an already created cloud one: http://support.microsoft.com/kb/2641663
i need your help please i was facing a problem
that problem after i trouble shooting in azure because there are many feature are not available so the trouble shoot show me that the problem from the ad connect so i uninstall it and then reach the cloud to see the users so i found them in deleted user so i decided to restore them again and every thing worked perfectly the next day i found that the users cant login into there profiles on their PC and an automatically New profile without any data created without any permission and when i try to delete the new user it recreate itself so what is the solution because i facing a big problem in my job and this is the diagram show how the company work
VasilMichev Hey I come from the future and admins are still making the same mistakes.
I can't delete the Office 365 user because the user has a EXO mailbox.
- user1@company.com.ni(Office 365 account)
- user1@company.local (AD account) synced by mistake to user1@company.onmicrosoft.com.
Now I have two duplicated users in AAD:
Is there any way I can change the sync target (user1@company.local --> user1@company.com.ni )? I tried to change the ImmutableId but failed.
Thanks in advance.
I see this is old and somewhat unanswered. I am sure you have likely found the solution by now, but for those that have this question.
---
When you end up with duplicate user accounts, while attempting to soft-match (ie. forgetting to update the UPN, or a slight variation in the logon name.) Even after simply deleting the duplicated account, you will still be unable to get the correct existing account in the AAD to soft-match until you remove the duplicate from the deleted users section of the Office365 portal.
To do this, use the following PowerShell cmdlet remove the account from the recycle bin;
Remove-MsolUser -UserPrincipalName <Incorrectaccountname@domain.com> -RemoveFromRecycleBin
You can then perform a new AAD Export and your accounts will be soft-matched correctly.
More Guidance regarding removing deleted users:
https://practical365.com/exchange-server/permanently-remove-deleted-users-office-365/
Hope this helps.
- So after I fixed the local account to have the correct UPN suffix, it would have auto-deleted the duplicate account it created, and synced to the correct one? I guess I should have given it more time. Thanks for the comprehensive response.
No, it will not auto-delete it, as the on-premises account and the "duplicate" cloud one are now "linked". But you can delete it directly from O365 without having to disable DirSync (use Remove-MsolUser/Remove-AzureADUser).
Now under the Azuer active directory web, under users, Deleted users, select the users and Delete Permanently. Then drag the users back into the OU Initial sync from local AD and the users will be sync.
I had an azuer global admin account that created a duplicate account name1234@domain.nam and I could not get rid of it. taking the user out of the OU, sync (this will add the name1234 user to the deleted users in Azuer), then taking global admin off the user in Azuer, then sync, then delete like I listed above, then move user back to OU, then sync.
Thanks to this conversation I was able to find my way.
