In a significant move towards enhancing browser security and performance, Microsoft has announced the retirement of Manifest V2 browser extensions in Microsoft Edge by early 2027. This transition mandates users, enterprises, and developers to adopt the newer Manifest V3, which promises stronger security features and improved performance metrics.
Transition to Manifest V3
The announcement was made through Message Center notification MC1467356 on September 4, 2026. The company plans to initiate an enterprise-wide rollout starting January 2027, with completion anticipated by April 2027. This change will impact Microsoft Edge desktop users on Windows, macOS, and Linux across all channels, including Canary, Dev, Beta, and Stable.
Manifest files are crucial as they define an extension’s capabilities, permissions, and operational behaviors. While Manifest V2 has been widely used for its flexibility, it also poses potential security risks due to its broad permission requests and remote code loading capabilities.
Benefits of the New Extension Framework
The introduction of Manifest V3 aims to mitigate these risks by enforcing stricter permissions and preventing the execution of remotely hosted code. Microsoft emphasizes that this new framework will significantly reduce the attack surface associated with older extensions and improve performance by optimizing background task management.
During the consumer deprecation phase, users will see warnings regarding Manifest V2 extensions on the Edge Manage Extensions page and on the Microsoft Edge Add-ons store. Eventually, these extensions will be removed from search results, and new installations will be blocked, although there might be a temporary option for users to manually re-enable them.
Impact on Enterprises and Developers
For enterprise users, there will be a temporary exception allowing the continued use of Manifest V2 extensions through the ExtensionManifestV2Availability policy. However, this will be phased out as well, requiring organizations to transition to Manifest V3 entirely.
Administrators are advised to identify current Manifest V2 extensions in use and look for available Manifest V3 replacements. It is crucial to update deployment policies accordingly before the deadline. Developers are also urged to migrate both internal and commercial extensions to the new framework, with the Microsoft Partner Center no longer accepting updates for Manifest V2 extensions unless they convert to V3.
Organizations should prepare for this transition by notifying users, especially if direct replacements for legacy extensions are unavailable. Support teams should anticipate an increase in requests as older extensions cease to function.
As this major shift unfolds, Microsoft underscores the need for all migration tasks to be completed before the enterprise deprecation stage, as no policy-based exceptions will be available thereafter.
