A DAG Tech cloud solution
Cut SharePoint storage costs.
Keep every file within reach.
Freeze archives inactive SharePoint files into Azure Blob Cold tier, leaves a self-service restore link in the original location, and verifies every copy before an original can be removed.
≈ $15,500 / yearestimated net savings on a 10 TB overage with 85% eligible$42 / TB / month · client-owned Azure storage · full audit trail
30 minutes · your estate size, current overage, and archival fit
The overage gap
Most Microsoft 365 storage bills are overage on data nobody has opened in years. Estimate yours.
view assumptions
Assumes Azure Blob Cold tier, LRS, in a subscription you own, at ≈$0.01/GB/mo ($10.24/TB/mo). Actual Azure pricing varies by region and is billed directly to your subscription, not by DAG Tech.
Implementation is quoted separately based on estate size and complexity. This is a planning estimate, not an invoice.
Cost per TB, per month
SharePoint storage typically runs 10–20x the cost of the same data at rest in Azure Blob Cold tier.
Pricing assumptions used above
- SharePoint overage: your Microsoft invoice rate, default ≈$0.20/GB/mo.
- Azure Blob Cold, LRS, client-hosted: ≈$0.01/GB/mo.
- Freeze service fee: $42/TB/mo of archived data, billed monthly.
- Implementation and onboarding are quoted separately.
12.8 TB estate · 467 sites · 98.7% of files inactive · 94% older than 3 years
Nothing is deleted on assumption.
Every Freeze policy moves through an explicit lifecycle. Only one state in that lifecycle is capable of removing a SharePoint original, and reaching it is a deliberate, confirmed act — not a default.
- Draft
A policy is written and scoped but has never run.
Moves to Simulation before it can touch a single file.
- Simulation
Runs report exactly what would be archived and deleted. Nothing is written or removed.
Requires a completed simulation report before it can be enforced.
- Enforced
The only state that can delete a SharePoint original — after it has been archived and verified.
Promotion requires an explicit confirmation showing the exact scope and blast radius.
- Disabled
Paused. Libraries under this policy are archived and deleted by no run.
Re-enabling returns the policy to Simulation, not directly to Enforced.
- eligibility evaluated
- uploaded to client's Azure
- integrity verified (quickXorHash / SHA-256)
- stub created
- deletion authorized via If-Match eTag
- event recorded
Deletion is the last verified step, never the first operation.
What your people see
When a file is archived, Freeze leaves a small link in its exact SharePoint location. Anyone who needs the file clicks it, signs in with their own Microsoft account — no Freeze account, no IT ticket — and the file is restored.
Because archived files sit in Azure Blob Cold tier, restores aren't instant the way an open file is. Files come back in about the time a download takes, not the time a backup takes.
Control & compliance
Archived files live in Azure Blob storage inside your own subscription, not DAG Tech's. If you ever stop using Freeze, your archive stays exactly where it is.
System and compliance libraries — including the Preservation Hold Library — are excluded from every policy; Freeze never archives or deletes content under hold.
A FreezeArchive column on any file or folder excludes it (and its subtree) from archival, so individual owners can opt specific content out without a policy change.
Every eligibility decision, upload, integrity check, stub creation, and deletion is recorded with who and when, searchable in the dashboard's Audit view.
Technical FAQ
What permissions does Freeze need in our tenant?
App-only Microsoft Graph permissions, granted once by a tenant admin through the standard Microsoft consent flow. Freeze authenticates as an application, not as a user — there's no individual account with a mailbox or a password to compromise.
Where do the archived bytes actually live?
Azure Blob Storage, Cold tier, in an Azure subscription your organization owns and controls — not a DAG Tech tenant. Deletion protection (soft delete, point-in-time restore, a resource lock) is configured on that storage account at onboarding.
What happens if an integrity check fails during archival?
Freeze compares the source file's hash (quickXorHash, falling back to SHA-256) against the uploaded blob before anything else happens. If they don't match, the SharePoint original is never deleted — the run flags the file and it's retried on the next pass.
How does restore authentication work?
An end user clicks the restore link left in the file's original location and signs in with their own Microsoft account. Freeze verifies their sign-in belongs to the same Microsoft 365 organization as the archived tenant — no separate Freeze account, no IT ticket.
What exactly is the ".url" stub?
A small internet-shortcut file that replaces the archived original in SharePoint, in the same folder, with the same display name pattern. Opening it starts the restore flow rather than opening a file.
How do we exclude specific content from archival?
Add a FreezeArchive column value to opt a file or folder out (folder opt-outs apply to the whole subtree), or scope policies away from a library, site, or the tenant entirely. Sites with no matching policy are archived and deleted by nothing.
For MSPs: Freeze runs multi-tenant, with per-client Azure storage you or your client controls, so it fits alongside an existing Microsoft 365 management practice without adding a shared blast radius across clients.
Discuss the partner modelBring your SharePoint storage bill.
We'll map the archive opportunity.
A 30-minute assessment covers your estate size, current overage, and which libraries are realistic candidates for archival — before anything is scoped, simulated, or enforced.