Several users have mailboxes that are 85–95% full, and a couple have Exchange plans that raise the quota to 150 GB. The organization uses retention and archive policies, but some users were excluded because the archive also needs to expand, and certain messages must be retained for up to 15 years due to industry regulations. Microsoft's archive and auto-expanding storage changes can also take time to propagate. I'm considering exporting or archiving mail in yearly batches, deleting messages with large attachments, and temporarily adjusting retention policies before enabling them again. Is this a sensible approach, and what should I verify with compliance or legal before making changes?
4 Answers
First separate the cloud mailbox problem from the Outlook client problem. Exchange Online can support larger quotas with the right licensing, while the local OST or PST file can become a performance and stability problem. Increasing the local file limit is possible, but it usually makes Outlook harder to manage. If offline access is not essential, disabling cached mode for the affected users—or using the newer Outlook client—may avoid the local-storage issue.
Start by identifying what is actually consuming the space. Large attachments, sent items, deleted items, and calendar data can account for a surprising amount. Targeted cleanup of redundant messages and attachment-heavy mail can help, but avoid broad searches such as deleting everything containing “unsubscribe” unless the results are reviewed and the messages are definitely outside the retention requirements.
For very large historical mailboxes, consider a supported cloud-based archive or backup product rather than building an in-house mail-archiving system. Older mail can remain searchable or recoverable without keeping every year in the primary mailbox, but make sure the product preserves metadata, searchability, retention controls, and eDiscovery capabilities.
A custom retention policy may help move older mail into the archive automatically. Set the age threshold according to the organization’s retention requirements, then use PowerShell to run the Managed Folder Assistant rather than waiting for the normal processing cycle. Be careful not to treat archiving as deletion: confirm that the archive, retention labels, holds, and audit requirements still satisfy legal and regulatory obligations before changing anything.
I’d get written approval from legal or compliance before bulk-exporting, deleting, or changing retention. A 15-year requirement may involve preservation holds or retention labels that ordinary mailbox cleanup could bypass.