Hey folks! I'm looking for some strategies to manage very large shared mailboxes (over 30 GB) in Exchange Online. We're dealing with heavy usage as many users are constantly reading, moving, and replying to dozens of emails every minute.
The big problem is that caching these shared mailboxes in Outlook results in incredibly large .ost files (10-20+ GB), leading to local performance issues and sync glitches. On the flip side, if we opt not to cache, Outlook has to fetch emails live from Exchange, which can slow things down and make searches less reliable.
Here's what I've gathered: when accessing shared mailboxes in Outlook, we usually encounter longer sync times compared to primary mailboxes, and real-time updates seem limited due to throttling policies and the way Outlook handles these connections. Meanwhile, using OWA or the new Outlook app appears to offer a better experience with real-time updates, as they rely on persistent connections.
I'd love to hear thoughts on the following: should we transition to using OWA or the new Outlook app for these high-activity mailboxes? Would it help to split them into smaller functional mailboxes (like support@, sales@)? Would reducing the cached timeframe or upgrading client hardware offer any significant benefits? Lastly, should we just consider giving users personal mailboxes and rely on distribution groups for collaboration? Looking forward to your insights!
4 Answers
It sounds like you're in a tough spot! First off, clarify why you're using shared mailboxes. Often, a proper CRM or ticketing system can handle email tasks more efficiently, especially in sales or support roles. This might save you a ton of hassle with mailbox performance.
Exactly! Using a CRM might turn out to be a more sustainable solution in the long run.
Disabling automapping might be the way to go. I’ve done it by re-adding the shared mailbox as a separate account in Outlook Classic. This way, you can manage settings and have a unique signature for each mailbox! Just a heads-up, it can be a hassle to do this at scale, though.
True, but scaling this solution could become a real challenge!
This is a solid tip! Definitely saves on complications.
Yes, mapping shared mailboxes as full secondary accounts is crucial. You avoid the 50GB cache limit and access useful features like custom signatures. Just ensure your local cache is kept small to avoid performance degradation. And if your clients need speed, 16GB RAM is pretty much a must these days!
Exactly! It’s amazing how much difference the right hardware makes.
I totally agree, proper hardware can really boost Outlook performance.
Have you explored using function-based shared mailboxes? It helps with compliance and maintaining separation of duties. Plus, with the new Outlook Monarch, it will soon allow shared mailboxes as accounts, which should simplify things significantly for you!
Totally! The inconsistencies really hurt productivity.
I agree! It’s frustrating how mixed up the implementation has been across platforms.
Good point! A CRM could definitely streamline the workflow and reduce reliance on email.