Microsoft plans to end support for Manifest V2 extensions in Edge starting this month, following Google Chrome, and for enterprise users in early 2027
Context & Ripple Effects
Edge’s extension compatibility has been tied to Chromium since Microsoft replaced EdgeHTML, giving its users access to the Chrome extension ecosystem through Microsoft’s Chromium-based extension strategy. Google then began disabling the older extension framework in Chrome’s pre-release channels in 2024, creating the upstream transition Edge is now following.
The enterprise timetable separates managed Edge deployments from the consumer browser transition, but it also sets a defined end point for organizations that have retained older extensions.
First-order effects
- Edge users will lose access to extensions that remain on Manifest V2 as Microsoft begins the phaseout, while extension developers must maintain Manifest V3-compatible versions for Edge.
- Enterprise Edge administrators retain a longer migration window, through early 2027, before their managed deployments lose Manifest V2 support.
Second-order effects
- Because Edge follows Chrome’s framework direction, developers can concentrate extension compatibility work on the Chromium ecosystem rather than sustain a distinct Edge path.
- Organizations with internal or policy-dependent extensions must test replacements and deployment policies before the enterprise deadline, shifting the transition work from browser choice to extension governance.
Third-order effects
- The move reinforces Chromium’s role in setting the practical technical baseline for browser extensions: Google’s platform changes propagate to Edge on a delayed but aligned schedule.
- As browsers retire older extension frameworks in stages, enterprise browser management becomes more dependent on vendors’ migration timetables and developers’ willingness to maintain current implementations.
The trend: Chromium-based browsers are converging on a single extension framework, with enterprise exemptions serving as temporary migration buffers rather than permanent forks.