🚀 Executive Summary

TL;DR: Expanding primary mailbox quotas for 20GB+ user and shared mailboxes severely degrades Outlook performance due to large local OST files, not backend storage costs. The solution involves implementing Online Archiving and Retention Policies to automatically move older emails to cloud-only storage, maintaining small local OSTs and improving user experience.

🎯 Key Takeaways

  • Outlook client performance issues (slow launches, ‘not responding’ errors, corrupted profiles) are primarily caused by local OST files exceeding 20GB, not server-side storage capacity.
  • Online Archiving (In-Place Archive) provides a separate, cloud-only mailbox that does not cache locally, effectively offloading historical data and keeping the primary OST file small.
  • Retention Policies are crucial for automating the transfer of older emails from the primary mailbox to the Online Archive, ensuring continuous mailbox hygiene without manual user intervention.
  • Shared Mailboxes are limited to 50GB by default; exceeding this requires assigning an Exchange Online Plan 2 license to increase their capacity to 100GB.

20GB user and shared mailboxes, should we expand?

Quick Summary: Stop treating email as a file server; learn why expanding quotas hurts Outlook performance and how to implement Online Archiving to keep your users happy and your storage bills sane.

The 50GB Trap: Handling Large User and Shared Mailboxes

I still remember the first time I got burned by the “just expand the storage” mentality. It was 2016, and our VP of Sales, let’s call him “Jim,” stormed into my office. His Outlook was crashing every time he tried to search for a contract. I checked Exchange Admin Center, and sure enough, his mailbox was sitting pretty at 98GB because a previous admin had just kept bumping his quota on an E3 license.

Here’s the thing: The server was fine. The cloud storage was fine. But Jim’s laptop? It was choking to death trying to sync a 98GB .ost file locally. That day, I learned a hard lesson: Just because you can give a user 100GB of space doesn’t mean you should.

If you are staring at a dashboard full of 20GB+ mailboxes and wondering if you should expand them, put the credit card away for a second. Let’s talk architecture.

The “Why”: It’s Not About Storage, It’s About I/O

The problem isn’t usually the backend storage cost (storage is relatively cheap). The problem is the local client performance. Outlook caches email locally in an OST file. Once that file creeps past 20GB—and definitely once it hits 50GB—you enter the “Danger Zone.”

You start seeing:

  • Slow application launches.
  • “Outlook is not responding” errors during search.
  • Corrupted profiles requiring full re-syncs (which kills your network bandwidth).

If you have users treating their Inbox like a file system (we all know that one user who CCs themselves on everything “just in case”), expanding the primary mailbox quota is just kicking the can down the road. Eventually, you run out of road.


The Fixes: From Hygiene to Nuclear

Here are the three strategies I use at TechResolve when a department comes to me begging for more space.

1. The Quick Fix: The Online Archive

This is the “Old Reliable” of Exchange administration. Instead of expanding the primary mailbox, you enable the Online Archive (In-Place Archive). This gives the user a secondary mailbox that lives 100% in the cloud. It doesn’t cache to the local hard drive, meaning their Outlook stays snappy.

Here is the PowerShell to check the status and enable it for a specific user:

# Connect to Exchange Online
Connect-ExchangeOnline

# Check current status
Get-Mailbox -Identity "jim.sales@techresolve.com" | Select-Object Name, ArchiveStatus, ArchiveQuota

# Enable the Archive (If not already active)
Enable-Mailbox -Identity "jim.sales@techresolve.com" -Archive

Pro Tip: Users hate change. Tell them: “It looks exactly like a folder in your Outlook sidebar, but it makes your computer run faster.” Sell the performance, not the storage.

2. The “Set It and Forget It” Fix: Retention Policies

Enabling the archive is step one, but if you don’t automate the movement of mail, Jim is never going to drag-and-drop those emails manually. You need a Retention Policy (or MRM Policy) applied to the mailbox.

I usually recommend a “2-Year Move to Archive” policy. It keeps the current stuff fast and accessible, while the historical data sits in the cold storage.

# Apply a retention policy (Assuming you created one named 'Standard-2Year-Archive')
Set-Mailbox -Identity "shared-marketing@techresolve.com" -RetentionPolicy "Standard-2Year-Archive"

# Force the Managed Folder Assistant to process it immediately (don't wait 7 days)
Start-ManagedFolderAssistant -Identity "shared-marketing@techresolve.com"

3. The ‘Nuclear’ Option: Licensing Upgrades & Shared Mailbox Limits

Sometimes, you really do just need the space. If you are dealing with a Shared Mailbox (like info@ or support@), remember the hard limits:

Mailbox Type Free Limit Required License for >50GB
User Mailbox N/A (License dependent) Exchange Online Plan 2 (100GB)
Shared Mailbox 50 GB Exchange Online Plan 2 (Allows 100GB)

If your shared-sales mailbox hits 49GB, it stops sending/receiving. It breaks. At that point, you have to assign a license to that Shared Mailbox to bump it to 100GB. It feels “hacky” to pay for a shared mailbox, but sometimes the business cost of deleting old leads is higher than the $8/month license.

My Final Verdict

If you are hovering around 20GB, you are safe for now, but don’t get comfortable. Implement the Online Archive now. It separates the “hot” data (recent emails) from the “cold” data (that PDF from 2019), keeping the local OST file small and the user experience smooth.

Don’t just expand the quota. You aren’t fixing the problem; you’re just building a bigger junk drawer.

Darian Vance - Lead Cloud Architect

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.


🤖 Frequently Asked Questions

âť“ Why does my Outlook client become slow or crash when my mailbox is large, even if the server has plenty of space?

Outlook performance issues stem from large local `.ost` files, typically when they exceed 20GB-50GB. The client struggles with I/O operations, leading to slow launches, ‘not responding’ errors, and profile corruption, regardless of backend server storage.

âť“ How does enabling an Online Archive compare to simply increasing a user’s primary mailbox quota?

Expanding the primary mailbox quota only delays performance issues by allowing the local `.ost` file to grow larger, exacerbating client-side problems. Online Archiving creates a separate, cloud-only mailbox that doesn’t cache locally, preserving client performance by keeping the primary `.ost` small while still providing access to historical data.

âť“ What is a common pitfall when implementing Online Archiving and how can it be avoided?

A common pitfall is enabling the archive without also implementing Retention Policies. Users rarely manually move emails to the archive. This can be avoided by applying a Retention Policy (e.g., ‘2-Year Move to Archive’) to the mailbox and using `Start-ManagedFolderAssistant` to automate the data migration.

Leave a Reply

Discover more from TechResolve - SaaS Troubleshooting & Software Alternatives

Subscribe now to keep reading and get access to the full archive.

Continue reading