New Outlook vs Classic Outlook on Windows: What You Gain and Lose

The short answer is that classic Outlook still wins the workflows that made Outlook the standard Windows email client — add-ins, PST files, deep offline, mail-folder delegation, and every macro or add-in that ships as a COM binary. New Outlook wins the workflows that have been quietly moving to the web for a decade — anything cross-device, anything that benefits from being the same experience on desktop, browser, and phone, anything a modern web add-in can do. That trade is the entire comparison, and it is why so much depends on the shape of your specific day.

The one fact that predicts almost everything below is architectural. Classic Outlook is a Win32 desktop application with three decades of accumulated capability, loading add-in code into its own process and keeping a local data file for your mailbox. New Outlook is the Outlook on the web experience running inside a thin native Windows shell — WebView2 plus a Native Windows Integration Component that lets the web experience touch local resources like notifications and the default-mail handler. Once you accept that framing, the missing features stop looking arbitrary. Anything that needed code running on your PC is gone. Anything that needed a file on your disk is partial. Anything the mailbox service already knew how to do is present.

You are also not choosing under a deadline. Microsoft's own message centre post MC949965 moved enterprise opt-out from April 2026 to 1 March 2027, and classic Outlook is supported through the perpetual and subscription licensing streams until at least 2029. The "April 2026 hard deadline" you keep seeing on aggregator sites is misreporting — a genuine plan that Microsoft revised, then never propagated to Learn because MC posts are tenant-scoped. Verify the current cutover date in your own Microsoft 365 admin centre; the message centre is the source of truth, not third-party summaries.

At a glance: new Outlook vs classic Outlook on Windows#

This table is a snapshot of the dimensions readers actually decide on, sourced from Microsoft's own feature comparison matrix and Learn architecture pages. Where a row says "partial," that is Microsoft's own word — the capability exists in some form but is meaningfully reduced from classic, and the specific gap is described further down.

Where classic Outlook wins outright#

Classic Outlook wins the workflows that made it the Windows email standard in the first place — the ones stitched into other software through code that runs inside its process. These are not features Microsoft forgot to port. They are features whose architecture is fundamentally incompatible with a WebView2 client, and Microsoft has been clear that the web add-in surface is the replacement plan, not a temporary detour.

COM / VSTO add-ins, VBA macros and custom forms#

This is the sharpest gap and the one nobody ranks honestly for. Classic Outlook loads COM and VSTO add-ins as native code inside its own process, which is how Salesforce Lightning for Outlook, DocuSign for Outlook, Dragon dictation add-ins, third-party mail-merge tools, in-house VSTO deployments, and every VBA macro your predecessor wrote in 2011 get to reach into a mail item and change it. New Outlook cannot host any of that. Web add-ins are the sanctioned replacement path and vendors are gradually shipping them, but the version you have today is often less capable than the COM one, or does not exist at all.

If your organisation depends on any COM or VSTO integration you did not write yourself, the honest question is not "do the vendors support new Outlook yet?" but "do their web add-ins do the specific things your users depend on?" Those are different questions. A vendor can truthfully say they support new Outlook while shipping a web add-in that only covers a fraction of the COM one's surface. Test the exact user actions before you decide, not the marketing page.

VBA macros and custom Outlook forms are gone with no replacement. If a team has built its own workflow with a UserForm and a VBA script, that stack does not move to new Outlook, and the migration options are Power Automate for the workflow half, a full web add-in project for the UI half, or staying on classic Outlook until you can retire the process. There is no "convert the VBA" button and there is not going to be one.

PST files, full offline access and client-only rules#

Classic Outlook opens, imports, exports and lives in PST files. Users on new Outlook can import a PST once, but they cannot mount a PST as an ongoing store, drag between the mailbox and a PST at will, or use a PST as an archive the way a paralegal or an e-discovery workflow does today. If your annual routine involves attaching a PST for a matter or a compliance hold, classic is the only build that does that natively.

Offline is the same story with different words. Classic Outlook keeps a complete OST cache of your mailbox on disk and can operate for days with no connection at all — every folder, every attachment, every search. New Outlook is partial-offline by design. You can read cached recent mail and draft replies, but this is not a full offline archive and it does not pretend to be. On a long flight or in an offline field environment, classic still wins by a wide margin.

Rules split into two categories, and one of them only exists in classic. Server-side rules — the kind Exchange runs before mail reaches the client — work in both, and new Outlook is the better place to author them because the UI is the same as the web. Client-only rules, which run on your PC and can do things like play a specific sound or run a script, are classic-only, and there is no equivalent surface in new Outlook. Rules import and export via .rwz files is also classic-only; new Outlook rules live server-side and move with the mailbox, which is a fair trade for people whose rules were living in a fragile .rwz backup, but is a real workflow loss for admins used to shipping a rules bundle to a new PC.

Mail-folder delegation and voting buttons#

Delegation is half-migrated and this is the enterprise blocker most rollouts hit at week two. Calendar delegation already works in new Outlook — you can grant a delegate access to your calendar from the new settings surface and it behaves the same. Mail-folder delegation is different: to assign a delegate permissions on your mail folders, you still have to open classic Outlook and do it there. New Outlook does not expose the assignment surface, which invalidates almost every internal how-to guide written in the last decade. If you run an executive assistant model where the assistant needs delegate rights on the executive's inbox, you cannot fully leave classic yet.

Voting buttons — the classic "reply with Yes / No / Maybe" survey attached to a mail message — are not supported in new Outlook and have no announced replacement. Teams that use Voting Buttons for internal polls have to send the poll from classic, or move the poll to Microsoft Forms and lose the inline experience. It is a small thing, but if your organisation runs on it, it is a real blocker.

Quick Steps, Search Folders and network-share attachments#

Quick Steps and Search Folders are both present in new Outlook but with a smaller feature surface than classic. Quick Steps in new Outlook covers the basic move / mark / reply combinations; the full library of custom actions and the ability to chain steps is thinner than what heavy classic users have built up over years. Search Folders in new Outlook exist but with tighter creation and scope limits — the specific advanced search-folder queries you have saved may not port cleanly.

Attaching files from a network share via a UNC path — the \\server\share pattern — works in classic and does not in new Outlook, which routes attachments through cloud storage instead. This matters in workplaces that keep documents on internal file shares as a policy, because the new Outlook workflow forces those documents through OneDrive or SharePoint first, and that is a governance change disguised as a UX one. Confirm your compliance team is comfortable with the routing before rollout.

Where new Outlook wins outright#

There is one dimension where new Outlook is genuinely better than classic, and it is worth conceding by name rather than hedging. New Outlook has built harder on modern web architecture than classic ever will, and that pays off in three specific ways that any honest comparison has to acknowledge.

First, design consistency. New Outlook is the same experience on Windows, on the web at outlook.office.com, on iOS and on Android. If your users move between a laptop and a phone throughout the day — most people do — the muscle memory transfers cleanly. Classic Outlook on Windows and Outlook on the web have always been two different apps sharing a mailbox, with different keyboard shortcuts, different rule surfaces, and different settings layouts. The unification is a real quality-of-life improvement for a hybrid workforce.

Second, shipping pace. Microsoft ships new Outlook feature updates monthly through the same pipeline as Outlook on the web. Classic updates arrive on the Microsoft 365 Apps channel your admin selected, which for most enterprises is Monthly Enterprise Channel or Semi-Annual Enterprise Channel — quarterly to twice-yearly. If your organisation values being on the current feature set, new Outlook gets you there sooner, and the Copilot integrations Microsoft is investing in land there first.

Third, the web add-in surface itself. Web add-ins are the strategic direction, they run in both new Outlook and Outlook on the web, they do not require redistributing an MSI, and IT can pin them centrally through the Microsoft 365 admin centre without touching endpoint software. For a new integration built today, a web add-in is the better foundation even if you are still on classic — because the same add-in will run in whatever comes after classic without a rewrite.

There is also a genuine gain on multi-account UX that is worth naming without pretending the trade is one-way. In new Outlook you can add third-party mailboxes — Gmail, Yahoo, IMAP — and see them in the same client as your Microsoft 365 mailbox, with a single unified inbox surface across all of them. In classic, adding a Gmail account works but the experience is bolted-on. The catch is where the mail flows: new Outlook synchronises third-party accounts through Microsoft's cloud, which is a real data-residency and privacy change some organisations cannot accept. If your compliance posture says third-party mail is not allowed to touch Microsoft's servers on the way to the client, that closes the door on new Outlook for that scenario entirely — the multi-account convenience comes with a routing consequence you have to sign off on.

Pricing: same licence, same price#

There is no separate SKU for new Outlook or classic Outlook. Both builds are included with the same Microsoft 365 subscriptions and the same perpetual Office licences that already entitle you to Outlook, and switching between them costs nothing on the licensing side. That is worth stating plainly because a lot of comparison content on this topic frames the choice as if one is a paid upgrade — it is not.

What actually costs money is the migration, and that cost is workflow-shaped rather than seat-shaped. Rewriting a VSTO add-in as a web add-in is a real project. Replacing VBA macros with Power Automate flows is real work. Retraining an assistant team on where mail-folder delegation is now assigned takes time. If you are budgeting for a new Outlook rollout, the line items are people-hours and vendor-side rework, not licensing.

Microsoft 365 pricing for the underlying subscriptions changes periodically — Microsoft raised Business plans in 2024 and layered Copilot on top in 2025 — and any current price we printed here would age badly and misinform the next reader. Check the live Microsoft 365 plan pages for what your specific licence costs today, and if you are considering Copilot for Microsoft 365 as part of the switch to new Outlook, price that separately because it is a distinct add-on with its own per-user cost.

Who each is genuinely for#

The right choice depends on which of the dimensions above matter most for your specific workflow. Two honest recommendations rather than a hedge:

• Stay on classic Outlook if you depend on any COM / VSTO add-in whose vendor has not shipped a web add-in that covers your actual workflow; run VBA macros or custom forms; live in PST files for archiving, compliance holds, or e-discovery; work offline for long stretches; assign mail-folder delegate permissions weekly; or attach files from an internal UNC network share as a matter of policy. These are not preferences, they are structural constraints new Outlook does not solve for.
• Move to new Outlook if your day is mail, calendar, categories, server-side rules, and shared mailboxes; you already use Outlook on the web on other devices and want the same experience on Windows; you value Microsoft's shipping cadence for new features; your organisation has no COM / VSTO investments to migrate; and your compliance team has signed off on third-party mail routing through Microsoft's cloud if you are consolidating personal accounts.
• Run both, deliberately, if you sit in the middle — most enterprises will for a couple of years. Microsoft supports both builds on the same PC; classic can be your workflow anchor for the tasks it still does better, and new Outlook can be your primary client for everyday mail. The mistake to avoid is running both accidentally, with users bouncing between them because a colleague sent a screenshot of the wrong UI. Pick a primary and set expectations.

The one recommendation to reject is the one that says the choice is urgent. It is not. Microsoft published a three-stage model — opt-in, opt-out, cutover — with at least twelve months' notice before each stage reaches production rings. Enterprise opt-out moved from April 2026 to 1 March 2027 per MC949965. Classic Outlook is supported through perpetual and subscription licensing until at least 2029. That gives most organisations a genuine multi-year window to migrate the workflows that need to move and stay on classic for the ones that do not.

The one 2026 retirement that is real is legacy Outlook for Mac against Exchange Online in October 2026 — and that is scoped specifically to legacy Outlook for Mac, not classic Outlook on Windows. Do not let a Mac-side deadline drive a Windows-side decision.

A third option, honestly#

This comparison is between two Microsoft builds, and if you are on Microsoft 365 the answer is one of them. But if part of what pushed you to compare the two is that Outlook itself — either build — is not really the workflow you want to keep, it is worth naming that separately. Third-party mail clients like Mimestream, Thunderbird, or eM Client each solve a specific slice of what Outlook does, with their own trade-offs against Exchange features you may or may not use.

We build AI Emaily, an AI-native email client that connects to Microsoft 365 accounts, Gmail, and IMAP, with an approve-before-send agent and a full undo and audit trail. It does not replace the deep Exchange features classic Outlook wins on above — no COM add-ins, no VSTO, no PST as a live store, no mail-folder delegate assignment surface — and we are not going to pretend otherwise. Where it fits is the layer above the mailbox: triage, drafting in your voice from a Personal Context brain, and closing loops without you touching them. If that is the shape of the problem, start with a 7-day free trial on Pro or Autopilot; card is taken at signup, nothing is charged if you cancel before day seven. Check AI Emaily pricing for what each tier covers.