Fix Azure AD Creating Duplicate Users with Onmicrosoft.com Names
Question details
The user needs to understand and resolve an issue where Azure Active Directory creates duplicate accounts with a specific default domain suffix during sign-in.

- Product
- Azure Active Directory (Azure AD)
- Device & OS
- not provided
- Scenario
- A user signs in with a federated domain account in an environment using Azure AD Connect with AD FS federation.
- Observed behavior
- A duplicate user account is automatically created ending in @domain.onmicrosoft.com with random numbers instead of matching the existing federated identity.
Before attempting to resolve identity conflicts, ensure you have Global Administrator credentials for your Microsoft 365 or Azure AD portal and access to the server hosting Azure AD Connect.
Review Azure AD Connect Sync and Contact Microsoft Support
Verify your synchronization settings and open a support ticket to properly merge or resolve the identity-matching conflict.
When Azure AD Connect with AD FS federation fails to accurately match an on-premises identity with an existing cloud identity, it creates a new duplicate account using the default routing domain (@domain.onmicrosoft.com) appended with random numbers. This prevents immediate data loss but signals a failure in ImmutableID or UPN synchronization that must be addressed from the backend.
Log in to the Microsoft 365 Admin Center or Azure Portal using your Global Administrator account and navigate to the Azure Active Directory section to check the Azure AD Connect health and sync status for specific object errors.
Consult the official Microsoft documentation regarding identity matching and incorrectly created Azure AD users to understand the specific cause of your duplicate User Principal Name (UPN) or ImmutableID conflict.
Navigate to the 'Help & Support' section in the Azure Portal or Microsoft 365 Admin Center and submit a new support request. Detail the duplicate account creation issue so that Microsoft technicians can investigate.
Gather and attach your Azure AD Connect synchronization logs and AD FS configuration details to the support ticket to expedite the investigation and identity correction process.

Keep Your Team Productive with WPS Office
While your IT administrators work with Microsoft Support to resolve Azure AD identity synchronization and sign-in issues, ensure your team's workflow remains uninterrupted. WPS Office is a powerful, free, and lightweight office suite that allows users to create and edit documents locally without relying on complex cloud identity authentications.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the Software: Run the downloaded installer and follow the quick on-screen instructions to complete the setup in minutes.
- 3. Edit Microsoft Formats Seamlessly: Launch WPS Office to instantly open, edit, and save your existing Word, Excel, and PowerPoint files without format shifting.

Frequently Asked Questions
Why does Azure AD use the @domain.onmicrosoft.com suffix for the duplicate user?
When a synchronization or identity-matching error occurs during federation, Azure AD cannot assign the federated custom domain to the conflicting account. As a fallback mechanism to ensure the user object is created, it assigns the tenant's default routing domain, which always ends in onmicrosoft.com.
Can I manually merge the duplicate Azure AD accounts?
No, Azure AD does not offer a native 'merge' function for user identities. The issue stems from incorrect source anchor (ImmutableID) or User Principal Name (UPN) matching between your on-premises AD and Azure AD. Fixing this usually requires correcting the AD attributes and forcing a delta sync, often with guidance from Microsoft Support.
Will these duplicate accounts impact my user's access to Microsoft 365 services?
Yes. Because the duplicate account is technically a separate identity, the user will likely log into a blank profile that lacks access to their assigned licenses, Exchange mailbox, OneDrive files, and SharePoint permissions tied to their original account.




