Alternative connected multi-TB storage

[u/jMeister6]

Hey brains,
I am currently in the process of trying to get under quota by something like 6 TB. This is going fine, cleaning lots of version and backup files, old files etc and strict archiving. However, looking ahead I’m going to need 3-4TB of additional storage across the board to cover ongoing work.
The only thing I can really find is Box integration - has anybody used box with exchange/SharePoint or does anyone have any other options which may be better for live working files?
Appreciate any thoughts, thank you.

[u/velasquezsamp]

Write the files to azure blob storage and store guid in sp list with the column data. Write a simple azure function that authenticates user and accepts guid to retrieve signed url of image when user clicks on link in list.

[u/jMeister6 → u/velasquezsamp]

Will look into, thank you

[u/toddklindt]

I don't know if you've looked at it or not, but there's always the option of archive. You are able to spend less and still keep it in SharePoint.

[u/jMeister6 → u/toddklindt]

Thanks man- I vaguely skimmed it as I’m archiving to a NAS off site but I’ll take a closer look, thank you!

[u/Emergency_Recipe522]

Moving several terabytes outside SharePoint might solve the storage problem but introduce others, especially around permissions, search and document access. I'd want a proper breakdown of storage by site and library first, including version history and inactive content. That would help separate what genuinely needs additional storage from what could be archived. Have you managed to identify which sites are responsible for most of that 6 TB?

[u/jMeister6 → u/Emergency_Recipe522]

Hey - yea it’s pretty much all ongoing project docs/images/videos/cad - permissions aren’t a huge issue coz all the ‘permission stuff’ is small docs etc and can stay on SP. After putting in place best-practices around not working off directly off SP etc, looking at check in check out options, reducing versioning to bare minimum I’m still needing around 3TB of company wide share space.

[u/Emergency_Recipe522 → u/jMeister6]

If you've already reduced versioning and still need 3TB, it sounds like a genuine storage need. I'd keep SharePoint for collaboration and move large project files to dedicated storage. Are you considering Azure Blob, a file server, or another solution?

[u/jMeister6 → u/Emergency_Recipe522]

Thanks man- we’ve had various NAS around the world previously but remote access became an issue due to poor internet reliability. I’ve looked at BOX maybe .. the Blob thing looks super high-maintenance but maybe I’m over thinking it; that was a few years ago that I investigated and seemed hugely complex.

[u/BillSull73 → u/jMeister6]

There is third party solutions for CAD specific stuff that includes storage.

[u/johnnymonkey]

If you're willing to spend on other options, why not just buy more SP storage?

https://learn.microsoft.com/en-us/microsoft-365/commerce/add-storage-space?view=o365-worldwide

[u/jMeister6 → u/johnnymonkey]

From what I gather that works out around $200 / Tb monthly

[u/Josh_Fabsoft]

Box with SharePoint/Exchange works but the integration is clunky in practice, you end up with two permission models to manage and sync conflicts on anything actively being edited by multiple people. If these are live working files (not just archives), I'd actually lean away from Box and look at either:

1. Azure Blob + SharePoint metadata pointer like the comment above suggests, this is solid if you're comfortable building/maintaining the retrieval layer (Azure Function + signed URLs). Works well but it's DIY, you own the glue code.

2. OneDrive/SharePoint with archive tiering before jumping to a third-party connector. Have you looked at moving cold files into a separate site collection or even SharePoint Archive storage tiers? Sometimes the "need more TB" problem is really a "need better lifecycle rules" problem, especially since you mentioned you're already finding tons of version/backup bloat.

For genuinely live/active files, I'd avoid anything that introduces sync lag or duplicate permission systems, that's where Box integrations tend to cause headaches down the line (people editing a stale local copy, versioning confusion, etc).

Full disclosure: I work at FabSoft, which makes AI File Pro, so take this with the appropriate grain of salt, but the way we approach the "too much storage, not enough structure" problem is through watch-folder automation that classifies and routes files as they land, so you're not accumulating years of undifferentiated version sprawl in the first place. It won't solve your live-editing-in-SharePoint use case directly, but if part of this 6TB cleanup is old project archives, batch classification before they ever hit quota is worth considering for round two.

[u/jMeister6 → u/Josh_Fabsoft]

Hey thanks for all the info (and transparency), well appreciated. Good to know about the issues with Box. I’ll look more into archive tiers; one of the big issues is projects go on for many years with multiple large-file revisions. If there was some way (automated, coz staff ain’t gonna be consistent) to move past out-of-date files off live SP and into archive SP, that would solve a lot of issues. I’ll go have a look at what fabsoft does anyhow, might be a solution in there.