If you moved to the new Outlook and your search broke, every classic repair on the internet - the service, the index, the rebuild - is aimed at machinery the new app barely uses. For server accounts, the new Outlook asks Microsoft's servers to search, and the servers keep their own index. This page draws the map honestly: which Outlook searches where, and which fix belongs to which world.
Two programs share the name Outlook and almost nothing about search. Classic Outlook with a PST file searches a catalogue on your own PC, maintained by the Windows Search service - the entire rest of this series is about that machine. The new Outlook is built around server accounts: for Microsoft 365, Outlook.com and Exchange mailboxes, your words travel to the server, the server's index answers, and your PC's indexing state is mostly irrelevant. Applying classic fixes to the new app is not just wasted effort - it sends people hunting through services and rebuilds for a problem that lives in an account or an app cache.
The map that decides which repair book to open. Find your row before touching any setting.
The two apps look similar and coexist on the same PC. Classic Outlook carries the full ribbon, the File tab with Options, and the search machinery described across this series. The new Outlook is the streamlined app Microsoft has been rolling out as the default, with a simpler settings panel and a strong assumption that your mailbox lives on a server. Every search decision that follows starts with this identification - check before you fix.
There is no local index to rebuild for a server account in the new app, so change tools:
Classic Outlook against an Exchange or Microsoft 365 server splits the work, and knowing the split explains its strangest symptom. Mail inside your cache window (the OST) is searched locally; results for older mail come from the server - that is what the line Click here to view more on Microsoft Exchange at the bottom of results means. If that line never appears and old mail seems missing, suspect the server half: a too-short cache slider hiding the years, or server search unavailable. The fix is the slider or the server, not the local index.
A POP account downloading into a PST, or archives kept as PST files, have no server index behind them at all - your PC's catalogue is the only one that will ever exist. For those accounts the classic machinery is the whole story: status counters, the Windows Search service, indexed locations and, when truly corrupt, the rebuild. This is also why heavy PST archives still belong in classic Outlook: the new app's handling of PST files has arrived in stages and is not yet the full classic experience.
The video works on the classic Outlook machinery - pair it with this page's map and you will always know whether a search problem is yours to fix or Microsoft's.
Watch Full VideoYour phone's mail app also asks the server, and it got an answer - so the server index is healthy and the fault is inside the desktop app: a stale session or cache. Fully close and reopen the app, install its updates, and if the gap persists, remove and re-add the account in the app.
For Microsoft 365, Outlook.com and Exchange accounts, effectively no - search is performed against the server's index. That is why rebuilding the Windows index, the classic cure, does nothing for new Outlook search failures on those accounts.
Classic Outlook. It fully supports PST files - opening, searching and indexing them through your profile - while the new Outlook's PST support has rolled out gradually and remains the thinner experience. Keep the archives in classic, and let the new app handle the server mailbox if you prefer it there.