Microsoft 365 Web Services Hit by Chrome 1 Google Compatibility

Microsoft is investigating a widespread authentication issue affecting users attempting to access Microsoft 365 web-based services through Google Chrome version 147.

The problem, first reported on April 16, 2026, has left a significant number of users unable to properly load or interact with Microsoft 365 applications in their browser.

According to Microsoft’s official service health dashboard, users running Google Chrome version 147 are experiencing failures when accessing Microsoft 365 web services.

Google Chrome 147 Compatibility Issue

The root cause appears to be tied to specific authentication configurations that are incompatible with the latest Chrome release. Microsoft confirmed the issue impacts the browser’s ability to complete authentication flows correctly, preventing users from signing in or loading web-based Microsoft 365 apps as expected.

The company stated it is actively working to identify all impacted authentication configurations and implement the necessary remediation steps.

Microsoft’s engineering team has been providing rolling updates throughout the day, with status notices issued at 1:20 PM, 3:29 PM, 4:18 PM, 5:48 PM, and most recently at 6:10 PM IST on April 16.

The disruption specifically targets users on Google Chrome version 147, which appears to have introduced a behavioral change that conflicts with Microsoft 365’s authentication infrastructure.

Services accessed through the browser, including Outlook on the web, Microsoft Teams (web client), SharePoint Online, and OneDrive, are among those potentially affected. Users on other browsers or desktop clients are not reported to be impacted.

Organizations relying heavily on browser-based Microsoft 365 workflows may face productivity disruptions, particularly in environments where Chrome is the standardized enterprise browser.

Workarounds

Microsoft has advised affected users to try the following steps while the fix is being rolled out:

• Refresh the browser page, which may restore access in some cases as Microsoft applies backend configuration changes
• Switch to an alternative browser, such as Microsoft Edge, Firefox, or Safari, as a temporary workaround
• Use Microsoft 365 desktop applications where available to avoid browser-dependent authentication flows
• IT administrators should monitor the Microsoft 365 admin center service health dashboard for real-time updates

Microsoft has not yet disclosed the specific technical change in Chrome 147 that triggered the conflict, nor has it provided a definitive estimated time to resolution. The frequency of status updates throughout April 16 suggests engineers are actively engaged and progressing toward a fix.

Users and administrators are encouraged to check the Microsoft 365 Service Health Dashboard for the latest developments as the situation continues to evolve.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.