Microsoft Edge adds native Google Account sign‑in in version 150

Microsoft Edge has rolled out native support for Google Account sign‑ins, a feature that debuted with the browser’s version 150 update for Windows and macOS. The change lets users log into Edge using the same Google credentials they use for Chrome, Gmail and other Google services, eliminating the need for a separate Microsoft account when syncing bookmarks, passwords and settings.

Core developments

Edge’s new authentication flow, first reported by Thurrott.com, integrates Google’s OAuth process directly into the browser’s sign‑in UI. When users click the profile icon, they are presented with an option to “Sign in with Google.” Selecting this launches the familiar Google login page, after which Edge securely stores the authentication token and links it to the user’s Edge profile.

The feature arrives in version 150, the same release that added a handful of under‑the‑hood performance tweaks. According to gHacks, the update is available for both Windows 10/11 and macOS Ventura and later, and it does not require any additional extensions or third‑party tools. Edge continues to support its traditional Microsoft account sign‑in, meaning users can choose whichever identity provider best fits their workflow.

Microsoft’s own documentation, referenced by TechSpot, frames the addition as a “reversal of stance” after the company previously positioned Edge as a direct competitor to Chrome. By embracing Google’s login system, Microsoft acknowledges the practical reality that many users maintain a primary Google identity across devices.

In addition to the sign‑in UI, Edge now synchronizes Google‑linked data such as saved passwords and autofill entries with its own sync engine. Neowin notes that the implementation respects Google’s security standards, using encrypted tokens and prompting for two‑factor authentication when the user’s Google account is protected.

Windows Central highlights that the move removes “the biggest roadblock for Chrome users” who previously had to create a Microsoft account merely to use Edge’s sync features. By allowing a Google account to serve the same purpose, Edge lowers the friction for users who might otherwise stay locked into Chrome.

Why it matters

Edge’s market share has hovered in the single digits for years, in part because many Windows users default to Chrome for its seamless Google integration. The new sign‑in option directly addresses that friction point, potentially expanding Edge’s appeal among the roughly 1.5 billion people who use Google accounts worldwide.

From a privacy perspective, the change also gives users more choice. Edge’s tracking‑prevention tools and built‑in Defender SmartScreen can now be paired with a Google identity, allowing privacy‑focused users to benefit from Microsoft’s security stack without abandoning the Google ecosystem.

Enterprise environments may see a shift as well. Companies that standardise on Microsoft 365 often mandate a Microsoft account for device enrolment, but many employees also maintain personal Google accounts for collaboration tools. The dual‑sign‑in capability could simplify policy enforcement by letting IT admins allow Edge with either credential type, reducing the need for separate browsers on corporate machines.

Reactions and viewpoints

Industry analysts cited by Thurrott.com view the move as a pragmatic acknowledgement that “the browser war is less about exclusive ecosystems and more about user convenience.” Some see it as a sign that Microsoft is willing to collaborate rather than compete outright with Google.

Conversely, a handful of privacy advocates expressed caution. TechSpot reported that while the integration uses encrypted tokens, it still creates a bridge between Microsoft’s telemetry collection and Google’s data‑sharing practices. The concern is that users may inadvertently expose browsing habits to two large data‑collectors, even if each company claims to keep the data separate.

Users on Reddit and other forums, referenced indirectly by Neowin, have welcomed the feature, noting that the previous requirement to maintain a Microsoft account felt “needlessly cumbersome.” Early feedback praises the smoothness of the login flow and the immediate availability of synced bookmarks across devices.

Google’s official stance was not quoted in any of the sources, but the lack of public objection suggests a tacit acceptance, perhaps because the implementation does not grant Edge any special access to Google services beyond what OAuth already permits.

What’s next

Microsoft has indicated that future Edge updates will continue to expand cross‑account functionality. The company’s roadmap, as hinted by Windows Central, includes tighter integration with Google’s password manager and possibly support for Google Workspace accounts in the enterprise tier of Edge.

Developers can expect the new sign‑in option to appear in the Edge settings panel, alongside the existing Microsoft sign‑in toggle. Microsoft’s engineering blog, though not directly cited, is expected to publish a deeper technical walkthrough in the coming weeks, detailing how token refresh and revocation are handled.

For users, the immediate step is to update Edge to version 150 via the built‑in “About Microsoft Edge” page or through the standard Windows Update channel. Once updated, the Google sign‑in button will appear the first time a profile is created, and existing profiles can be linked retroactively through the profile management UI.

Whether the feature translates into measurable market‑share gains remains to be seen. Analysts will likely track Edge’s adoption metrics over the next quarter, looking for any uptick among users who previously identified as “Chrome‑only.”