Understanding the Microsoft 365 Authenticator Issues in Chrome and Edge

Imagine sitting down for a routine work session and suddenly being unable to sign in to Microsoft 365 because your browser—whether Chrome or Edge—presents an error blocking the authentication process. This issue has recently affected many consumer Microsoft 365 users, causing frustration and workflow disruption.

Background and Context

Microsoft 365 employs Multi-Factor Authentication (MFA) as part of its robust security protocol, typically combining your password with a confirmation via the Microsoft Authenticator app. The login process involves a token exchange that verifies your identity securely. However, an authentication loop bug has emerged where approvals sent via the Authenticator app fail to be received by Microsoft’s backend, leaving users stuck in a never-ending sign-in request.

This issue predominantly impacts individuals and small businesses using personal Microsoft 365 subscriptions, with no significant reports from enterprise environments so far.

What Triggers the Issue?

Although Microsoft has not fully disclosed the technical root cause, it appears related to recent changes in authentication protocols or browser compatibility, particularly affecting Chrome and Edge browsers. The problem may involve backend timeouts or token handling inadequacies within these browsers, leading to failed communication between the Authenticator app and Microsoft's cloud services.

Implications for Users and Organizations

  • Work Disruption: Professionals depending on timely access to Microsoft 365 apps such as Word, Excel, and Outlook experience interruptions in their productivity.
  • Security Concerns: MFA is a security cornerstone; when it glitches, users may resort to less secure authentication fallback options.
  • Reliance on Cloud Services: The incident highlights the risks inherent in cloud-first architectures where service disruptions ripple widely.

Technical Details and Workarounds

Users encountering the error message:"We have sent a sign-in request to a Microsoft app that you use to approve sign-in requests, but we have not received your approval," can try the following workarounds:

  1. Switch Browsers: Use alternative browsers such as Firefox or Safari temporarily, as the problem is currently isolated to Chrome and Edge.
  2. Alternative Authentication Methods: Microsoft offers other MFA options:
  • Password-only login (less secure but effective in a bind)
  • One-time codes via SMS or email
  • Passkeys (cryptography-based authentication if enabled)

Users should manage these options through the Microsoft account Security Info dashboard.

  1. Use Mobile Apps: Access Microsoft 365 services via official mobile apps, which generally remain unaffected by the browser-based issues.

Ongoing Fix and Outlook

Microsoft has acknowledged the problem and is actively working on a resolution, aiming to release a fix by January 23, 2025, 21:30 CET. Although specifics remain undisclosed, the swift timeline suggests the issue might be linked to recent backend or browser updates.

Broader Implications

This issue casts a spotlight on two evolving trends:

  • MFA Dependence: As MFA becomes standard, backup login methods and redundancy in authentication become critical to maintain access during outages.
  • Cloud-Native Vulnerabilities: Cloud-first approaches demand high service reliability, and downtime can cascade across industries reliant on Microsoft 365.

Conclusion and Recommendations

While Microsoft refines its service, users should adopt workarounds and maintain awareness of official Microsoft status updates. IT professionals and users alike are reminded to maintain alternative authentication methods and diversify access points to mitigate future risks.

For now, patience and browser switching appear to be the best temporary relief while awaiting Microsoft's promised patch.

References and Further Reading

These references provide additional insight into the issue, user experiences, and the evolving official responses from Microsoft.

Author note: Article based on recent authentication issue reports and forum insights as of January 2025.