Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"Sorry, but we're having trouble signing you in" and "80048163" error when a federated user tries to sign in to Office 365, Windows Azure, or Windows Intune


View products that this article applies to.

Problem

When a federated user tries to sign in to a Microsoft cloud service such as Office 365, Windows Azure, or Windows Intune from a sign-in webpage whose URL starts with https://login.microsoftonline.com/login, authentication for that user isn't successful. Instead, the user receives the following error message:
Sorry, but we're having trouble signing you in

Please try again in a few minutes. If this doesn't work, you might want to contact your admin and report the following error:
80048163

This issue may occur if the following steps were performed:
  1. The on-premises user object is first provisioned by using Unicode characters that aren't supported by Windows Azure Active Directory (Windows Azure AD).
  2. Directory synchronization is then run to create a user ID that has the same characters.

↑ Back to the top


Solution

To resolve this issue, make sure that the user's user principal name (UPN) contains only supported characters. Sign-in fails if the UPN contains characters that aren't supported.

↑ Back to the top


More information

Microsoft cloud services supports the following characters in the UPN:
  • Alphanumeric characters (uppercase and lowercase)
  • Period (.) as long as it does not appear directly before the at sign (@)
  • Hyphen (-)
  • Underscore (_)
For example, the following UPN is supported:
aA13.b@contoso.com
However, the following UPN isn't supported:
aA13.b.@contoso.com

↑ Back to the top


References

Still need help? Go to the Office 365 Community website or the Windows Azure Active Directory Forums website.

↑ Back to the top


Keywords: o365e, o365022013, o365062011, o365, o365m, pre-upgrade, after, upgrade, o365a, KB2757747

↑ Back to the top

Article Info
Article ID : 2757747
Revision : 11
Created on : 11/13/2013
Published on : 11/13/2013
Exists online : False
Views : 576