When a federated user tries to sign in to a Microsoft cloud service such as Office 365, Microsoft Azure, or Microsoft Intune from a sign-in webpage whose URL starts with https://login.microsoftonline.com/login, authentication for that user is unsuccessful. The user gets 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: 80045C06
This issue can occur if the time setting in the on-premises environment doesn't match the time setting of the Microsoft Azure Active Directory (Azure AD) authentication system. Where the time difference between Active Directory Federation Services (AD FS) clients or servers and the Azure AD authentication system is more than 5 minutes, logons by federated users will fail. This may occur if one or more of the following conditions are true:
The client computer or computers aren't syncing correctly with the on-premises Active Directory.
The AD FS service components aren't syncing correctly with the on-premises Active Directory.
The on-premises Active Directory Primary Domain Controller (PDC) emulator isn't syncing to an accurate Internet time source.
The token validity period for AD FS claims is too short.
To resolve this issue, use one of the following methods:
Method 1: Set up client computers and AD FS servers to use the on-premises Active Directory PDC emulator as a Network Time Protocol (NTP) time source
Microsoft Azure cloud services, Microsoft Azure Active Directory, Microsoft Office 365, Microsoft Intune, CRM Online via Office 365 E Plans, Microsoft Azure Recovery Services, Office 365 Identity Management