A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The message “Sorry, but we’re having trouble signing you in” means the Microsoft sign-in process is failing, even if credentials were entered correctly. In this state, the account is not considered successfully signed in to that application or site.
For Microsoft services that use modern authentication (such as Microsoft 365, Azure, or other apps fronted by Microsoft Entra ID), this error typically indicates an authentication problem on the service side rather than a problem with the local Windows sign-in or with the device’s lack of biometrics. The service may be encountering an Entra authentication error state and interrupting the sign-in flow.
In practice this means:
- The sign-in did not complete successfully for that web front end.
- The application should not treat the session as authenticated, even if a Windows session is already active.
- The issue is usually with how the relying application or its identity configuration is set up (for example, domain or federation configuration, user ID/UPN handling, or other Entra-side issues), not with the end user’s long-standing Microsoft usage or expectations.
Because this is tied to the prospective employer’s front end, the correct next step is for their IT/admin team to review the sign-in configuration and associated Microsoft Entra error details. The generic “Sorry, but we’re having trouble signing you in” message is the standard surface for these backend authentication issues.
References: