Introduction

A Microsoft 365 mailbox migration can finish while the user’s Online Archive never appears in Outlook or Outlook on the web. The primary mailbox may work normally, but the archive remains missing because the archive state, license assignment, or mailbox move result did not line up cleanly on the destination side.

Treat this as an archive-provisioning problem instead of a normal mailbox sync issue. Start by confirming whether the mailbox is supposed to have an Online Archive in the destination tenant and whether that archive is actually enabled for the migrated user.

Symptoms

  • The primary mailbox works after migration, but the Online Archive is missing
  • Outlook on the web or desktop Outlook does not show the archive mailbox
  • One migrated user is missing the archive while others still have it
  • The archive existed before the move, but it disappeared after cutover
  • The issue appears after tenant migration, mailbox move, or license reassignment
  • Archive-related retention behavior seems wrong after migration

Common Causes

  • The destination user does not have the license required for Online Archive
  • The archive mailbox was not enabled or re-enabled after migration
  • The mailbox move completed, but the archive state did not follow correctly
  • The client is showing stale profile data after the mailbox change
  • The archive exists, but the user is connected to the wrong tenant or mailbox profile
  • Retention or provisioning delays make the archive appear absent right after cutover

Step-by-Step Fix

  1. Confirm that the migrated user is supposed to have an Online Archive in the destination Microsoft 365 environment, because you need to separate a missing entitlement from a broken client view.
  2. Check the user’s current license assignment and make sure it includes archive capability where required, because archive visibility depends on the destination tenant’s actual licensing state.
  3. Verify whether the archive mailbox is enabled for the migrated user on the destination side, because a mailbox move can complete while the archive itself remains disabled or unprovisioned.
  4. Compare the mailbox state before and after migration if you have records from the source tenant, because this shows whether the archive disappeared during the move or was never recreated.
  5. Test the same user in Outlook on the web and desktop Outlook, because one client can hold stale profile state while the archive is already present server-side.
  6. Rebuild or refresh the Outlook profile only after confirming the archive exists in the service, because client troubleshooting will not help if the destination mailbox was never provisioned correctly.
  7. Check whether the user is connected to the intended tenant and mailbox identity after the migration, because a wrong account context can make the archive seem missing even when it exists elsewhere.
  8. Allow for provisioning completion and retest after any license or archive-state correction, because archive availability may lag behind the primary mailbox during cutover.
  9. Document which migrated users require Online Archive and how it is validated post-move, because archive visibility is often missed in mailbox migration sign-off.