Archive and retention features can influence mailbox capacity, but they also serve distinct operational and governance purposes. Define the requirement before changing configuration.
What problem are we trying to solve?
Is the immediate concern a mailbox approaching capacity, rapid tenant growth, a compliance requirement or a user-access need? Write down the intended result and the evidence supporting it.
Which mailboxes are affected?
Review size, item count, mailbox type, archive status and ownership. Determine whether pressure is tenant-wide or limited to a small number of users or shared mailboxes.
What is the current archive position?
- Which mailboxes already have an Online Archive?
- How much data is in each archive?
- Are archive usage patterns understood by administrators and users?
- Do licence assignments support the intended configuration?
What must be retained—and for how long?
Confirm requirements with the appropriate governance, legal and compliance owners. Avoid using storage pressure alone to determine how long business records should remain available.
What will users experience?
Consider where older content will appear, how search and access may differ, and what communication or support users will need. A technically valid change can still create friction if expectations are unclear.
How will the outcome be validated?
Define the measures to review after any admin-approved change: mailbox growth, archive use, capacity headroom, exceptions and support feedback. Keep a record of the evidence, decision owner and review date.
MailboxVitals provides read-only, metadata-led insight into mailbox and archive health with practical recommendations. It does not change policies or modify mailbox content; administrators retain control of every next step.