Article ID: 2523192 - View products that this article applies to.
When you run the Microsoft Azure Active Directory Sync tool, you notice that the user name of a user in Office 365, Azure, or Windows Intune doesn't match the user's on-premises user principal name (UPN) or alternate login ID. The UPN or alternate login ID could be the user's user name, email address, or some other attribute.
There are three possible causes of this issue:
Scenario 1: Your company domain is not yet verifiedMake sure that the domain suffix of the UPN or alternate login ID is verified in your organization. If you sync users before you verify the domain, the user name of the user is changed accordingly.
How to determine the domain suffix for a UPNOn a domain controller or on a computer on which the Windows Server Administration Toolkit is installed, follow these steps:
How to determine the domain suffix for an alternate login IDOn a domain controller or on a computer on which the Windows Server Administration Toolkit is installed, you can use Active Directory Service Interfaces Editor (ADSI Edit) to determine the domain suffix for an alternate login ID. To learn more about how to do this, see Using ADSI Edit to Edit Active Directory Attributes
Note If the domain suffix isn't a registered domain, you must either register the domain by using a domain registrar or change the domain suffix of the user to a domain that's registered. This domain suffix must be registered by using a domain registrar before you can verify the domain in your organizational account.
Scenario 2: The cloud-managed user has a licenseTo update the UPN of a cloud-managed user who was assigned a license, follow these steps:
Scenario 3: The domain suffix of the UPN or alternate login ID changed from one federated domain to another federated domainFollow the steps in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/2669550/ )Changes aren't synced by the Azure Active Directory Sync tool after you change the UPN of a user account to use a different federated domain
The Windows PowerShell commands in this article require the Azure Active Directory Module for Windows PowerShell. For more information, go to the following Microsoft website:
Manage Azure Active Directory by using Windows PowerShellFor more information about how to add and verify a domain in Office 365, go to the following Microsoft website:
Add your domain to Office 365For more information about how to update other synced attributes, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2643629/ )One or more objects don't sync when using the Azure Active Directory Sync tool
Still need help? Go to the Office 365 Community
(http://community.office365.com/)website or the Azure Active Directory Forums
Article ID: 2523192 - Last Review: July 9, 2014 - Revision: 53.0