New Outlook has stopped connecting to google workspace gmail

Hi AH

Since Classic Outlook on another PC still connects successfully and you've already tried repairing, resetting, removing credentials, and changing the default browser, this looks less like a Gmail configuration issue and more like a problem with the New Outlook OAuth sign-in flow on this specific device.

A few additional things worth trying:

1. Confirm you can sign into the same Google Workspace account directly in a browser and that there are no pending Google security prompts or consent requests.
2. Test with an InPrivate/Incognito browser session and temporarily sign out of other Google accounts before adding the account again.
3. Temporarily disable any ad blockers, privacy extensions, security software, VPNs, or web filtering that could prevent the authentication handoff from Outlook to the browser. Similar authentication issues have been linked to blocked cookies or browser components.
4. Create a new Windows user profile and test New Outlook there. If it works, the issue is likely related to the current profile's cached authentication state.
5. If the problem started abruptly yesterday with no configuration changes and continues after the above tests, it may be a service-side or application regression affecting Google Workspace authentication in New Outlook. At that point, I would recommend using Classic Outlook as a temporary workaround and reporting it through Help > Feedback in New Outlook so the Outlook team can investigate.

As this is a public forum, we don't have access to Outlook or Google server-side logs, but the fact that the browser sign-in page never launches suggests the authentication handoff is failing before Google can complete the authorization process.

Hope this helps. Let us know whether the browser page opens when testing from a new Windows profile or an InPrivate session.

This issue occurs because the WebView2 runtime (which New Outlook uses for web rendering) fails to pass the OAuth authentication request to your default browser, or an old session token in Google is blocking the pop-up trigger.

Here are the direct, proven steps to fix this:

Step 1: Clear the New Outlook & WebView2 App Data

Resetting the local cache clears stuck authentication loops without deleting your mailbox on the server:

• Close New Outlook completely.
• Press Windows Key + R, paste the following path, and press Enter: %localappdata%\Microsoft\Olk
• Delete all files and folders inside this Olk folder.
• Restart your computer, reopen New Outlook, and try adding your Workspace account again.

Step 2: Revoke Microsoft Permissions in Google Workspace

A corrupted token on Google's side can silently freeze the login handoff:

• Open your browser and go to: myaccount.google.com/connections
• Under Third-party apps & services, locate Microsoft apps & services (or Microsoft Outlook).
• Click it and select Delete all connections that you have with Microsoft apps & services.
• Go back to New Outlook and add your Gmail account. This forces Google to generate a clean login prompt.

Step 3: Check Default Protocol Handlers

Even if Edge or Chrome is set as the default browser, link protocols can get detached:

• Go to Settings > Apps > Default apps.
• Select your default browser (Chrome or Edge).
• Ensure both HTTP and HTTPS link types are assigned to that browser.
• Temporarily disable any aggressive pop-up blocker, ad-blocker extensions, or third-party web shields (e.g., Bitdefender, Kaspersky) while adding the account.

Quick Workaround:

If you need immediate access, toggle off the "New Outlook" switch in the top-right corner to return to Classic Outlook, which uses standard Windows MAPI/REST protocols and does not rely on the WebView2 browser handoff.

Kanul - thanks for your detailed response.

I've also tried each of the steps you provided - but also no success.

See me earlier comments to Alex - authentication also fails from a different user profile and PC.

Would I be able to log a case with Microsoft? Not sure how to do this.