I'm troubleshooting a user with a 100GB Microsoft 365 mailbox that is currently using about 80GB. Outlook Classic reaches the local OST size limit when configured for Cached Exchange Mode, while Online Mode is noticeably slow for the user. A policy currently forces the mailbox to cache all messages, so reducing the synchronization period is not currently available.
The user has many years of email and wants to retain the history. Deleting tens of gigabytes would take considerable time, and our organization currently does not have mail archiving enabled. Assuming the caching policy cannot be changed, what reliable options are available to provide the best possible Outlook Classic experience without losing historical mail?
4 Answers
If the organization cannot use an online archive, a possible fallback is moving older mail into one or more year-based PST files and opening them in Outlook when needed. Keep the active mailbox small and make sure the PSTs are backed up and not stored in a sync folder.
A shared mailbox with caching disabled can sometimes be used for historical data, but it needs careful permission, search, compliance, and backup review. It is not a substitute for a properly managed archive. Alternative mail clients may offer different offline controls, but they can lack full calendar, contacts, meeting, and directory support, so they’re usually not the best answer for a user who depends on Outlook features.
Have management and compliance define a retention policy. Keeping every message indefinitely because it might be useful someday creates storage, legal, security, and discovery problems. Old mail that must be retained can go into an online archive, while mail that has no business or regulatory value can be deleted according to policy.
Also check Deleted Items, Sent Items, and folders containing unusually large numbers of messages or attachments. Splitting huge folders and removing obsolete attachments can improve Outlook responsiveness, but those steps won’t solve the fundamental OST capacity problem by themselves.
There isn’t a dependable technical workaround for making an 80GB mailbox behave well in one local OST. Increasing the registry size limit may appear to help in some versions, but very large OST files commonly lead to slow searches, synchronization problems, corruption, and long rebuilds. I would avoid presenting that as a supported solution.
The real choices are to enable online archiving, change the caching policy, move older mail into a properly backed-up PST, or have management approve deletion and retention rules. If none of those are permitted, document that the mailbox is exceeding Outlook Classic’s practical limits and escalate the business decision rather than taking responsibility for an unstable configuration.
A local PST can work for historical mail, but only if it is stored outside synchronized folders and included in a reliable backup process. Putting it in OneDrive or another file-sync location can cause locking and corruption issues.
The practical answer is an Exchange Online Archive. It keeps older messages available in Outlook while removing them from the primary mailbox that Outlook is trying to cache. You can apply a retention policy, such as moving messages older than two years, and adjust it based on the user’s needs. The archive can provide substantially more capacity than the primary mailbox, depending on the licensing and configuration.
Once enough mail has moved out of the primary mailbox, the OST should stay below its limit and Outlook Classic should be much more stable. It’s also worth checking whether the archive can be enabled as an organizational policy rather than treating it as a one-off workaround.
That approach has worked well for us. Describing it as a cloud-based PST usually helps users understand that the mail is still searchable and available, just stored separately.
I’d frame this as a policy and risk decision for management: they need to choose between changing the cache requirement, funding archiving, enforcing retention, or accepting the performance and reliability limitations.