Microsoft Edge Beta 150 landed on June 11, 2026, with a feature that blurs the line between browser ecosystems like never before: native support for Google account sign-in in browser profiles. The update, rolling out to Windows and macOS users on the Beta channel, means you can now log into Edge using your Gmail or Workspace credentials and sync bookmarks, passwords, history, extensions, and other settings across devices — without a Microsoft account. For enterprises, Microsoft is shipping a dedicated Group Policy to keep administrators in control of which identity providers are allowed.

The move has been rumored for months, with code snippets appearing in Edge Canary builds. Now official, it marks a strategic pivot: rather than forcing users into the Microsoft account ecosystem, Edge is opening its sync backbone to a competing identity platform. The immediate user benefit is reduced friction for the millions who live in Google’s apps but prefer Edge’s interface, efficiency, or Copilot integration. At the same time, it raises questions about data handling, privacy, and the future of browser lockdowns in managed environments.

What the Google Sign-In Actually Does in Edge

When you add a new profile in Edge Beta 150 and choose “Sign in with Google,” the browser launches a standard OAuth consent flow. After granting the requested permissions, Edge creates a local profile linked to that Google identity. The sync engine then kicks in, encrypting your data client-side before it travels to Microsoft’s sync servers. Notably, your Google account password is never shared with Microsoft — authentication uses a short-lived token, and Edge relies on open standards like OpenID Connect.

The sync scope mirrors what you’d get with a Microsoft account. That includes:

  • Favorites and reading list
  • Saved passwords (optionally stored in Edge’s built-in password manager)
  • Browsing history and open tabs
  • Extensions and their settings
  • Addresses, payment methods (if you’ve saved them in Edge)
  • Collections and tracking prevention exceptions

One key difference: Microsoft Rewards and family safety features remain tied to a Microsoft account, so logging in with Google won’t let you earn points or manage child screen time. Similarly, the Edge sidebar’s Microsoft 365 pane and price comparison tools still expect a Microsoft identity for full functionality. However, features like vertical tabs, sleeping tabs, and Copilot in the sidebar work regardless of your authentication provider.

Early testers report that the sync is fast and seamless, with the first sync completing within a minute on a stable connection. Switching between devices feels exactly like it does with a Microsoft account — a testament to Microsoft’s investment in its sync infrastructure over the past few years.

Enterprise Controls: The ‘NonMicrosoftAccountSignInEnabled’ Policy

IT administrators don’t love surprises. To address this, Edge 150 introduces a new Group Policy (and corresponding MDM setting) called NonMicrosoftAccountSignInEnabled. The name aligns with Microsoft’s typical pattern for optional policies — though the excerpt from the original announcement refers to it as “NonMicro,” which appears to be a shorthand for the full policy string.

When set to 0 (Disabled), this policy blocks all non-Microsoft account sign-ins, including Google. When set to 1 (Enabled), users can sign in with Google or any future external identity provider that Microsoft might add. If the policy is not configured, the browser defaults to the state set in Edge’s internal flags, which in Beta 150 is enabled out of the box.

The policy is available under both Computer Configuration and User Configuration in the Group Policy Editor, path: Administrative Templates / Microsoft Edge / Identity and sign-in. Microsoft has also updated its Intune settings catalog to pull in the new CSP (Configuration Service Provider) node, so cloud-managed devices can toggle it remotely.

Several admins on early adopter forums have already begun testing. The general sentiment is positive — organizations with BYOD policies or mixed cloud ecosystems see value in letting employees use their existing Google accounts. However, concerns about data residency and compliance linger, particularly in regulated industries. Microsoft’s documentation clarifies that sync data is encrypted in transit and at rest, and that the data is stored in Microsoft’s own data centers, subject to the same privacy protections as Microsoft account sync. This distinction is crucial: Google is used only for identity verification, not as a data host.

How to Get Started

If you’re already on the Edge Beta channel, simply update to version 150.0.xxxx. Then:

  1. Click your profile icon in the top-right corner.
  2. Select “Add profile” or “Sign in.”
  3. Choose “Sign in with Google” from the identity provider list.
  4. Complete the OAuth flow in the pop-up window.
  5. Enable sync when prompted.

For new Edge installations on Windows or macOS, the out-of-box experience (OOBE) will also surface the Google sign-in option on the welcome screen. Existing users who previously set up a local profile can convert it by going to edge://settings/profiles, clicking “Sign in,” and selecting Google. The browser then migrates local data to the new synced profile — though some testers advise backing up bookmarks beforehand, just in case.

The feature is currently exclusive to Beta 150 and above. If the rollout follows the usual Chromium cadence, it should reach the Stable channel within 4–6 weeks, likely in late July or early August 2026. It’s not yet available on Linux, but the platform’s shared codebase makes a future port probable.

What This Means for the Browser Landscape

Microsoft’s decision to embrace Google accounts is about more than convenience. It’s a direct challenge to Chrome’s sticky ecosystem. For years, Chrome’s primary moat has been its seamless synchronization across devices via Gmail login. By offering the same zero-friction setup, Edge removes a major reason to switch browsers — or to switch back.

Edge has been gaining market share steadily since the Chromium rebuild, often praised for lower memory consumption and tighter Windows integration. Yet many Chrome defectors still kept Chrome installed solely for cross-device sync with their Google accounts. With this update, Edge essentially says: you don’t need Chrome for that anymore.

It also reshapes the enterprise conversation. Companies that standardized on Google Workspace but run Windows can now deploy Edge and let employees sign in with their Workspace credentials, all while benefiting from the same Group Policy management they’d use for Microsoft Edge. This reduces the appeal of Chrome’s enterprise management and could sway procurement decisions.

However, Microsoft is careful not to alienate its own ecosystem. Microsoft account sign-in remains the default and is the only path to unlock the full suite of Microsoft 365 integrations. The coexistence hints at a “better together” strategy: use your Google account for sync, but stay signed into Microsoft 365 on the web for productivity.

Privacy and Security Considerations

Whenever a browser handles credentials from a third-party, the privacy question surfaces. How much does Google see? What data does Microsoft collect? Here’s what we know from Microsoft’s documentation and the browser’s source code:

  • Authentication tokens: Microsoft Edge receives a short-lived OAuth token from Google. It cannot access your Google password or two-factor authentication secrets.
  • Sync data: Bookmarks, passwords, and other sync items are encrypted client-side using a sync passphrase (if set) or the device’s credentials. This data is stored on Microsoft servers. Google has no visibility into it, as the token only grants access to basic profile information (email, name, avatar) for display purposes.
  • Audit logs: Enterprise administrators can view sign-in events in both Google Workspace admin console (to see that the “Microsoft Edge” OAuth app was authorized) and in Microsoft compliance portals (to see sign-in attempts via Edge).
  • Data residency: As with Microsoft account sync, data is stored in Microsoft Azure data centers. Organizations with strict sovereignty requirements should verify that the default data location matches their compliance needs.

A potential risk: if a user’s Google account is compromised, and the attacker authorizes the Edge OAuth app, they could potentially request a sync token and access the user’s synced Edge data — but only if they also have access to the device or can install Edge and initiate sync. This attack surface is comparable to signing into any OAuth-enabled third-party service. Users are advised to enable multi-factor authentication on their Google accounts.

Microsoft has published a detailed whitepaper on Edge sync encryption, which now includes a section specific to third-party identity providers. The key takeaway: your Google credentials are not used as encryption material; they merely grant a claim to retrieve your sync sessions.

Community Reaction and Early Feedback

Although the official announcement thread on WindowsForum is sparse, chatter across other enthusiast communities has been largely positive. The phrase “finally” appears frequently. Many users see it as a pragmatic move that acknowledges reality: not everyone wants a Microsoft account, especially on shared or work devices.

Some long-time Edge users expressed initial confusion about having two identity layers (Microsoft plus Google) inside the same browser, but the profile manager clearly separates them. A few power users are already exploring workarounds to use the Google sign-in as the default while keeping Microsoft account features accessible via a secondary profile.

On the enterprise side, administrators are cautiously optimistic. The Group Policy is welcomed, but there are calls for more granular controls — for example, allowing Google sign-in only for certain OUs or excluding it for specific security groups. Microsoft’s documentation suggests that the policy is a simple on/off toggle at this time, but feedback could shape future iterations.

Critics point out that Edge still lacks built-in support for other identity providers like Apple ID or GitHub, which some would prefer. The underlying infrastructure appears to be extensible, as the “Sign in with” dialog in Beta 150 includes a placeholder list that could accommodate additional providers. That’s speculation for now, but a compelling roadmap indicator.

Looking Ahead: The Road to Stable and Beyond

The Google sign-in feature is the latest in a series of identity expansions for Edge. Last year, the browser added support for Microsoft Entra ID (formerly Azure AD) as a first-class identity for enterprise profiles. Today’s Google account support opens the door to a truly multi-identity browser, something no other major browser offers out of the box.

What might come next? Here are some educated guesses based on commit history and public statements:
- Apple ID and Facebook Login: The OAuth framework in Edge can accommodate any OpenID Connect provider. Adding Apple or Facebook would be mostly a UI and policy undertaking.
- Google Drive integration: If Edge can authenticate with Google, there’s potential for deeper Workspace connections — think direct saving to Google Docs from the browser’s print dialog, or Drive-powered file sync for Edge profiles.
- Unified sync profile: A long-term vision might let you merge data from multiple accounts, though the privacy and technical hurdles are significant.

For now, the focus is on polishing the Google sign-in experience and rolling it out to Stable. Beta testers should keep an eye on edge://sync-internals to monitor sync status and file bugs via the Edge Insider feedback tool. Microsoft has set up a dedicated feedback category for “Google account sync,” indicating they’re actively monitoring reports.

Should You Switch Your Profile to Google Login?

If you’re already happy with your Microsoft account, there’s little reason to change. The core Edge experience doesn’t differ based on identity. The move is designed for users who either don’t have a Microsoft account, prefer to keep their work and personal lives separate, or simply trust Google’s authentication more.

For those who do switch, be aware that some Edge features will silently degrade. Microsoft Rewards won’t accumulate, the digital legacy feature won’t be available, and certain password monitor alerts tied to Microsoft Defender may not fire. These are minor trade-offs for many.

One practical tip: if you rely on Edge’s built-in password manager and sync, you can export your existing passwords before switching profiles, then import them into the new Google-linked profile. That ensures no loss of credentials.

As with any beta feature, there’s a small chance of data loss or sync desynchronization. The official recommendation is to wait for Stable release for production workflows. But for early adopters and the tech-curious, Beta 150 is stable enough to explore.

Final Thoughts

Microsoft Edge Beta 150’s Google sign-in is more than a convenience update — it’s a declaration that the browser wars have entered a new era of cooperation. By decoupling the sync engine from its own identity platform, Microsoft is betting that a superior browsing experience will keep users loyal, even when they bring their own accounts. The chess move puts pressure on Google’s Chrome, which shows no sign of reciprocating with native Microsoft account support, and on the broader industry to rethink how browsers handle identity.

For IT pros, the new policy controls ensure that flexibility doesn’t come at the cost of security. For everyday users, it’s one less barrier to trying — or sticking with — Edge. As the feature matures and expands to more platforms and providers, it could reshape expectations around browser sync for years to come.

Download the update from the Microsoft Edge Insider website, and if you encounter any issues, use the in-app feedback tool to help Microsoft smooth out the rough edges before the Stable launch.