October 2026 Workspaces: invite your team

The October 2026 Outlook deadline is wrong

Classic Outlook's Word rendering engine isn't retiring on any confirmed date, and here's what Microsoft actually committed to

The claim

Search for "Outlook Word rendering engine retire" and you'll find dozens of articles stating, as settled fact, that Microsoft is ending support for it in October 2026. It's repeated across email-dev blogs, PST-recovery software marketing pages, and, until we corrected it while writing this piece, this site's own Outlook and MSO rendering article.

The claim usually appears without a citation. When we traced it back, one of the earliest clean statements of it doesn't link to a Microsoft source either. From there it spread through repetition rather than verification, the way an unsourced number tends to when everyone assumes someone else already checked it.

What Microsoft actually says

Microsoft's own published roadmap describes a three-phase migration, not a retirement date:

  • Opt-in (now). Users can try the new Outlook for Windows while keeping classic Outlook installed.
  • Opt-out, starting April 2026. New Outlook becomes the default for most users, but classic Outlook stays installed and can still be reverted to.
  • Cutover, date not announced. At some future point classic Outlook stops being newly installable. Microsoft has not set this date.

The one firm commitment Microsoft has made: existing installations of classic Outlook, through both Microsoft 365 subscriptions and perpetual licensing (Office LTSC), stay supported until at least 2029. That's three years past the date circulating online, and it's a floor, not a deadline.

It also helps to be precise about what "new Outlook" is. It isn't a patch applied to classic Outlook's rendering engine. It's a separate application, built on the same WebView2 codebase as Outlook on the web, shipped and installed alongside classic Outlook.

Microsoft is changing which app new users land in by default. It is not reaching into the old app and swapping its renderer. Classic Outlook, wherever it keeps running, keeps rendering HTML exactly as it always has.

Where October 2026 probably came from

Microsoft does have a real October 2026 deadline, just not for this. Exchange Web Services (EWS) is being disabled in Exchange Online on that date, and legacy Outlook for Mac loses access to Exchange Online mailboxes on the same timeline. Both are about authentication and API access, unrelated to how classic Outlook for Windows renders HTML.

Our best read: a real Microsoft October 2026 headline about Outlook got mixed up with the separate, ongoing "new Outlook is coming" story, and the merged claim was repeated forward without anyone tracing it back to its source. Once a handful of higher-traffic blogs stated it as fact, lower-effort content mills copied it verbatim, and now it reads as consensus simply because it's everywhere.

What this means for your email code

The VML buttons, MSO conditional comments, and pixel-width table workarounds described elsewhere on this hub aren't a temporary bridge to some upcoming cutoff. They're the baseline for classic Outlook users for years to come, guaranteed through at least 2029, with no announced end after that. Build for it as a fixture of the email landscape, not a countdown you're waiting out.

Gotchas to watch for

  • The default switch is reversible. April 2026's opt-out phase changes what new users see first, not what's installed. Users and admins can revert to classic Outlook, so don't assume a recipient is on the new renderer just because the date has passed.
  • Perpetual licenses can outlast the guarantee. Office LTSC installs are typically supported for the lifetime of that license term, which can extend well past 2029 for organizations that bought in late. Enterprise rendering quirks tend to have long tails.
  • Don't design around a date that doesn't exist. Shipping a "temporary" hack on the assumption Outlook's quirks disappear soon just means you'll be maintaining that hack for years past whenever you expected to retire it.

Sources

How Postcraft handles this

You don't need to track Microsoft's roadmap to be covered. Postcraft's target=email render generates MSO-safe, VML-backed HTML automatically, today, and it'll keep doing so for as long as classic Outlook is out there. See the Outlook and MSO rendering deep-dive for the technical detail.

Try it free