Article ID: 2844931 - View products that this article applies to.
Not sure which release of Office 365 you're using? Go to the following Microsoft website:
Am I using Office 365 after the service upgrade?
When a user tries to sign in to Office 365, the user receives the following error message:
Sorry, that didn't work
This doesn't look like a valid user ID. Make sure you typed the user ID assigned to you by your organization. It usually looks like email@example.com or firstname.lastname@example.org.
This issue occurs if the user principal name (UPN) of the user in the on-premises Active Directory environment and the user's UPN in Windows Azure Active Directory (Windows Azure AD) don't match. For example, the issue occurs if the on-premises UPN is email@example.com and the Windows Azure AD UPN is firstname.lastname@example.org.
This situation can occur if the user's UPN changed but directory synchronization didn't yet occur to sync the change.
To resolve this issue, make sure that the on-premises UPN suffix is a verified domain, and then either wait until the next time that directory synchronization runs or force directory synchronization.
For more information about how to troubleshoot UPN suffixes, go to the following Microsoft Knowledge Base article:
2669550For more information about how to force directory synchronization, go to the following Microsoft website:
(http://support.microsoft.com/kb/2669550/ )Changes aren't synced to Windows Azure AD after you change the UPN of an on-premises user account to use a different SSO-enabled domain suffix
Force directory synchronization
Still need help? Go to the Office 365 Community
Article ID: 2844931 - Last Review: October 28, 2013 - Revision: 7.0