Exchange Online

Diagnose an Archive Not Reducing Primary Mailbox Usage

A repeatable PowerShell procedure for proving whether archive movement is configured, blocked, and actually occurring. Measure first. Change only what the evidence supports.

Written by Published Last reviewed

Estimated Time

20–30 Minutes

Difficulty

Intermediate

Technologies

Exchange Online / MRM / PowerShell

Goal

Separate configuration from proof of processing.

An enabled archive and an assigned retention policy do not prove that eligible items are moving. This procedure captures a baseline, checks the archive and MRM configuration, identifies retention hold state, and measures the mailbox again after processing is requested.

All identities, policy names, tag names, measurements, and example output in this tutorial are synthetic. Replace them only with values from the environment you are authorized to administer.

Before You Start

Begin read-only and preserve an attributable baseline.

Use an authenticated Exchange Online PowerShell session with the permissions required for the cmdlets shown below. Record when each measurement was taken. Do not remove a hold until its purpose and the authority to change it have been confirmed.

Do not treat every hold as the same control

This procedure checks several hold-related properties for context, but the state-changing example applies only to RetentionHoldEnabled, the MRM retention hold documented in KT-000002. Do not change litigation, in-place, or other preservation controls as part of this procedure.

Procedure

Diagnose archive movement in six evidence-based steps.

Step 1

Set the synthetic example identity and capture both mailbox baselines

Measure the primary mailbox and its archive with the same fields. Keep the timestamp with the results so later changes can be compared to a specific baseline. 

$mbx = "user01@contoso.com" # Synthetic identity

Get-EXOMailboxStatistics -Identity $mbx |
    Select-Object DisplayName, TotalItemSize, ItemCount

Get-EXOMailboxStatistics -Identity $mbx -Archive |
    Select-Object DisplayName, TotalItemSize, ItemCount

Preserve both results. A later increase in archive item count can be stronger evidence of movement than waiting for a dramatic primary mailbox size decrease.

Step 2

Inspect archive, policy, and hold state together

Get-EXOMailbox -Identity $mbx -PropertySets Archive, Hold, Policy, Retention |
    Select-Object RetentionPolicy,
                  RetentionHoldEnabled,
                  LitigationHoldEnabled,
                  InPlaceHolds,
                  ArchiveStatus,
                  ArchiveState,
                  AutoExpandingArchiveEnabled

Confirm that the archive is active, note the assigned retention policy, and record every displayed hold property. If RetentionHoldEnabled is True, MRM can continue applying tags while archive and expiration actions for visible mailbox folders remain suspended.

Step 3

Verify the assigned policy and its archive tag

Use the actual names observed in the environment. The names below are deliberately synthetic. 

$policyName = "KER-DEMO-Archive-365"             # Synthetic name
$archiveTagName = "KER-DEMO-MoveToArchive-365"  # Synthetic name

Get-RetentionPolicy -Identity $policyName |
    Format-List Name, RetentionPolicyTagLinks

Get-RetentionPolicyTag -Identity $archiveTagName |
    Select-Object Name,
                  Type,
                  RetentionEnabled,
                  AgeLimitForRetention,
                  RetentionAction

Verify that the policy links the intended archive tag. Confirm that the tag is enabled and that its action is MoveToArchive. Record the tag type and age limit instead of assuming that the policy name describes its effective behavior.

Read-only checkpoint

Before changing anything, the evidence should show whether the archive is active, which policy is assigned, whether the policy links the intended archive tag, whether that tag is enabled, and whether RetentionHoldEnabled is blocking the expected action.

Step 4

Remove the MRM retention hold only when approved

Run this command only when the hold is confirmed to be stale or unintended and the change has been authorized. 

Set-Mailbox -Identity $mbx -RetentionHoldEnabled $false

Query the setting again and retain the result as change evidence:

Get-EXOMailbox -Identity $mbx -PropertySets Policy, Retention |
    Select-Object RetentionPolicy, RetentionHoldEnabled

Continue only after the output confirms RetentionHoldEnabled=False and the intended policy remains assigned.

Step 5

Request Managed Folder Assistant processing

Start-ManagedFolderAssistant -Identity $mbx

The command requests processing; it does not make mailbox statistics change instantly. Record when it was run and allow time before drawing a conclusion from the next measurement.

Step 6

Measure primary and archive statistics again

Get-EXOMailboxStatistics -Identity $mbx |
    Select-Object DisplayName, TotalItemSize, ItemCount

Get-EXOMailboxStatistics -Identity $mbx -Archive |
    Select-Object DisplayName, TotalItemSize, ItemCount

Compare the second result with the original baseline. Look for archive item-count or size growth while the policy and tag remain correct. Do not declare failure solely because the primary mailbox size is unchanged immediately after requesting processing.

Interpretation

Use the evidence to choose the next action.

Archive State

Not active

Stop. Archive movement cannot be proven until the archive state is corrected through the appropriate approved process.

Policy or Tag

Missing or mismatched

Stop. Document the mismatch and correct the intended MRM configuration through a separately approved change.

MRM Retention Hold

Enabled

Confirm why it exists. Remove only when it is stale or unintended and authorization is documented.

Configuration Valid

No immediate movement

Preserve the timestamps, allow processing time, and compare another measured interval before escalating.

Final verification checklist

Archive: active and associated with the expected mailbox.

Policy: the intended retention policy remains assigned.

Archive tag: linked, enabled, and configured with MoveToArchive.

MRM hold: RetentionHoldEnabled=False when removal was approved.

Processing: Managed Folder Assistant was requested and timestamped.

Movement: primary and archive statistics were compared across at least two attributable measurements.

Real-World Notes

Configuration is not the same as execution. A policy can be assigned, a tag can be correct, and the archive can be active while an MRM retention hold still prevents visible-folder items from moving.

Preserve before-and-after measurements. A single screenshot or a single mailbox size is not enough to prove that archiving is working or broken.

Microsoft References

Current documentation for every command used.

Related Case

See the investigation and judgment behind this procedure.

KT-000002

Exchange Online Archive Not Reducing Primary Mailbox

The case preserves the evidence chain, competing explanations, confirmed root cause, authorized remediation, and final verification. This tutorial extracts only the repeatable technical procedure.