Edge Manifest V2: enterprise deprecation is early 2027

Microsoft is retiring Manifest V2 browser extensions in Edge, and the reason it is worth ten minutes of your attention rather than none is that the date that applies to you is probably not the date you have heard. The widely-reported 2026 timeline is the consumer one. If you manage your fleet, yours is in 2027 — and there is a documentation conflict sitting in the middle of it.

The two timelines, kept apart

From Microsoft's Edge developer blog of August 7, 2026: the consumer transition began in August 2026, rolling out through Canary, Dev and Beta channels before reaching Stable, with the intention of finishing by the end of 2026. The same post states plainly that managed devices are not affected during that rollout, and that enterprise deprecation follows in early 2027.

Microsoft's Learn timeline page, updated September 2, 2026, lines the milestones up:

So the practical read for a managed mid-market fleet is: nothing breaks for you in 2026. That is genuinely good news, and it is the opposite of the impression the consumer coverage gives.

The part that does not add up

Microsoft's Message Center notice on enterprise deprecation, MC1467356, is reported to say two things that matter: that the rollout runs from early January 2027 to late April 2027, and that the enterprise policy override is removed at that point — after which MV2 extensions stop working on all devices, managed ones included.

Now read Microsoft's own policy documentation. The Learn page for ExtensionManifestV2Availability still says no Manifest V2 timeline has been set, and it describes the EnableForForcedExtensions option as available regardless of the manifest migration state. That page and that Message Center notice cannot both be right after early 2027.

The likeliest explanation is mundane — the policy reference has not been revised since the timeline firmed up, the same lag we keep finding across Microsoft's documentation this year. But the consequence for you is not mundane at all: an engineer who checks the policy page to decide whether the override will save them will conclude that it will. Plan on losing it.

What this actually costs you

Less than it sounds, if you start with an inventory. Microsoft reports that 95% of the most-used MV2 extensions have already shipped an MV3 version, and that of the 58 MV2 extensions still seeing meaningful usage, only 3 have no MV3 equivalent at all.

That shape makes the work clear. For almost everything, migration happens because the vendor already did it and the extension updates itself. The job is finding the exceptions — and specifically, finding them among your force-installed extensions, because those are the ones that were deployed by policy for a reason and are most likely to be load-bearing for someone's workflow.

1. List your force-installed extensions from policy, and separately list what users have installed themselves. These are different risk profiles: the first is your decision, the second is your surprise.
2. Check each against whether an MV3 build exists. Most will already be on it.
3. For anything with no MV3 successor, decide now what replaces it. After enterprise deprecation there is no switch to keep it running, and a bespoke or abandoned extension is exactly the kind of thing that has no migration path.

Sources

Microsoft's Edge developer blog, Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3 (August 7, 2026), and the Learn page Timeline for migrating to Manifest V3 (updated September 2, 2026), plus the ExtensionManifestV2Availability policy reference. Message Center notice MC1467356 is cited as reported, not quoted — see the note above.

The 30-second version

Edge's Manifest V2 retirement has two timelines. Consumers are losing MV2 across 2026. Managed devices are explicitly exempt from that rollout, and enterprise deprecation is expected to begin in early 2027. Microsoft's policy page still claims no timeline exists and implies the enterprise override survives — the Message Center says the override is removed. Assume it is removed, inventory your force-installed extensions now, and find the three-in-58 that have nowhere to go.