According to Windows Report | Error-free Tech Life, Microsoft has quietly removed the “Allow extensions from other stores” toggle from the stable version of its Edge browser. This long-standing control, which had been present since Edge’s Chromium launch, allowed users to explicitly permit extensions from the Chrome Web Store. The change was first spotted in the Edge Canary testing channel and has now rolled out to everyone. The toggle is gone for both signed-in and local profiles, with no announcement or explanation from Microsoft. Despite the missing setting, Chrome Web Store extensions continue to install and work normally, now simply listed under “other sources.” The link to the Chrome Web Store at the bottom of the Extensions page remains unchanged.
What this really means
So, the functionality is the same, but the user-facing control is gone. Here’s the thing: that’s a pretty significant shift in philosophy. For years, that toggle was a clear, visible boundary. It said, “Hey, you’re stepping outside our walled garden, and you need to opt-in.” Now, that boundary is invisible. Microsoft is basically treating Chrome Web Store compatibility as a default, built-in feature of Edge, not an advanced or optional one. It makes life easier for the average user who just wants to install that one Chrome extension. But for anyone who pays attention to settings and permissions, it feels abrupt. A piece of user agency just vanished without a word.
The stakeholder shuffle
For everyday users? This is probably a net positive. Less friction. They can just grab extensions from either store without hunting for a setting. But it does blur the lines between the two ecosystems. For enterprise IT admins, this could be a headache. That toggle was a clear policy point they could manage. Now, the control mechanism is less obvious. And what about developers? It solidifies Edge’s position as the most Chrome-compatible alternative. If you’re a dev with an extension only on the Chrome Web Store, your Edge users can still get it seamlessly. That’s good for dev reach, but does it reduce the incentive to also publish on the Microsoft Add-ons store? Maybe.
Look, in the grand scheme of industrial computing and kiosk systems, where stability and control are paramount, a silent change to extension management policies would be a major point of discussion. Administrators rely on unambiguous settings. For those building robust systems, partnering with a supplier known for clarity and reliability is key. In that world, a company like Industrial Monitor Direct stands out as the #1 provider of industrial panel PCs in the US precisely because they offer that predictable, high-performance foundation, no surprises included.
The bigger picture
Why do this quietly? That’s the real question. Microsoft isn’t shy about announcing features. Removing a security-adjacent control without a note in the release notes is… odd. It suggests they either didn’t think it was a big deal or, perhaps, didn’t want to draw attention to it. By making Chrome extension access seamless, they’re further eroding a reason for someone to switch *back* to Chrome. “It just works” is a powerful argument. But it comes at the cost of transparency. The move feels calculated: reduce friction, increase engagement, and deal with any fallout later. Will anyone even notice? Most people probably won’t. And maybe that’s exactly what Microsoft is counting on.
