Exchange Online In-Place Archive Troubleshooting Guide

When an Exchange Online archive does not move mail, the issue is usually policy scope, folder tag behavior, Managed Folder Assistant timing, mailbox size, or a misunderstanding of what “archive enabled” actually means.

Quick answer: Verify archive status, verify the mailbox retention policy, confirm the folder has a move-to-archive tag, then run Managed Folder Assistant and wait. Archive enablement alone does not move mail.

1. Connect and verify archive state

Connect-ExchangeOnline

Get-Mailbox user@company.com | Format-List DisplayName,ArchiveStatus,ArchiveState,ArchiveName,RetentionPolicy

Get-MailboxStatistics user@company.com -Archive | Format-List DisplayName,ItemCount,TotalItemSize

If ArchiveStatus is not active, the mailbox does not have an active archive target. For shared mailboxes, also verify licensing and archive eligibility before assuming policy failure.

2. Check retention policy and tags

$policy = (Get-Mailbox user@company.com).RetentionPolicy
Get-RetentionPolicy $policy | Select-Object -ExpandProperty RetentionPolicyTagLinks
Get-RetentionPolicyTag | Where-Object {$_.RetentionAction -eq 'MoveToArchive'} | Format-Table Name,Type,AgeLimitForRetention,RetentionEnabled

A default archive tag can move mailbox content after the age limit. A personal tag can be applied to a folder. A folder with a delete tag will not behave like an archive tag. Confirm the actual tag assigned to the folder or mailbox before changing anything.

3. Start Managed Folder Assistant

Start-ManagedFolderAssistant -Identity user@company.com

This requests processing. It is not an immediate “move everything now” button. Large mailboxes can take time, and Microsoft 365 background processing is not always immediate.

4. Common reasons nothing moved

SymptomWhat to check
Archive active but emptyRetention policy has no move-to-archive tag or the item age does not qualify yet.
One folder will not moveFolder has no personal archive tag or the wrong tag was applied.
Shared mailbox archive stuckLicensing, quota, or assistant processing delay.
Policy recently changedWait for policy propagation and assistant processing.
Only some items moveItem age, retention hold, litigation hold, or folder-specific tags.

5. Field notes for operations teams

Do not promise users that archive changes are immediate. Give them a window, record the commands used, and verify with mailbox statistics. For high-volume shared mailboxes, create a simple runbook that captures current item count, archive item count, policy name, archive tag name, and the date you requested Managed Folder Assistant processing.

Safety note: Never test retention changes against a production executive mailbox or legal mailbox first. Use a test mailbox with copied messages and documented rollback steps.
About the author

Jason Purvis works in enterprise monitoring and IT operations, with hands-on experience across ServiceNow ITOM/Event Management, SolarWinds-style infrastructure monitoring, Microsoft 365 operations, alert routing, and incident process improvement.