KitNelo · All tools · Blog
Browsers & softwareTech news

Edge 154 Adds Google Sign-in: Check Your Browser Profile First

Microsoft added Google account sign-in in the September 24, 2026 main Stable release of Edge 154. For readers moving between browsers or personal and work accounts, the useful question is how to inspect profiles before changing their routine. This article was published on October 4; the September feature is not presented as a launch today.

KitNeloPublished Event date 4 min read
A laptop, paper notebook and mug on a desk, illustrating browser account management rather than the Edge interface
Illustrative photo: Daniil Komov · Unsplash License

Quick answer

Microsoft confirms the Google sign-in option through the profile menu and sign-in screen on Windows and macOS, with administrator control. Check the version and management status, then try a separate profile. Choosing a Google identity does not establish that your old browser data was imported or that every website is signed in.

What the release establishes

The Microsoft Edge Stable release notes list Google sign-in under version 154.0.4258.37, dated September 24, 2026, for Windows and macOS. This article focuses on that account entry rather than combining changes from several versions on the same page.

The administrator setting is NonMicrosoftAccountSignInEnabled. Managed school or company environments therefore need an additional check. Do not infer mobile support, website login state or your own data contents from this desktop announcement.

Inspect profile identity and website identity separately

Editorial advice: distinguish the browser profile you are using, the identity shown for that profile and the account shown by each website. Checking all three helps you notice unintended mixing of personal and work contexts before editing or submitting anything.

Suppose you create a personal test profile and then open a work application. Confirm the account and access scope shown by the application; the browser avatar is not evidence of that website’s identity. Likewise, a new sign-in option does not demonstrate that bookmarks, extensions or history have already moved from the old browser.

Prepare a reversible trial

The earlier Firefox update checks for work and study also use real tasks for acceptance. Apply that approach here to identities and profiles, without treating it as a browser performance comparison.

  • Record the operating system, Edge version, profile name and whether the device is managed.
  • Choose the purpose: testing the sign-in entry or migrating selected data. A migration needs its own backup and reconciliation steps.
  • Keep the existing working environment and start with a separate test profile. Avoid adding personal material to a shared device.
  • Choose a non-sensitive test website and a short bookmark checklist to inspect the actual state.

Suggested steps for trying the entry

  1. 1Open Edge’s About page and record the version after any required update steps. The Chrome update-verification guide explains the distinction between initiating and completing an update; use Edge’s own menus here.
  2. 2Open the profile menu and confirm that you are operating in the intended test profile. If the Google option appears, follow the current interface. If it is absent, check version and management status first.
  3. 3Inspect the identity in the profile menu, then open the test and work websites separately. Check each website’s own account and access scope.
  4. 4If you deliberately migrated data, compare bookmarks, common pages and required extensions against your checklist. If you did not import anything, missing old data does not by itself mean sign-in failed.
  5. 5Return to the original profile and confirm your usual tasks still work before deciding to adopt the new profile.

Record observable results

A useful result states which profile is signed in, which identities the websites show and which data was or was not migrated. A note saying only 'sign-in successful' can leave the actual scope unclear.

If a website shows an unexpected account, pause editing or submission there and correct the identity first. If a managed device blocks the entry, record the version and management message for the administrator. Do not change organizational policy just to force a trial.

What remains environment-specific

The release notes establish the desktop entry and its system scope. They do not verify all extensions, school single sign-on systems or enterprise websites for you. This article has not performed your account migration and does not promise individual synchronization items, regional access or mobile availability.

The cover is an illustrative desk photograph, not an Edge screenshot or launch event. The workflow above is editorial advice. Use current official records and your actual settings when product behavior changes.

Common questions

Was this launched on October 4?

No. This article covers the account feature in Microsoft’s September 24 Edge 154 main Stable release and was prepared on October 4.

Why is the option missing on a company computer?

Check version and whether the device is managed. Administrator policy may affect the entry; a personal device does not establish behavior everywhere.

Does Google sign-in import everything from Chrome?

Do not infer that. Profile identity, data migration and website sign-in need separate acceptance. Record only the data you actually imported and reconciled.

Further reading & sources

Related articles