Microsoft Quietly Kills the Chrome Web Store Extension Control in Edge

Since its Chromium launch, Microsoft Edge has supported extensions from the Chrome Web Store, but only after users enabled a visible control in settings called “Allow extensions from other stores.” That toggle existed for years and clearly signaled when Edge allowed extensions from outside Microsoft’s own store.

Microsoft has quietly removed that long-standing toggle in stable Edge, even though Chrome Web Store extensions continue to install and work as before.

We first spotted this change in Microsoft Edge Canary, where the toggle no longer appeared in the Extensions settings.

At the time, Chrome Web Store extensions continued to install and work normally. This showed that Microsoft was adjusting the interface rather than limiting extension support.

The same behavior is now present in the stable release of Edge.

The toggle is gone in stable Edge on both:

• Signed-in profiles
• Non-signed-in local profiles

Chrome Web Store extensions still install normally and appear under “other sources.” There is no opt-in prompt or permission switch shown during installation.

Edge now allows Chrome Web Store extensions without showing the control that previously handled that access.

The Extensions page still includes a link to the Chrome Web Store at the bottom, and that part of the experience has not changed.

Microsoft has not announced this change or mentioned it in Edge release notes.

For users who pay attention to browser settings, the change may feel abrupt. A long-standing control has disappeared without warning or explanation.

Even though extension behavior remains the same, the lack of communication stands out. Changes tied to extensions and security settings usually come with clear notice.

By removing the toggle, Microsoft now treats Chrome Web Store compatibility as a built-in part of Edge rather than an optional choice.

This makes it easier for users who rely on Chrome extensions, but it also changes how control and consent appear inside the browser. Many users may only notice the change when they look for the missing setting.

So far, Microsoft has not addressed the change.