What it is and how content gets there
Enabling the archive (Enable-Mailbox -Archive) gives the user a second, separate mailbox surfaced in Outlook/OWA. Content arrives two ways: users drag it, or — the scalable path — an MRM move-to-archive tag (default DPT, e.g. 'move items > 2 years') runs via the Managed Folder Assistant (retention concept's engine). The strategic job: kill PSTs — decades of .pst sprawl (unbackuped, uncompliant, corruption-prone) imported into governed archive space.
Auto-expanding archives (the capacity story and its catch)
Beyond the base archive quota, auto-expanding adds storage in chunks up to a large ceiling (multi-TB) — 'unlimited enough'. The catches:
- Provisioning is asynchronous and lagged: enabling auto-expand, then hitting the base limit, then WAITING for expansion — the 'archive is full' window before the system catches up.
- Auxiliary archives fragment access: expanded storage lives in additional archive units; some access paths (certain search/export, older clients) handle the fragments imperfectly — eDiscovery over deep auto-expanded archives is where surprises live (compliance teams: test your export against a big one).
- No going back cleanly: auto-expand is a one-way enablement in practice — plan it as permanent.
Access and lifecycle gaps
The archive is NOT offline-cached like the primary (search needs connectivity — the 'I can't find old mail on the plane' ticket); mobile access to archive is limited; and shared-mailbox archives have their own licensing/size rules (species concept's free-tier edges apply). On leaver flow: the archive rides the primary's fate (inactive/hold covers both) — but VERIFY, because 'we held the mailbox' occasionally missed that the crown-jewel history was in the archive half.
What to watch (proofs)
- Archive enablement + fill: Get-Mailbox -Archive | Get-MailboxStatistics -Archive — who has one, how full, expansion state; the near-ceiling report is next month's 'archive full'.
- Move-tag reality: the archive DPT assignments (retention scan) — what's actually flowing to archive vs sitting in bloated primaries.
- PST eradication progress: import batch history + endpoint PST detection (where tooled) — the project's burn-down.
- The eDiscovery-over-archive test: an export spanning a big auto-expanded archive, item-count reconciled — the compliance proof that fragments didn't swallow anything.