New Outlook vs Classic Outlook: What Actually Changed (2026)

The short answer
Classic Outlook is a Windows desktop application; new Outlook is Outlook on the web wrapped in a thin native shell. That one difference explains the rest: COM add-ins, VBA and rules import are gone; PST, offline, Quick Steps, Search Folders and delegation are partial; and third-party accounts sync through Microsoft's cloud.
New Outlook vs classic Outlook differences, by capability: what moved, what is partial, what is gone, and why the architecture predicts all of it.
On this page
- 01New Outlook vs classic Outlook: the short verdict
- 02Why the architecture predicts every other difference
- 03Is new Outlook the same as Outlook on the web?
- 04The difference table: extensibility and automation
- 05The difference table: data, offline and organisation
- 06What it means for add-ins and automation
- 07What it means for offline work, PST files and archives
- 08What it means for rules, Quick Steps and Search Folders
- 09What it means for delegation and shared mailboxes
- 10Does classic Outlook stop working in 2026?
- 11Who should switch, and who should not
- 12A third option, honestly
- 13The short version
New Outlook vs classic Outlook: the short verdict#
The differences between new Outlook and classic Outlook come from one fact worth getting straight before any feature list: these are not two versions of the same program. Classic Outlook for Windows is a desktop application with three decades of accumulated capability. New Outlook is the Outlook on the web experience running inside a thin native Windows shell.
Microsoft's own architecture page says as much. New Outlook is built on WebView2 with a Native Windows Integration Component that gives the web experience access to local machine resources. Once you know that, you can predict most of the gaps without looking any of them up.
The practical verdict as of July 2026: if your day is mail, calendar, search, categories and shared mailboxes, new Outlook covers it. If your day depends on desktop code, local data files, working offline for long stretches, or assigning delegate permissions on mail folders, classic still does things new Outlook does not.
And you are not choosing under a deadline. Classic Outlook is supported until at least 2029. The 2026 cut-off that keeps circulating is a misreading, and there is a section on it below.
Why the architecture predicts every other difference#
Classic Outlook is a Win32 application. It keeps a local data file for your mailbox, talks to the server through its own sync engine, and loads add-in code directly into its own running process. The work happens on your PC, and the server is where it synchronises to.
New Outlook inverts that. The mailbox and most of the logic live in the service, the web experience renders it, and the native shell supplies what a browser tab cannot: notifications, local file access, being your default mail handler. Extensions run as sandboxed web add-ins, the same ones Outlook on the web uses.
That gives you a rule of thumb that holds up across almost the whole comparison matrix.
- If a feature needed code running on your PC, it is gone: COM and VSTO add-ins, VBA macros, custom forms.
- If a feature needed a file on your disk, it is partial: PST archives, a complete offline cache, client-only rules.
- If a feature is really a mailbox feature the server can perform, it is present: server-side rules, categories, shared mailboxes, the Global Address List.
You can preview switch day for free
Is new Outlook the same as Outlook on the web?#
Close, but not identical. The mail, calendar and search experience is the same codebase, which is why the two behave alike and get features at the same time. The native shell is what makes new Outlook a desktop client rather than a bookmark.
The shell adds Windows integration: system notifications, a taskbar presence, local file access, being the default handler for mail links, and a cached window of mail so the app opens with something in it offline.
It also accepts account types the work browser experience does not. As of July 2026 Microsoft lists Gmail, Yahoo, iCloud, IMAP and POP accounts as supported in new Outlook for Windows, alongside Microsoft 365 and Outlook.com.
The difference table: extensibility and automation#
Microsoft publishes a live comparison matrix with four status words: available, partially available, not supported and upcoming. The tables below use those words rather than yes and no, because partial is where the surprises live. Statuses are as of July 2026 and this area moves, so check the matrix for your build before planning a migration around any one row.
| Capability | Classic Outlook | New Outlook for Windows | What it means |
|---|---|---|---|
| COM and VSTO add-ins | Supported | Not supported | CRM, e-signature and dictation panes built as desktop code cannot load |
| Web add-ins | Supported | Supported, and the only extension model | The same add-in works in new Outlook and in the browser |
| VBA macros and the Developer tab | Supported | Not supported | Rebuild repeatable actions as Power Automate flows or Graph scripts |
| Custom forms | Supported | Not supported | No published-form equivalent exists |
| Voting buttons | Supported | Not supported | Use a poll or a form for the same job |
| Server-side rules | Supported | Available | Conditions and actions the mailbox can run by itself carry across |
| Client-only rules | Supported | Not supported; rules overall are partially available | Rules that act on the PC, such as playing a sound, need classic |
| Rules import and export | Supported | Not supported | Rule sets have to be rebuilt by hand, not carried over as a file |
| Quick Steps | Supported | Partially available | Common multi-step actions exist; the full builder does not |
Read the status word, not the headline
The difference table: data, offline and organisation#

| Capability | Classic Outlook | New Outlook for Windows | What it means |
|---|---|---|---|
| PST files | Open, browse and archive to them directly | Partially available | Scope has been changing; confirm what your build does before archiving |
| Offline working | Full local cache of the mailbox | Partially available | Expect a cached window, not a complete offline mailbox |
| Search Folders | Supported | Partially available | Saved searches exist in a reduced form |
| Conditional formatting | Supported | Partially available | Colour-coding rules for the message list are limited |
| Public folders | Supported | Partially available | Check your specific folders, not the feature name |
| Multiple mail profiles | Supported | Upcoming | Separate profiles for separate contexts are not there yet |
| LDAP directories | Supported | Upcoming | Relevant if you query a non-Exchange directory |
| Attaching from a network share | Supported | Not supported | Attach a copy or send a link instead |
| Business cards | Supported | Not supported | A cosmetic loss for most people |
| Third-party accounts such as Gmail | Connects to the provider directly | Synced through Microsoft's cloud | A copy of that mail sits in Microsoft data centres |
| Signatures, categories, shared mailboxes, Global Address List, contacts | Supported | Available | The everyday core is not where the risk is |
What it means for add-ins and automation#
This is the gap people hit first, usually within an hour of switching, and it is the one with no workaround inside the new client. A COM add-in loaded into the classic Outlook process; new Outlook has no such process, so there is no setting that brings it back.
The full audit procedure is written up separately in COM add-ins not working in new Outlook, including how to tell a COM add-in from a web one and how to test the vendor's web version first. The short version: list your add-ins, rank them by how often you use them, and let the daily ones decide.
VBA is the quieter loss, because macros tend to be personal, undocumented and load-bearing for exactly one person. If a macro performed a repeatable action rather than a judgement call, Power Automate or a Microsoft Graph script is the nearest replacement.
What it means for offline work, PST files and archives#
Classic Outlook was built to be usable on a laptop with no connection. It keeps a local copy of the mailbox and syncs when it can, which is why long flights and bad hotel wifi never really broke it.
New Outlook lists offline as partially available. In practice you get a cached window of recent mail and calendar rather than the whole mailbox, and some actions queue until you are back online. If you routinely work disconnected for hours, test that specific pattern before you move, not the feature name.
PST is the same story with higher stakes, because a PST often holds the only copy of old mail. Classic opens them as live folders you can browse, search and file into. New Outlook lists PST as partially available and the scope has moved more than once, so confirm what your build does before trusting it with an archive you cannot lose.
What it means for rules, Quick Steps and Search Folders#
Rules split cleanly along the architectural line. Anything the mailbox can evaluate on the server, such as moving mail from a sender into a folder, works in new Outlook. Anything that needed your PC awake and running, such as playing a sound or filing into a local PST, does not.
The sharper problem is that rules import and export is listed as not supported. A rule set built over years cannot travel as a file, so budget an afternoon to rebuild it by hand and treat that as a chance to delete the ones you stopped needing.
One quota to know while you rebuild, verified as of July 2026: an Exchange Online mailbox has a 256 KB inbox rules quota, raisable for migrated mailboxes. Long rules with many conditions consume it faster than short ones, which is why a large rule set can start refusing new entries.
Quick Steps and Search Folders are both partially available: the common cases are there, the deeper builders are reduced. If either sits in your daily path, rebuild one in new Outlook before deciding, because the answer depends on how you built yours.
What it means for delegation and shared mailboxes#
This is the enterprise blocker, and it invalidates most guides written before 2026 because delegation is only half migrated. Calendar delegation works in new Outlook. Mail-folder delegate permissions still have to be assigned from classic Outlook.
That distinction matters for executive assistants more than anyone. The assistant can generally work in new Outlook once permissions exist; it is the act of granting or changing those permissions on mail folders that sends someone back to classic or to admin tooling.
| Task | Where it works today |
|---|---|
| Assign delegate permissions on mail folders | Classic Outlook, or admin tooling |
| Assign calendar delegation | New Outlook or classic Outlook |
| Work in a mailbox you have been delegated | New Outlook |
| Send on behalf of someone once permissions exist | New Outlook |
| Open a shared mailbox alongside your own | New Outlook |
Does classic Outlook stop working in 2026?#
No, and this is the single most misreported fact in the category. Microsoft's published model has three stages, opt-in then opt-out then a final cutover, with at least twelve months of notice before each stage reaches production rings.
New Outlook became the default for small and medium business in January 2025, with the ability to switch back. Enterprise opt-out is scheduled for 1 March 2027, and that is where the rumour comes from: opt-out changes the default, it does not remove classic. Existing classic installs are supported through perpetual and subscription licensing until at least 2029, and no firm cutover date has been announced.
One 2026 date is real, and it is narrower than the headlines suggest: legacy Outlook for Mac retires for Exchange Online accounts in October 2026. That is a Mac client against a specific service, not classic Outlook for Windows.
| Stage | Timing |
|---|---|
| New Outlook default for small and medium business, revert available | January 2025 |
| Enterprise opt-out begins | 1 March 2027 |
| Legacy Outlook for Mac retires against Exchange Online | October 2026 |
| Classic Outlook supported via perpetual and subscription licensing | Until at least 2029 |
| Final cutover with no switching back | No firm date announced |
Do not plan around a 2026 shutdown of classic Outlook
Who should switch, and who should not#
Because there is no real deadline, this is a fit question rather than a timing one. Match yourself to a row rather than to a general recommendation.
- Whichever way you go, keep classic installed while you can; the toggle back is only useful if the app is still there.
- Re-check your blockers each quarter. Partial and upcoming rows do move, and not supported rows do not.
- Decide from your blockers, not from a count of missing features. One unreplaceable daily tool outweighs ten you never open.
| If you are | Switch to new Outlook? | Why |
|---|---|---|
| Mostly in mail, calendar, search and a shared mailbox | Yes | The core is available, and new features land here first |
| Already living in Outlook on the web most days | Yes | Same experience, plus Windows notifications and local file access |
| Dependent on a CRM, e-signature or dictation add-in built as COM | Not yet | There is no path for desktop add-in code in the new client |
| Running VBA macros, custom forms or a large exported rule set | Not yet | Not supported, and rules cannot be imported as a file |
| An assistant who grants mail-folder delegate permissions | Partly | Calendar delegation works; mail-folder permissions still need classic |
| Frequently offline, or working out of large PST archives | Test first | Offline and PST are both partial, so test your own pattern |
A third option, honestly#
Disclosure first: we build AI Emaily, so treat this as an interested opinion. It belongs here because a share of people asking this question are not really choosing a Microsoft client. They want to spend less time in the inbox and assume the newer Microsoft app is how.
AI Emaily is a separate AI-native email client. It connects Outlook and Microsoft 365 accounts alongside Gmail and IMAP, so one inbox covers accounts either Outlook would keep in separate profiles. It triages, summarises long threads and drafts replies from a Personal Context you write yourself, plus client profiles you control, rather than reading your past mail to imitate you. It runs at three levels: Manual, Copilot where nothing sends without your approval, and Autopilot for narrow cases you allow. Every action has undo and an audit trail, and we do not train on your mail.
The limits, plainly. It does not run COM add-ins or VBA either, so if Salesforce logging is your blocker, classic Outlook is still the answer. It is not an Exchange administration tool, so mail-folder delegation and public folders stay where they are. And it is a hosted client: your mail syncs to our infrastructure, much as new Outlook syncs third-party accounts to Microsoft's.
If the real problem is the hours the inbox takes, that comparison is worth running. If it is a compliance archive or a CRM pane, stay inside the Microsoft decision this article is about.
The short version#
New Outlook is a web client with a native Windows shell; classic Outlook is a desktop application. Every difference that follows is predictable from that, which is more useful than memorising the matrix.
Desktop code is gone, local-file features are partial, mailbox features are present, and delegation is half migrated. There is no 2026 deadline forcing the decision on Windows, so audit your blockers, test the ones that matter in Outlook on the web, and switch when your list is clear.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Microsoft Support — Feature comparison between new Outlook and classic Outlook
- Microsoft Learn — Overview of the new Outlook for Windows
- Microsoft Learn — Guide to product availability and the stages of migration to new Outlook
- Microsoft Support — About delegates: allow someone to manage your mail and calendar
- Microsoft Support — Sync your account in Outlook to the Microsoft Cloud

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.