1. Establish your 2025 baseline
Start with the numbers finance already recognises. Export the last 12 months of SharePoint storage consumption from the Microsoft 365 admin centre and calculate the monthly average.
These values feed directly into the forecast model below. Replace them with your actual metrics.
2. Segment workloads
BlobBridge is most impactful where content is binary-heavy (media, engineering outputs, archives). Allocate each workload to one of three buckets:
- Keep in SharePoint: Collaboration libraries with retention or compliance dependencies.
- Migrate to BlobBridge: Libraries where users only need the SharePoint UI, not the storage features.
- Archive elsewhere: Data that can move to cold storage or be deleted following records policies.
Most customers shift 40–70% of their terabytes to BlobBridge once they account for media centres, knowledge bases, project handovers and system exports.
3. Model Azure Blob costs
BlobBridge maps 1:1 to Azure Blob containers. You control the tier (Hot/Cool/Archive) and therefore the price. Below is a reference table using publicly listed UK South pricing as of October 2025.
| Tier | £ / GB / month | Notes |
|---|---|---|
| Hot | 0.015 | Interactive workloads, frequent updates |
| Cool | 0.010 | Read-heavy, monthly writes |
| Archive | 0.002 | Long-term, infrequent access |
Prices exclude transactions and data egress, which are typically negligible for intra-region SharePoint usage.
4. Build the 2026 scenarios
Combine your baseline, growth rate and BlobBridge adoption assumptions. The example below uses three scenarios (conservative, expected, stretch):
| Scenario | SharePoint TB (2026) | BlobBridge TB (2026) | Monthly SharePoint cost (£) | Monthly Azure cost (£) | Total monthly (£) | Monthly saving vs status quo (£) |
|---|---|---|---|---|---|---|
| Conservative | 15 | 12 | 2,850 | 135 | 2,985 | 950 |
| Expected | 12 | 18 | 2,280 | 180 | 2,460 | 1,740 |
| Stretch | 9 | 24 | 1,710 | 230 | 1,940 | 2,500 |
The “Monthly saving” column compares each scenario to doing nothing (letting SharePoint grow to 26 TB x £0.19 = £4,940 per month). Even the conservative BlobBridge plan halves the spend.
5. Communicate the forecast
Finance wants traceability, IT leadership wants feasibility. Package the story around four pillars:
- Volumes: SharePoint vs BlobBridge TB per quarter.
- Cost curve: Monthly cost under each scenario, including licence amortisation.
- Key activities: Container creation schedule, SAS rotation cadence, site rollout plan.
- Risks & mitigations: What happens if adoption lags? If storage growth spikes?
BlobBridge customers often anchor the forecast to existing media-heavy departments (Marketing, Product, PMO) because the savings are immediate and demonstrable.
6. Turn forecast into execution
Numbers alone do not deliver savings. Pair the model with a concrete plan:
- Q4 2025: Finalise governance, deploy BlobBridge to pilot sites, validate SAS lifecycle.
- Q1 2026: Onboard the first 5 TB of workloads (media libraries, knowledge bases).
- Q2 2026: Expand to engineering/operations libraries, introduce Azure lifecycle policies to cool tier.
- Q3 2026: Review growth against forecast, adjust container allocation, renew licence if required.
Layer this roadmap into your PMO tooling so tasks surface alongside other digital workplace projects.
Key takeaways
- BlobBridge makes Azure Blob pricing accessible to SharePoint users without new training.
- Baseline measurements + realistic growth assumptions unlock conversations with finance.
- Even cautious adoption scenarios create four-figure monthly savings versus SharePoint add-ons.
- Governance (RBAC, SAS rotation, monitoring) needs to be written into the forecast deliverables.