Microsoft to Retire Manifest V2 Extensions in Edge by Early 2027
Microsoft is phasing out Manifest V2 browser extensions in Edge by early 2027, mandating a transition to Manifest V3 to enhance security and performance.
Microsoft has announced a significant shift in its browser extension policy, signaling the retirement of Manifest V2 support in Microsoft Edge by early 2027. This move necessitates that all users, enterprises, and developers transition to Manifest V3, a newer framework designed to bolster browser security, improve overall performance, and mitigate risks associated with legacy extension code.
The company communicated this change via Message Center notification MC1467356, with a phased rollout planned. The enterprise transition is slated to begin in early January 2027 and conclude by late April 2027. This policy update will impact Microsoft Edge desktop users across Windows, macOS, and Linux, affecting all release channels including Canary, Dev, Beta, and Stable.
Manifest files are crucial components that define an extension's capabilities, the permissions it requires, its background processes, and its general operational behavior. Manifest V2 has been the standard for many years, offering developers considerable flexibility in accessing browser resources. However, this flexibility has also presented security challenges, particularly when extensions request broad permissions or load code from remote sources.
Manifest V3 addresses these concerns by introducing more stringent controls. It enforces tighter permission models, prohibits the execution of remotely hosted code, and generally reduces the attack surface that older Manifest V2 extensions could exploit. Furthermore, the Manifest V3 architecture modifies how extensions handle background tasks, leading to more efficient resource utilization and enhanced browser performance.
During the consumer deprecation phase, users will notice warnings on the Edge Manage Extensions page and on extension product pages within the Microsoft Edge Add-ons store for any remaining Manifest V2 extensions. Microsoft will also cease new installations from the store and remove these extensions from search results. While consumers might initially have a limited ability to manually re-enable disabled Manifest V2 extensions, this option will be progressively removed as the retirement process advances, eventually rendering these extensions non-functional.
For enterprise environments, a temporary exception will be in place during the consumer rollout. Administrators can leverage the ExtensionManifestV2Availability policy to maintain Manifest V2 support on managed endpoints if necessary. However, this policy exception will be removed once the enterprise deprecation phase commences, meaning Manifest V2 extensions will cease to function even on previously configured devices. Organizations relying on policies like ExtensionInstallForcelist and ExtensionInstallAllowlist for extension deployment must prepare for this change.
Microsoft strongly advises developers to migrate their internal and commercial extensions to Manifest V3. The Partner Center will no longer accept new submissions or updates for Manifest V2 extensions, though updates that convert an existing extension to Manifest V3 will still be processed. New Manifest V2 extension submissions were already blocked as of July 2022.
Organizations are urged to proactively inform their users about this transition, especially if critical extensions lack direct Manifest V3 replacements. Security teams and IT support should also brace for an increase in user inquiries as older extensions become disabled. All migration efforts must be completed before the enterprise deprecation deadline, as no further policy-based exceptions will be available.