Prevent Duplicate Microsoft 365 Users After Azure AD Connect Sync
Question details
The user needs to associate recreated on-premises accounts with existing Microsoft 365 users without creating duplicate cloud accounts.

- Product
- Microsoft 365 and Microsoft Entra Connect Sync
- Device & OS
- not provided
- Scenario
- On-premises user accounts were recreated after a domain controller failure and must be synchronized with an existing Microsoft 365 tenant.
- Observed behavior
- Recreated accounts can produce duplicate Microsoft 365 users when the sync service cannot match them to existing cloud identities.
Identify the existing cloud user and corresponding recreated on-premises account for each person, including their UPN and primary SMTP address. Keep the recreated accounts out of sync scope until you have reviewed the matching plan and the configured source anchor.
Use soft matching to associate existing cloud users
Use UPN or primary SMTP address matching where the existing account is eligible for matching and the identities can be verified.
Microsoft Entra Connect Sync, formerly Azure AD Connect, can match an incoming on-premises user to an existing cloud-only user by UPN or primary SMTP address. Matching is subject to Microsoft Entra tenant settings and account restrictions.
In the Microsoft Entra admin center, open Identity > Users > All users and inspect the existing user's UPN and email addresses. Confirm that it is the intended cloud-only account.
Open Active Directory Users and Computers and compare the recreated user's UPN and primary SMTP proxy address with the cloud account. For proxy addresses, the primary SMTP address is marked with an uppercase SMTP: prefix.
Correct an eligible matching attribute only after verifying ownership and checking for conflicts. Use a verified domain for the UPN, and do not reassign an email address without confirming its impact.
After reviewing Microsoft's existing-user matching guidance, include a verified test account in the sync scope and run a synchronization cycle from the Entra Connect server. In Identity > Users > All users, confirm that the existing cloud account is now synchronized and that no duplicate was created.

Review source-anchor matching or escalate duplicates
Use this route when soft matching is unsuitable, fails, or duplicate objects already exist.
Work with Office files in WPS Office
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Office format support make it easy to move existing files, although it does not manage Microsoft 365 identities or repair Entra Connect synchronization.

Frequently Asked Questions
What is the difference between soft matching and hard matching?
Soft matching uses the UPN or primary SMTP address to find an eligible existing cloud user. Hard matching uses the on-premises source anchor and the cloud user's on-premises immutable ID.
Why might a recreated user fail to match the original cloud account?
The recreated account can have a different source-anchor value, and its UPN or primary SMTP address may not match the existing cloud user. Tenant matching settings and account protections can also prevent a match.
Which proxy address is used for soft matching?
The primary SMTP address can be used for matching. In the on-premises proxyAddresses attribute, it is identified by the uppercase SMTP: prefix; secondary addresses use lowercase smtp:.
What should I do if duplicate Microsoft 365 users already exist?
Avoid deleting either account until you understand which one holds the mailbox, licenses, and other data. Open Help & support in the Microsoft 365 admin center and ask Microsoft Support to help plan the correction.




