I inherited an Exchange setup where a distribution list sends more than 2 GB of high-resolution images from field operations to many users every day. Most users have a one-month move-to-archive policy, but their mailboxes are still filling faster than auto-expanding archives can process the data. The users are accustomed to working from email and would prefer to keep that workflow. I moved the distribution list to a shared mailbox as a temporary measure, but I'm looking for a sustainable solution. One idea is to strip attachments, store them in Azure Blob Storage, and replace them with SAS-protected links. Are there better native, homegrown, or commercial approaches?
4 Answers
Avoid building an attachment-stripping service unless there’s no alternative. You would permanently own the processing, failure handling, permissions, link expiration, auditing, and support burden. SAS tokens and missed uploads could easily turn into operational incidents. Fixing the source system is much safer.
The long-term fix is to change the workflow rather than optimize email storage. Identify the field system or process generating the images and have it upload them directly to SharePoint, Azure storage, or another document platform, with email notifications containing links instead of full attachments. If possible, make management approve storage limits, training, and a transition date so users have time to adapt.
A shared mailbox is a reasonable interim solution because it keeps one copy of each message instead of replicating the attachments into every user’s mailbox. Apply an appropriate retention policy and give the team access to that mailbox. It won’t solve the underlying storage problem, but it can greatly reduce the immediate impact while the workflow is redesigned.
Before choosing a tool, document why the images are being emailed, who needs access, how long they must be retained, and whether anyone needs to edit or search them. Those answers will help determine whether SharePoint, a dedicated file share, object storage, or a purpose-built field-operations system is the right destination. Auto-expanding archives should be treated as a safety net, not as the capacity plan.
That’s what I’ve done temporarily. The images come from field operations, so the next step is finding out whether that process can upload directly to SharePoint or Azure storage instead.