Microsoft Edge 150 Enables Google Account Sign-In on Windows and macOS

Microsoft Edge adds native Google account sign‑in

Microsoft’s Edge browser has rolled out version 150 with built‑in support for Google account authentication on both Windows and macOS computers. The change lets users sync bookmarks, passwords and other data using their Google credentials, a feature previously exclusive to Chrome and a notable shift after Microsoft publicly resisted Google‑centric sign‑ins.

Core developments across the announcements

All five outlets reporting the update agree that Edge 150 now presents a “Sign in with Google” button on the browser’s profile picker. When selected, the user is redirected to Google’s OAuth flow, after which Edge creates a local profile linked to the Google ID. The integration works for the desktop versions of Edge on Windows 11, Windows 10 and macOS 13 Ventura, and it is available to users as soon as they update to the stable 150 channel.

According to gHacks, the feature is optional and can be turned off in the browser’s settings, preserving the existing Microsoft account sync option. TechSpot notes that the addition represents a reversal of Microsoft’s earlier policy, which had blocked third‑party sign‑ins to keep users within the Microsoft ecosystem. Thurrott.com adds that the Google sign‑in experience mirrors the one in Chrome, allowing Edge to import existing Google‑saved passwords and bookmarks after the user consents.

Windows Central emphasizes that the move removes what it calls “the biggest roadblock for Chrome users” who might consider switching to Edge but were deterred by the lack of a familiar Google login. Neowin reports that the new sign‑in flow also surfaces a consent screen that explains what data will be shared with Microsoft, aligning with the company’s broader privacy‑by‑design messaging.

Why it matters

The browser market has long been dominated by Google Chrome, which leverages seamless Google account integration to lock users into its services. By offering the same convenience, Edge hopes to lower the friction for users who are curious about Microsoft’s Chromium‑based browser but have been wary of abandoning their Google‑centric workflow.

From a strategic perspective, the feature could be read as a pragmatic acknowledgement that interoperability, rather than exclusivity, may drive broader adoption. Analysts cited by TechSpot suggest that the move may help Edge close the gap in global market share, especially among enterprise users who already run Microsoft 365 but still rely on personal Google accounts for non‑work tasks.

Privacy advocates, however, warn that the new sign‑in creates another data‑sharing pipeline between Google and Microsoft. While Microsoft says it only accesses the minimal profile information required for sync, the consent dialog highlighted by Neowin indicates that user data such as email address, profile picture and basic account metadata will be transferred to Microsoft’s servers.

For developers, the change opens the door to deeper integration of Google services within Edge extensions and Progressive Web Apps, potentially encouraging Microsoft to support more third‑party identity providers in the future.

Differing viewpoints and reactions

gHacks frames the update as a “welcome addition” that could finally make Edge a viable alternative for users who are entrenched in Google’s ecosystem. The outlet points out that the feature’s optional nature respects users who prefer to stay with Microsoft accounts.

In contrast, Windows Central cautions that the convenience may come at the cost of data sovereignty, reminding readers that Microsoft could now correlate Google usage patterns with its own telemetry data. The article quotes a privacy researcher (paraphrased) who says the partnership “blurs the line between competing ecosystems.”

TechSpot highlights the corporate angle, noting that Microsoft’s reversal may be a response to pressure from enterprise customers who demand seamless sign‑in across both Microsoft and Google services. The piece also mentions that some industry insiders view the move as a “strategic concession” designed to keep Edge relevant in a market where Chrome’s 70‑plus percent share feels insurmountable.

Finally, Neowin adopts a more neutral tone, simply reporting the technical steps required to enable the feature while reminding users to review the consent screen carefully.

What’s next for Edge and third‑party sign‑ins

Microsoft has hinted that the Google sign‑in capability is the first of several third‑party identity integrations planned for future releases. Edge’s roadmap, referenced in a developer blog (not directly cited), includes support for Apple ID and possibly Facebook login, though no official timeline has been announced.

On the mobile front, the company has not yet extended the Google sign‑in to Android or iOS versions of Edge, but gHacks reports that a beta for Android is in internal testing. If successful, the feature could unify the desktop and mobile experience, allowing users to carry the same profile across devices.

Microsoft’s broader strategy appears to focus on making Edge a “best‑of‑both‑worlds” browser: a Chromium foundation that respects user choice while still promoting Microsoft services. As Edge 150 spreads, the real test will be whether users actually adopt the Google sign‑in or continue to rely on Microsoft accounts for work‑related sync.

Regardless of the outcome, the decision marks a clear departure from Microsoft’s earlier hard‑line stance on third‑party authentication, suggesting that the company is willing to compromise on ecosystem purity in favor of market relevance.