Rebuilding an Outlook profile is a large, slow, destructive-feeling action: it
discards the local OST and re-downloads the mailbox. On a 90 GB mailbox that is most
of a working day. It is also the most over-used step on a service desk, because it
occasionally fixes things by accident.
Decide deliberately.
Establish which side is failing first
Open Outlook connection status and read three things:
- Connection — connected or not, and over what.
- Authentication — modern authentication, and whether a token was acquired.
- Last token acquisition — success, or a failure code.
Then compare against Outlook on the web from a different device. That single
comparison splits the world in half:
| Web works | Web fails | Conclusion |
|---|---|---|
| Yes | — | Server-side data and permissions are fine. Look at the client or the profile. |
| — | Yes | The problem is in the service, the mailbox, or the identity. The client is innocent. |
Cases where a rebuild is not the answer
- The mailbox is over quota. The rejection is server-side (
550 5.2.2). A new
profile hits the same wall.
- A shared mailbox is missing. Auto-mapping is a server attribute. A new profile
reads the same attribute.
- Mail was never delivered. Quarantined or blocked messages are not in the
mailbox, so no cache can show them.
- Sign-in fails with a policy or MFA code. Nothing in a profile affects
Conditional Access or authentication method registration.
In each of these a rebuild costs hours and changes nothing.
Cases where a rebuild is reasonable
- The OST is genuinely corrupt — repeated
0x8004010F, or Outlook crashes opening a
specific folder while the same folder is fine on the web.
- The profile points at a stale server or a migrated mailbox after a tenant move.
- Search is broken locally and rebuilding the index has not helped.
- A cached credential is wedged and clearing the Credential Manager entry did not
resolve the prompt loop.
Cheaper things to try first
- Fully exit Outlook (not just close the window) and reopen.
- Clear the stale entry in Windows Credential Manager for the affected account.
- Run the Support and Recovery Assistant — it identifies profile and
connectivity faults without destroying anything.
- Toggle Work Offline off, if the client is showing Disconnected.
- Test with a new profile alongside the existing one rather than replacing it.
If you do rebuild
- Warn the user how long the re-sync will take and check they can work meanwhile
(Outlook on the web still works).
- Note the OST size in the ticket before you start.
- Confirm any additional mailboxes reappear afterwards — auto-mapped mailboxes come
back only if the server attribute says so.
Related
- Shared mailboxes and auto-mapping
- Mailbox quotas and archiving
- Reading sign-in failure codes (AADSTS)