How Search Works in New Outlook vs Classic Outlook

The one difference: a local index versus a server query#

New Outlook search vs classic Outlook search comes down to where the query is answered. In classic Outlook running in Cached Exchange Mode, your mail is copied to a local data file and Windows Search builds a catalog over it, so a search is answered by your own PC. In new Outlook for Windows, the query goes to the server and the results come back over the network.

Everything people find confusing follows from that. Results differ between the two clients because they are reading two different indexes. The old Indexing Status dialog is gone in new Outlook because there is no local catalog to report on. Rebuilding the search index fixes classic and does nothing for new Outlook.

Once you know which client is answering the query, the failures stop looking random. A missing old email in classic is usually a cached-window or index problem. The same symptom in new Outlook is usually scope, sync or connectivity.

Why new Outlook is built this way#

This is not a search decision, it is an application decision. Microsoft Learn describes new Outlook for Windows as built on modern service architecture and inspired by the Outlook web experience, running on WebView2 inside a thin Native Windows Integration Component. In Microsoft's own words, the experience is provided by Outlook on the web, with access to local machine resources through that component.

So new Outlook is, underneath, the web client in a Windows wrapper. The web client has never had a Windows Search catalog, and it does not grow one by being installed as an app.

The same architecture is why COM add-ins are not supported in new Outlook, which Microsoft states on the same page. Search and add-ins are two symptoms of one design.

What the split changes, symptom by symptom#

Here is how the two clients behave, as of July 2026. Rows marked with a Microsoft label come from the feature comparison page, last updated 14 April 2026; verify anything load-bearing there, because it moves.

Is classic search purely local? Not quite#

Classic is local by default, not local by rule. Microsoft's troubleshooting article documents a registry value named DisableServerAssistedSearch aimed at shared mailboxes, which only exists because classic hands some searches to the server.

In practice, an online-mode profile and shared or delegated mailboxes lean on the server, while your own cached mailbox is answered from the local catalog. New Outlook has no equivalent switch: the server answers, and there is no local catalog to fall back to.

Does new Outlook search work offline?#

Yes, within a window. Microsoft lists searching for email among the actions available offline in new Outlook, and offline is on by default. The catch is the size of the offline store: new Outlook offers 7, 30, 90 or 180 days of mail, and the default is 30.

Classic is more generous by design. Cached Exchange Mode defaults to 12 months and can be set to keep everything, so an offline classic search covers years of mail rather than a month.

This is the single most useful thing to know before a flight. If you disconnect from a new Outlook install on defaults, anything older than 30 days is not searchable until you reconnect.

Search syntax and operators: what carries over#

Most of the keyword syntax is shared, because Microsoft documents it for classic Outlook, Outlook.com and new Outlook for Windows on one page. Operators go in the search box as keyword and colon and value, with no space after the colon.

Where the two clients genuinely diverge on searching#

Operators are the compatible part. The builders are not. Classic keeps Advanced Find, reachable with Ctrl+Shift+F, and the custom search-folder dialog that combines conditions across arbitrary fields; new Outlook has neither, and Microsoft support answers say so plainly.

New Outlook answers with a filter panel next to the search box, plus refiners on the results, which classic does not have. So the trade is a saved compound query in classic against faster narrowing of a live result set in new Outlook.

If saved views are what you are actually chasing, our companion post on search folders in new Outlook covers exactly which ones rebuild and which have no equivalent. There is no point duplicating it here.

Troubleshooting: match the fix to the architecture#

Most bad search advice online is classic advice applied to new Outlook. Find your client in the middle column first, then act.

A third option, honestly#

Full disclosure: we build AI Emaily, so treat this as the vendor entry. It leads because the architecture argument above has a third answer that neither Outlook client offers, and because search is the part of our product we would put up against anyone's.

AI Emaily searches every connected account in one ranked list: Gmail, Microsoft 365 and IMAP together, no migration. That matters here because no Outlook client does it. Classic can scope to the mailboxes in one profile, and new Outlook searches the account you have selected, but neither returns a single result set spanning a work Microsoft account and an unrelated Gmail one.

Search runs in two modes. Keyword handles exact terms and operators the way you already type them; Smart ranks by meaning, so the unpaid invoice Acme sent in spring surfaces without you recalling a word from it. Ask AI goes one step further and answers the question directly with the source threads attached. Details are at /features/smart-search and /docs/semantic-search.

Ranking uses a Personal Context brain and client profiles that you set, not a model trained on your mailbox. Anything the assistant drafts off a search result still goes through approve-before-send, with undo and an audit trail.

Where we concede: a local index is instant and it works fully offline over everything you have cached, which is a genuine advantage of classic's model and not one we replicate. Keyword search works offline against cached threads, but Smart search and Ask AI are server-side and need a connection. We are also a separate client, not an Outlook add-in, and we do not import classic search folders.

The Microsoft-native options, stated plainly#

Staying on classic is defensible if a local index and Advanced Find run your day. Microsoft supports existing classic installs until at least 2029, and no firm final cutover date has been published.

Using Outlook on the web alongside classic is the cheapest way to get both indexes. When classic comes back empty, re-run the same query on the web and you are querying the server copy, which is what new Outlook would have shown you.

And if you have already moved, the honest advice is to stop importing classic habits. Set the offline window once, set the default search scope once, and treat the filter panel as the replacement for the dialogs you lost.

The short version#

Classic Outlook answers your search from a Windows Search catalog on your PC. New Outlook is Outlook on the web in a Windows shell, so it asks the server. Two indexes, two sets of failure modes, two sets of fixes.

Practically: in classic, look at the index and the cached window. In new Outlook, look at scope, sync and the offline window, and never rebuild an index that is not there.