Microsoft Edge 150 is a more practical update than its version number suggests. The headline change is that Microsoft is beginning to let users sign in to Edge with a Google account, a move that acknowledges how many people work across Microsoft-managed Windows PCs while still living inside Gmail, Google Password Manager, Chrome bookmarks, and other Google services at home or in mixed-device environments.

For Windows users and IT teams, the update is not just about convenience. Edge 150 also changes how Workspaces behave, adds new management controls, introduces security-update alerting for administrators, and marks an important support boundary for older macOS devices. The result is a browser release that deserves a quick review before it rolls through your organization or becomes the default experience on a personal PC.

Google sign-in makes Edge less of an identity island

The most visible change in Edge 150 is support for signing in with a Google account. According to the Windows Latest report, the feature is rolling out gradually and appears in the profile menu when available. Once enabled, it can help users bring key Chrome-related data into Edge without first creating or using a Microsoft account as the main browser identity.

That matters because many users do not choose their browser in a vacuum. A company laptop may be standardized on Edge, while the same person may use Chrome on a phone, home computer, or tablet. Until now, that split often encouraged people to install Chrome immediately or run two browsers side by side. Google sign-in gives Edge a better chance of becoming the browser people actually use on managed Windows devices.

There are limits. The feature is not a complete Chrome clone inside Edge. Users should expect import and profile convenience rather than full Chrome synchronization. Items such as bookmarks, history, passwords, and settings may be brought across, but Chrome extensions, themes, experimental flags, and ongoing Chrome data sync are not the same thing as signing in to Chrome itself. In other words, treat this as an onboarding and identity improvement, not as a full replacement for every Chrome feature.

What IT administrators should review first

For administrators, the big question is policy. Edge 150 introduces a policy named NonMicrosoftAccountSignInEnabled, giving organizations a way to control whether non-Microsoft account sign-in is allowed. That is important for environments with strict identity, data-loss prevention, or browser-profile separation requirements.

Before enabling the feature broadly, IT teams should review their profile strategy before turning this on. Decide whether Google sign-in is acceptable for all users, only for certain groups, or not at all. Also consider how imported passwords and autofill data interact with existing password-manager standards. If your organization already requires Microsoft Entra ID profiles, enterprise password vaults, or managed favorites, do not assume the new sign-in option is automatically harmless.

On the other hand, the feature could reduce support friction in less restrictive environments. If users keep installing Chrome just to access familiar bookmarks or passwords, a controlled Edge profile that supports Google sign-in may be easier to manage than an unmanaged second browser.

Workspaces move to a new architecture

Edge 150 also moves Workspaces to a new V2 architecture. The practical benefit is performance and reliability: workspace data is shifting into Edge Sync rather than relying on the previous OneDrive and SharePoint-backed model.

The trade-off is collaboration. Windows Latest notes that Workspaces no longer sync across devices in the same way and become more local in nature. That may be fine for users who treat Workspaces as a personal organization tool, but it is a meaningful change for teams that used shared browser sessions as a lightweight collaboration layer.

If your users rely on Workspaces for project handoffs, testing workflows, or group research, communicate the change before the update becomes widespread. A faster local workspace is useful, but it is not the same as a collaborative workspace.

Management, security, and WebView2 changes

The enterprise side of Edge 150 includes several smaller but useful adjustments. Security Update Alerts are being added to the Edge management service in public preview, allowing administrators to choose severity thresholds and receive notifications when updates include important security fixes, including zero-day-related fixes. For teams that manage many endpoints, that can help prioritize patch communication instead of treating every browser update with the same urgency.

Microsoft is also adding a WebView2 DowngradeVersion policy. This gives administrators a temporary rollback option when a WebView2 runtime update breaks an internal application. Because WebView2 is embedded in many business apps, a controlled rollback can be valuable during incident response. It should still be treated as a temporary bridge, not a long-term patching strategy.

There are also changes for Intune MAM-protected downloads, which now land in OneDrive under a Microsoft Edge downloads path. This may improve consistency for managed data handling, although users may need guidance on where protected files are stored.

Sidebar apps are being phased out

Edge 150 continues Microsoft’s move away from sidebar apps. New sidebar apps can no longer be added, and existing pinned apps are expected to disappear as Microsoft shifts attention toward Copilot-powered experiences.

For most users, this will be a minor annoyance. For power users or service desks that pinned internal tools in the sidebar, it is worth preparing alternatives. Browser features that look convenient can still be temporary, especially when Microsoft is reorganizing Edge around AI-assisted workflows.

Compatibility notes and recommended action

There are two final compatibility points. First, Windows users may see stronger validation around “View in File Explorer,” reinforcing the security sensitivity of browser interactions with the local file system. Second, Edge 150 is the last version supporting macOS 12 Monterey. Mac users who depend on Edge should plan for macOS Ventura or newer before the next major Edge release.

The practical advice is simple: test Edge 150 with your normal profiles, password policies, Workspaces usage, and WebView2-dependent apps before pushing it everywhere. For enthusiasts, the Google sign-in option makes Edge easier to try. For IT teams, it is a useful feature only if it fits your identity and data-governance model.

Source: Windows Latest source