When the Free Tier Ends, So Does Your Data

Digital sovereignty is not about where your data sits. It is about whether you can leave with it, and whether continuity of access is your decision or somebody else’s. In June 2026, a large number of small nonprofits found out that neither was true for them.

Slate reported on August 18 that Microsoft’s retirement of its free Microsoft 365 Business Premium grant for small nonprofits ended with deleted OneDrive accounts and unrecoverable data. The program had run since 2013 and, according to nonprofit consultant George Weiner quoted in the piece, covered roughly 400,000 small organizations worldwide. They did not all lose access on one date: each organization’s grant ended on its own renewal date, so they came off the program in batches of roughly 33,000 a month, about a year’s worth of staggered cut-offs. A Microsoft representative told one affected nonprofit that around 171,000 small NGOs “lost everything” in their OneDrive accounts. That figure comes from a phone call relayed by a single source, not from Microsoft’s official statement, so treat it as a claim rather than a confirmed number.

Microsoft’s position, given to Slate: the offers were “retired to streamline our grant offerings and simplify our grant portfolio,” the company “strongly advised” customers to move to a different Microsoft 365 nonprofit offer before their renewal date, and it “began notifying nonprofit customers in Spring 2025.” Some nonprofits confirm they were warned in time and migrated without loss.

The details that matter are in the cases where it went wrong.

Ronald Khosla, who runs the environmental venture nonprofit Canopy, renewed his license in October 2025 and holds an email from Microsoft confirming access until October 4, 2026. His data was deleted on June 11, 2026. Support first told him the files could be retrieved, then called back to say they were gone permanently. One operator of a children’s healthcare nonprofit lost about 500 gigabytes and had no external copy, specifically because OneDrive offered automatic backup syncing. Another organization’s warnings had gone to an admin mailbox that did not forward anywhere and could not be opened in the desktop client, while the invoices that did arrive were billed at zero and gave no hint anything was ending.

The counterargument, and where it holds

The obvious reading is that there is no free lunch. It is a fair reading, and it is partly right.

This was a grant, not a purchase. Microsoft was entitled to end it. The organizations that let a donated product carry roughly 30 percent of their IT spend, Weiner’s estimate for a sector where most American nonprofits operate on annual budgets under one million dollars, took a risk they never priced. A free tier carries no service level commitment, no retention obligation, and no migration support. None of that is hidden.

If the story ended with “Microsoft withdrew a discount,” there would be nothing to write about.

Where it breaks

Withdrawing a discount is a commercial decision. Destroying the customer’s data is a custody decision. They are not the same event, and three things in this story are not explained by the price being zero.

The paperwork did not hold. Khosla had written confirmation of access through October 2026 and was purged in June. Whatever the grant terms said, the customer’s own record of the agreement gave him no protection, no notice period, and no recourse. A paying customer whose subscription lapses during a billing dispute sits in exactly the same position, holding exactly the same kind of paperwork.

The vendor owned the channel that announced its own withdrawal. Notifications went to tenant admin identities that exist only inside the service being switched off. When the provider controls both the service and the only channel that tells you the service is ending, “we notified you” cannot be checked from the customer’s side. This is not a communications failure. It is a structural property of a stack where identity, mail, storage, and billing all belong to one vendor.

Sync was sold as backup. The 500 gigabytes were lost because the vendor’s own convenience feature had replaced the customer’s independent copy. Continuous sync to a provider is not a backup, because it faithfully replicates deletion. If the only copy of your data lives inside the system that can delete it, you have redundancy against disk failure and nothing else.

The fair objection here is that this organization simply had no business continuity plan and did not understand backups. That is true, and it is not a defense of the vendor. The word on the feature was “backup”, and a two-person nonprofit read the label rather than the architecture. Selling replication under the name of the thing it is not is how an organization ends up with one copy while believing it has two.

None of these three depend on the customer being a nonprofit, and none depend on the service being free.

The free tier is the leading indicator

Read this as a warning about grants and you will miss it. A vendor has the least obligation at the bottom of its price list, so that is where portfolio decisions get tested first. They arrive in the paid tiers later.

The pattern is already visible. HashiCorp moved Terraform to the BSL, which is why OpenTofu now exists under the Linux Foundation. ti&m CEO Thomas Wüst said at the Swiss Software Festival 2026 that his company’s Jira license costs rose roughly 900 percent between 2023 and 2027 through the forced path from Server to Data Center to Cloud. The backdrop is that storage is under pressure everywhere: Microsoft has been running into Azure capacity constraints as AI capital expenditure balloons. The nonprofits were not singled out. They were simply cheapest to drop.

Your organization is also somewhere on that price list.

What sovereignty actually means here

The usual sovereignty debate is about jurisdiction: which law applies, whether the CLOUD Act reaches your data, which flag is on the data center. Those questions matter. They would not have saved a single one of these nonprofits. Their data sat in ordinary data centers under ordinary terms, and it was destroyed by a routine portfolio decision.

The sharper test is operational, and it has two parts:

1. Can you leave with your data, today, without the provider’s cooperation? Not “is there an export API in the documentation,” but: when did you last restore from a copy the provider can neither reach nor switch off?
2. Is continuity of access a decision you get to make? If the provider changes its offer, its pricing, its ownership, or its politics, does your service keep running while you decide what to do?

For regulated Swiss organizations, this is not philosophy. Under FINMA supervision, you must be able to document an exit from any provider within twelve months or you are not compliant. EMBAG has required federal software to be open source by default since 2024, so that no vendor can hold the source to public infrastructure hostage. The Ständerat’s June 2026 vote for a digital sovereignty impulse program points the same way. The regulator has been asking the operational question all along, while most procurement processes still ask the jurisdictional one.

Five questions worth asking your provider

• If our contract ended tomorrow, how long would our data remain retrievable, and where is that stated in writing?
• Which mailbox receives service-end notices, who reads it, and does it live inside the service being notified about?
• Do we hold a restorable copy outside the provider, and when did we last restore from it?
• If the provider raised prices or dropped the product, could we run the same software with a different operator, or would we be rebuilding?
• Is the software under a license that can be revoked, or one that cannot?

The last one is worth dwelling on. Open-source licenses such as GPLv2 grant permanent local operational control and are generally excluded from export control regulations, unlike proprietary licenses that can be revoked or sanctioned. That is a legal property of the license, not a promise from a vendor.

How we answer them

VSHN has operated production infrastructure for regulated Swiss organizations since 2014, and we were Switzerland’s first CNCF Kubernetes Certified Service Provider in 2019. We are ISO 27001 certified and a Red Hat Premier Certified Cloud & Service Provider. In our own self-assessment against the EU Cloud Sovereignty Framework, we scored SEAL-3 for digital resilience.

The specifics that bear on this article:

• Every service in the VSHN Application Catalog is upstream open source. PostgreSQL, MariaDB, Redis, Keycloak, GitLab, OpenBao, Forgejo. If you want to leave, you take your data to another operator running the same software. There is no proprietary format to convert and no control plane to rebuild.
• Automated encrypted off-site backups, with restores you can test. Off-site means a different infrastructure provider or your own hardware, outside the reach of the provider running the workload. Our backup operator K8up is open source and runs in your cluster. A backup you have never restored is a hypothesis.
• Infrastructure you choose. Cloudscale, Exoscale, or your own hardware, under Swiss law, operated by a Swiss team.
• Fixed monthly pricing per service. Not per user, not per gigabyte of AI training data we would like to store somewhere else.

We did not build it this way because sovereignty became fashionable in 2026. We built it this way because customers in banking, healthcare, and government could not sign anything else.

The point

The nonprofits in the Slate story were not careless. They were reasonable people who trusted a large, stable vendor with a thirteen-year-old program, kept their invoices, read their renewal confirmations, and lost everything anyway. The lesson is not that free things end. It is that a provider who can delete your data is a provider who decides whether you continue to exist.

Digital sovereignty is not a property of a data center. It is the state of having decided, consciously and yourself, who can reach your data and who can switch it off. If you cannot answer the five questions above about your own stack, that decision is currently being made by someone who does not work for you, which is the precise opposite of sovereignty.

VSHN automates the operation of open-source software on any cloud, for regulated Swiss organizations, since 2014. Book a consultation to review your exit path and backup strategy.

Sources:

• Over 170,000 Nonprofits Lost All Their Data. Is Microsoft to Blame? by Nitish Pahwa, Slate, August 18, 2026
• Changes to Microsoft 365 nonprofit grants by Microsoft, announced May 2025
• EUR 180 Million for Sovereign Cloud by VSHN, April 2026
• Open Source as State Policy by VSHN, June 2026