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 "80041034 " error messages when a federated user tries to sign in to Office 365, Azure, or Intune


View products that this article applies to.

Problem

When a user tries to sign in to a Microsoft cloud service such as Office 365, Azure, or Microsoft Intune from a sign-in webpage whose URL starts with "https://login.microsoftonline.com/login.srf," the user receives a sign-in error message and can't sign in.�

The following is an example of an error message that the user may receive:
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:
80041034

↑ Back to the top


Solution

On a client computer that has the Azure Active Directory Module for Windows PowerShell installed, follow these steps:
  1. Click Start, point to All Programs, click Windows Azure Active Directory, right-click Windows Azure Active Directory Module for Windows PowerShell, and then click Run as administrator.
  2. Run the following commands and press Enter after each command:
    1. connect-MSOLService  
    2. Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]
      Note In this command, [CurrentUPN]�represents the user's current user principal name (UPN), and�[NewUPN] represents the user's UPN that has a domain suffix that changed to the initial onmicrosoft.com domain.

      For example, a Contoso administrator might run the following command:
      Set-MsolUserPrincipalName -UserPrincipalName user1@constoso.com -NewUserPrincipalName user1@contoso.onmicrosoft.com
  3. Exit the Azure Active Directory Module for Windows PowerShell.
  4. Open the Azure Active Directory Module for Windows PowerShell again, and then run the following commands and press Enter after each command:
    1. connect-MSOLService 
    2. Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]
      Note In this command, [CurrentUPN] represents the UPN of the user after you run the command in step 2b, and [NewUPN] is the original UPN.

↑ Back to the top


More information

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

↑ Back to the top


Keywords: KB2962537, o365a, o365m, o365e, o365, o365022013

↑ Back to the top

Article Info
Article ID : 2962537
Revision : 6
Created on : 12/12/2014
Published on : 12/12/2014
Exists online : False
Views : 632