Microsoft is pricing SharePoint pay-as-you-go storage at $0.20 per GB per month in public preview. That is the part that matters. Not the nicer admin story, not the “flexibility” line. If your tenant drifts 5 TB over quota, that is about $1,024 per month in extra run-rate before anyone starts cleaning up. Engineers should care because this turns what used to be a licensing purchase into a consumption meter tied to Azure billing, which many Microsoft 365 teams still do not monitor tightly enough.
The original write-up is a useful heads-up, and the feature itself is real. Microsoft has added Microsoft 365 SharePoint Storage as a pay-as-you-go service for commercial tenants in public preview as of June 2026. It is off by default, requires an Azure subscription for billing, and is not currently available for education, GCC, or 21Vianet tenants. Existing Office 365 Extra File Storage add-ons remain available, so this is an additional model, not a forced replacement.
What is Microsoft actually changing?
Previously, if you exceeded SharePoint quota, the answer was usually some combination of deleting data, archiving it, buying Extra File Storage, or living dangerously until sites started hitting enforcement. Microsoft’s own docs still describe the standard tenant allocation as 1 TB plus 10 GB per eligible license, with overage risk eventually pushing the environment toward read-only behavior.
Now there is another option: let SharePoint keep growing past quota and bill only the excess usage.
This is the relevant pricing from Microsoft’s pay-as-you-go table:
| Service | What's counted? | What's billed? |
|---|---|---|
| Microsoft 365 SharePoint Storage | The number of GB of data that exceeds the SharePoint tenant quota | $0.20/GB/month |
| Microsoft 365 Archive | The number of GB archived, only when archived plus active storage exceeds tenant capacity | $0.05/GB/month |
That comparison is where the real decision starts. Active overage storage is 4 times the archive rate. So if your excess data is inactive, the financial signal is pretty obvious: archive it or clean it up, do not just let it sit hot forever.
Why this is useful, and where the trap is
I think this is a good addition, with a catch. The good part is operational: no more panic buying static storage just because you briefly crossed the line. For projects with temporary spikes, migrations, or poorly timed department uploads, pay-as-you-go is cleaner than over-provisioning.
The catch is that it makes storage overruns easier to ignore. Microsoft notes that while a tenant is enrolled in pay-as-you-go SharePoint Storage, you won’t receive quota-related email notifications or banner notifications in the SharePoint admin center, because the tenant is treated as within quota. That is convenient right up until nobody notices storage growth for six months.
This is the second-order effect I’d watch: the pressure to govern content gets weaker at the exact moment the bill gets more variable. If you do not already have decent AI and automation audit practices around ownership, lifecycle, and cost accountability, this can become one more quiet Azure charge that lands in a central platform budget nobody tied back to a business unit.
What admins should do before enabling it
This is not a feature I would switch on without guardrails. At minimum:
- Review current usage in SharePoint admin center, Active sites
- Confirm who owns the linked Azure subscription and who sees the bill
- Set a Microsoft 365 pay-as-you-go budget and alerts
- Decide when to use active overage storage versus Microsoft 365 Archive
- Make sure site lifecycle and deletion policies exist before giving SharePoint a blank check
If you are already building Microsoft Copilot and AI agents or broader PowerShell and Azure automation around M365 governance, this is worth folding into those controls now. Storage meters are boring until they are not.
My view: this is a sensible feature, but also a classic example of Microsoft moving a hard limit into a softer billing surface. For most orgs, no immediate impact because it is opt-in. But if you enable it, treat it like any other consumption service: with budgets, ownership, and a plan to move cold data out of the expensive tier.
