| Option | How it works | Pros | Cons / Risks | Best for |
|---|---|---|---|---|
| BlobBridge (this product) | Mounts an Azure Blob container inside a SharePoint page. | SharePoint‑native UX; keep TBs in Blob (low cost); no sync client; fast rollout. | Governed by Azure permissions, not SharePoint; requires SAS management; egress charges on heavy downloads. | Teams with lots of media/archives needing direct access in SharePoint. |
| Buy more SharePoint storage | Purchase Microsoft 365 SharePoint capacity add‑ons. | Zero change to user experience; data stays in Microsoft 365 compliance boundary. | Highest monthly cost per GB; not ideal for infrequently accessed or very large files. | When budgets are flexible and compliance must stay solely in M365. |
| OneDrive/Sync to Blob (custom) | Keep data in Blob; sync a subset to local + SharePoint shortcuts. | Flexible; works for small, curated sets. | Operational overhead; user confusion; not scalable for TBs. | Small teams with limited scope. |
| Microsoft 365 Archive | Cold‑storage for inactive SharePoint sites/libraries. | Very low cost per GB for inactive data. | Not for active, in‑place browsing; restore workflows add friction. | Compliance archiving where access is rare. |
| Marketplace alternatives | Other SharePoint web‑parts connecting Blob. | Variety of features and pricing. | Some require storage access keys or subscriptions; ensure security posture meets your standards. | When you need a different feature mix or pricing model. |
Cost notes
- Azure Blob Hot/Cool tiers are typically a fraction of SharePoint add‑on storage per GB.
- Egress fees apply for outbound data; keep storage region close to users and consider CDN.