MC1467356: Microsoft Edge Retires Manifest V2 Extensions and Moves to Manifest V3

📢 Official Microsoft Message Center Announcement

[What and why:]

Microsoft Edge is retiring support for Manifest V2 (MV2) browser extensions and is moving fully to Manifest V3 (MV3). MV2 will no longer run in Microsoft Edge after enterprise deprecation completes. Enterprise deprecation is currently planned for early 2027.

This change delivers customer value by pinging performance and security improvements. MV3 enforces stricter permissions, blocks remotely hosted code, and reduces the attack surface associated with legacy MV2 extensions.

To minimize disruption on the customers, better MV3 replacements are available on Edge Add-ons store.

[Rollout schedule:]

Worldwide, GCC, GCC High, DoD: We will begin rolling out on early January 2027 and expect to complete by late April 2027.

[Impact on your organization:]

Who is affected

1. All tenants and users of Microsoft Edge (consumer and enterprise) who have Manifest V2 extensions installed.
2. Enterprise administrators who deploy or allow-list MV2 extensions via Microsoft Edge policies (for example, ExtensionInstallForcelist, ExtensionInstallAllowlist, or ExtensionManifestV2Availability).
3. Extension developers who publish MV2 extensions to Microsoft Edge Add-ons through Microsoft Partner Center.
4. Managed devices are unaffected during the consumer rollout. A policy ExtensionManifestV2Availability will be provided to continue maintaining MV2 support. Managed devices are affected once enterprise deprecation begins.

Platforms / Services

1. Microsoft Edge (desktop) on Windows, macOS, and Linux — all channels: Canary, Dev, Beta, and Stable.
2. Microsoft Edge Add-ons store — MV2 extension discovery, install, and updates.
3. Microsoft Partner Center — Microsoft Edge Add-ons extension submissions and updates.
4. Microsoft Edge policies — the ExtensionManifestV2Availability policy is removed at enterprise deprecation.

What will happen

1. MV2 extensions will begin showing deprecation warnings on the Manage Extensions page (edge://extensions) and on Microsoft Edge Add-ons product detail pages. MV2 extensions will no longer appear in Add-ons search.
2. MV2 extensions will be disabled by default for consumer users; users will initially be able to re-enable them, and this option will phase out over time.
3. New installs of MV2 extensions from Microsoft Edge Add-ons will be blocked.
4. After enterprise deprecation, the ExtensionManifestV2Availability policy will be removed and MV2 extensions will stop working on all devices, including managed devices with the policy previously set.
5. Existing MV2 configurations relying on the ExtensionManifestV2Availability policy will no longer take effect after enterprise deprecation.
6. Microsoft Partner Center will stop accepting updates to MV2 extensions; updates that migrate an extension from MV2 to MV3 will still be accepted.
7. No new extensions can be published as MV2 on Microsoft Edge Add-ons (already in effect since July 2022).

[Action required / Recommendations:]

Migration steps (a replacement exists — Manifest V3)

1. Inventory MV2 extensions in your environment using Microsoft Edge management reporting or the Edge management service.
2. Identify which MV2 extensions have an MV3 version on Microsoft Edge Add-ons and plan the update through your normal deployment process.
3. For internal (line-of-business) MV2 extensions, migrate them to Manifest V3 using the Microsoft Edge migration guide and resubmit through Microsoft Partner Center.
4. Update ExtensionInstallForcelist and ExtensionInstallAllowlist entries to reference the MV3 versions of the extensions you deploy.
5. Configure ExtensionManifestV2Availability intentionally: keep MV2 available for your users during the consumer rollout only if needed, and plan to remove the dependency before enterprise deprecation.

Deadline

1. All migration off MV2 must be complete before the enterprise GA. After that date, MV2 extensions will not function in Microsoft Edge, and the ExtensionManifestV2Availability policy will be removed.

Communication guidance

1. Notify affected end users in advance, especially where an MV2 extension will not have a direct MV3 replacement.
2. Update internal documentation and knowledge base articles that reference MV2 extensions or the ExtensionManifestV2Availability policy.
3. Inform your helpdesk about the change so they can support users whose extensions are disabled or replaced, and share the MV3 alternatives being recommended.
4. Engage extension vendors (third-party and internal) to confirm their MV3 timeline and align it to your enterprise deadline.

Source: Microsoft Message Center • Analysed by MWPro