
Check Microsoft 365 service health
Open Microsoft's public service-health page and check whether Microsoft 365 is reporting a current issue. Work or school accounts may also have a more detailed status view in the Microsoft 365 admin center. Save the incident name, affected service, start time, and current status if one is listed.
When a live incident includes Exchange Online or search, do not rebuild a Windows index to fix a cloud-side problem. Try the same search in Outlook on the web and another network only if that comparison is practical. Keep the exact time because a service can recover before someone reviews the case.
Identify the Outlook version and account
New Outlook and classic Outlook do not use the same local search path. Outlook on the web is a third comparison, not a label for either desktop app. Record the app name, version, Windows version, account type, and whether the mailbox belongs to you or is shared.
- New Outlook: focus first on search scope, filters, account selection, and synchronized mail.
- Classic Outlook: include Windows Search indexing, cached mail age, data files, and indexing status.
- Outlook on the web: use it to compare the account and cloud search path.
- Shared mailbox: record whether it was added automatically, opened separately, or searched from your own mailbox view.
Use one known message as the test
Choose a message you can open manually. Save its sender, subject, date, folder, and account. Search one distinctive word from the subject, then the sender address. Do not use confidential names or message contents in a public screenshot or support post.
Keep the test fixed while you change one search control at a time. If you change the query, folder, filters, account, and app together, the final result will not show which branch mattered.
Clear filters and widen the search scope
Microsoft's current Outlook search guidance separates the query from the scope and filters. Clear date, attachment, sender, unread, and folder filters. Then widen the scope from the current folder to the current mailbox or all mailboxes, depending on the Outlook version and account.
- One folder fails: move to the mailbox scope and search the same known message.
- One account fails: select that account directly and compare another account only as a control.
- Recent mail is missing: check synchronization and offline-mail age before indexing.
- Old mail is missing: compare Outlook on the web to learn whether the item exists in the cloud but is outside the local cache.
- Deleted mail is missing: include deleted items only when the current Outlook setting and account support it.
Compare Outlook on the web
Sign in through the normal Microsoft 365 or Outlook web route for the same account. Search the same known message with the same simple query.
- Web and desktop both fail: keep the query, account, time, service status, and message location. The problem is not isolated to the local Windows index.
- Web works and new Outlook fails: focus on the selected account, scope, filters, synchronization, and app state.
- Web works and classic Outlook fails: check cached-mail range, indexing status, indexed locations, and Windows Search.
- The message is absent on the web: confirm the folder and account. Index repair cannot find a message that is not in that mailbox.
For new Outlook, check sync and account limits
In new Outlook, confirm that the search is running against the intended account. Microsoft notes that searches across several accounts can have limits, so repeat the query inside one account before calling the result incomplete.
Check whether the missing message is older than the mail kept offline on the device. If the web result exists but the desktop result does not, keep that age comparison. Do not remove and re-add the account until account access, multi-factor authentication, shared mailboxes, local drafts, and offline work are understood.
For classic Outlook, read indexing status
Classic Outlook can depend on Windows Search. Open Outlook's indexing status and save the number of items that remain. A changing number can mean indexing is still working. A count that never changes, an unavailable search service, or Outlook missing from indexed locations points to a narrower local branch.
Confirm that the Windows Search service is available and that Microsoft Outlook is included in the indexed locations described by Microsoft. Restarting a service or rebuilding the index affects more than one query, so record the current state first. If the computer is managed, ask the administrator before changing service or index settings.
Check the cached-mail range
Classic Outlook may keep only a selected period of Exchange mail offline. A two-year-old message can appear on the web but remain outside the local cache. That is different from a damaged search index.
Record the missing message date and the account's offline-mail range. Increasing the range can use substantial disk space and network bandwidth. Check free storage and organizational policy before changing it, then let synchronization finish before testing the same message again.
Treat shared mailboxes as a separate branch
Shared-mailbox search depends on how the mailbox was added, what scope is selected, what is cached, and which Outlook version is in use. First open the shared mailbox and search from inside that mailbox. Compare the same item in Outlook on the web if your organization permits it.
Record the shared mailbox name without exposing private addresses, the folder, the access method, and whether other authorized users see the same failure. Do not remove permissions, convert mailbox types, or reconfigure organization-wide search from a general guide.
Rebuild the index only after the checks point there
A rebuild can be reasonable when Outlook on the web finds the message, classic Outlook has the mail stored locally, filters and scope are correct, Outlook is an indexed location, and indexing remains stuck or incomplete. It is not a useful response to an active Microsoft incident, a new Outlook scope problem, or mail outside the local cache.
Before rebuilding, save the indexing status, affected accounts, data-file paths, free disk space, Windows version, Outlook version, and time. Expect search results in Outlook and other indexed locations to be incomplete while Windows rebuilds. Do not interrupt a normal rebuild just because the count is still moving.
Know when the administrator needs the case
Escalate a work or school account when several users are affected, the admin center shows an incident, shared-mailbox access changed, policy blocks indexing or offline mail, the mailbox is on legal hold, or web search fails for a known item. Include the time zone, query type, message date and folder, affected client, service-health result, and comparisons already completed.
Do not send message bodies, tokens, passwords, recovery codes, personal addresses, or full screenshots with unrelated mail. Redact what the reviewer does not need.
Keep nearby problems separate
If OneDrive files are also missing or stuck, use the separate OneDrive sync guide. If Windows Settings will not open while you check search services, use the Windows Settings guide. A wider Windows problem can affect the troubleshooting path, but it does not prove why Outlook search failed.
Where OmniMend fits
OmniMend does not repair Microsoft's cloud search, change mailbox permissions, edit Outlook search scope, read private mail, or rebuild an organization-wide index. On a Windows PC, OmniMend can help organize system, storage, service, update, and log clues before you choose a local repair or administrator handoff.
Download OmniMend if you want an optional Windows diagnostic pass after the service, scope, filter, web, and sync checks. Review what OmniMend can inspect, use the help center for product questions, and keep mail contents, account secrets, and organization data out of shared reports.
Editorial sources
Checked September 3, 2026 against Microsoft's current Outlook search troubleshooting, Outlook search scopes and refiners, desktop search service guidance, shared-mailbox guidance, and Microsoft 365 service health. Microsoft provides the version, scope, filter, indexing, cache, shared-mailbox, and service-status branches. OmniMend added the fixed-message comparison, privacy limits, stopping points, and product boundaries.