Google Workspace starts nudging Firefox users toward Chrome with security warnings

On June 18, 2026, a Google Workspace administrator on a Business Plus plan reported that signing in from Firefox triggered a full-page interstitial urging them to “secure” their device and download Chrome to keep accessing their work account. The browser and OS were fully up to date, and access still functioned at the time of writing — but with no indication of how long that would last. When contacted, Google support claimed the prompt only appears for admins reaching admin.google.com, insisted it was a recommendation rather than a block, and said the behavior would not be documented publicly.

Google’s follow-up email did nothing to clarify the situation. It was generic boilerplate listing officially supported browsers and noting that Firefox lacks offline access and client-side encryption in Meet, alongside the usual advice to keep browsers updated and enable cookies and JavaScript. None of it addressed why a current Firefox release was suddenly being flagged as insecure. The author, who is the account’s own admin, ruled out the usual culprits: they don’t use Identity-Aware Proxy (which is genuinely Chrome-only for device verification), and Context-Aware Access is an enterprise tier they aren’t on.

The episode matters because it looks less like a technical requirement than a soft push toward Chrome, dressed up as a device-security measure. For teams that need to validate software across browsers — and for users who simply prefer Firefox — an undocumented, support-denied nudge that could escalate into a hard block sets an uncomfortable precedent for how a dominant platform vendor steers users onto its own browser.