On 7 October 2026, The Register reported that the Dutch tax office (Belastingdienst) is pulling back from Microsoft 365, Microsoft’s cloud office and email suite. In 2027, it’ll move email and calendars onto servers it owns or controls, according to the government’s letter to parliament. So is it dropping Microsoft? Not entirely. The hosting moves, and the plan reuses existing licences where possible, so Microsoft software likely stays in the mix. European open-source tools for files and collaboration come later, in late 2027 and 2028.
That split matters if you’re weighing cloud against on-prem for sensitive data. It’s a staged, partial reversal at government scale. No public total cost has been published. The letter says existing licences will be reused where possible, but the added infrastructure and running costs aren’t disclosed. There are no named server versions and no benchmarks either. Sources retrieved 7 October 2026.
What Happened
October 2025: Microsoft 365 is selected. The Belastingdienst, Customs (Douane), and the Benefits Service (Dienst Toeslagen) jointly chose Microsoft 365 as their new office workplace. NL Times reported on 2 October 2025 that the tax office would go ahead despite data privacy concerns.
February 2026: Alternatives get a cool reception. On 18 February 2026, Computable reported that the Belastingdienst was dismissive of Microsoft alternatives. Keep that in mind. It shows how far the position later moved.
10 July 2026: The rollout is paused. The planned deployment covered about 47,500 employees. It was paused so the authority could reassess an on-prem scenario and its backup plans. In June, the Dutch Advisory Council on ICT Assessment (Adviescollege ICT-Toetsing) had recommended rolling the cloud rollout back. The Register quotes the board as saying the public-cloud design “falls short on information security, information processing and future-proofing.”
About 5,000 employees had already moved before the pause.
6 October 2026: The revised plan. State Secretary Eelco Eerenberg set out the new direction in a letter to parliament (coverage: NU.nl/Tweakers; Neowin):
| Workload | Old plan | Revised plan | When |
|---|---|---|---|
| Email and calendar | Microsoft 365 cloud | On-premises, on servers the tax authority owns or controls | 2027 |
| Email client software | Microsoft (Outlook) | Reportedly still Microsoft, including Outlook; existing licences reused where possible | Ongoing |
| Personal file storage and collaboration | Microsoft 365 cloud | European open-source tools; no products named in the letter | Later in 2027 and 2028 |
| ~5,000 already-migrated users | Microsoft 365 cloud | Not addressed in the letter | Unclear |
| Core tax and collection systems | Belastingdienst’s own data centers in Apeldoorn | Unchanged. Outside the office-workplace program | n/a |
Two points get lost in the headlines.
Core tax systems weren’t part of this. A June 2026 letter to parliament says the primary-process applications for levying and collecting tax run in the Belastingdienst’s own data centers in Apeldoorn, and TaxLive reported in February that they would stay there. This decision covers office tools only: email, calendar, files, and collaboration.
It’s a hybrid move. Neowin says tools like Outlook will likely stay. What changes is the hosting: Microsoft’s cloud out, the tax authority’s own data center in. The letter names no server products or versions for the on-prem setup. Don’t assume a specific Exchange Server or SharePoint Server release until the government publishes details. It does flag one gap: some records-management tools in the Microsoft 365 package aren’t available on-prem.
The earlier exit plan is worth a look too. When the cloud rollout was still on, Computable reported that the documented exit strategy was a slimmed-down version of the authority’s existing on-prem HCL environment, with reduced functionality. That’s a fallback, not a replacement for Microsoft 365.
Microsoft’s integration documentation covers the general patterns for running Microsoft 365 next to on-prem Active Directory, Exchange, and SharePoint. Treat it as background on hybrid setups. It says nothing about the Belastingdienst’s own deployment.
How It Stacks Up
Who this affects
- Direct impact: About 47,500 staff across the Belastingdienst, Douane, and Dienst Toeslagen. The letter doesn’t say what happens to the ~5,000 already on Microsoft 365. Everyone else’s rollout gets redirected.
- Indirect impact: Every European public-sector IT team that has to defend a Microsoft 365 migration to an auditor. A national tax authority changed course mid-rollout. People will cite that.
- Not affected: The core tax and collection systems, which run in the authority’s own data centers.
The cost picture: one number, and it’s not the one you want
The only hard figure is €14.4 million. That’s what the authority had invested in the new office environment since 2021, as of February 2026 (Computable; TaxLive).
Be precise about what that number covers:
- It’s sunk cost on the workplace program so far.
- It leaves out the cost of the new on-prem plus open-source plan.
- It leaves out the cost of the reversal.
- It gives you no cloud vs. on-prem total cost of ownership comparison.
The letter gives no total cost for the revised plan. It says existing licences will be reused where possible to limit extra investment, and that added data-center capacity made the on-prem option possible. Any article that calls €14.4 million “the price of going back on-prem” is wrong.
Against the alternatives
How does this compare with other options? The record is thin:
| Option | Role in the Dutch plan | Published benchmark or cost data |
|---|---|---|
| Microsoft 365 (cloud) | Paused, except for ~5,000 existing users | €14.4M program spend since 2021 (whole program, not M365 licensing) |
| Microsoft client software (Outlook) on own infrastructure | Reportedly retained for email and calendar | None published; server versions unnamed |
| Nextcloud | Discussed in February 2026; not named in the October letter | None. Not judged equivalent to Microsoft 365 at the time |
| OpenDesk | Discussed in February 2026; not named in the October letter | None. Same caveat as Nextcloud |
| Legacy HCL environment | Exit strategy for the original cloud plan, reduced capability | None |
| Google Workspace | No evaluation found | None |
There’s no Google Workspace bake-off here, and no source names a virtualization or container stack.
Admin cost and migration effort
The timeline gives a few useful clues:
- Duration: The program started in 2021, and the new end state lands in 2027 to 2028. That’s a seven-year effort, with at least two more years of change ahead.
- Split estate: Some users sit on Microsoft 365 cloud. Most will be on self-hosted Microsoft email. File storage moves to open-source tools later. That’s three operating models running at once. Parallel identity, mail routing, and support are where on-prem admin cost piles up. In big shops it’s usually the hidden line item, and the government hasn’t published it.
- Readiness gap: The letter names no open-source products. When Nextcloud and OpenDesk came up in February, the authority didn’t judge them equal to Microsoft 365. A 2027 to 2028 target leaves little room to evaluate, buy, and migrate 47,500 seats.
The Reaction
Public reaction is still forming. Coverage such as Neowin’s stressed that Outlook likely stays, which is the right emphasis. In the Security.NL comment thread, early readers were largely positive; one opened with “Complimenten voor de Belastingdienst. Verstandig besluit.” (“Compliments to the tax office. Sensible decision.”)
The real debate started earlier. A r/thenetherlands thread on the July pause is where Dutch readers first caught the story.
The decision is smaller than the “ditches Microsoft” headlines suggest.
Our Take
Verdict: Hold on copying the Dutch move. Pilot the exit option.
The Belastingdienst reached a narrow conclusion. For a government body with sensitive data, who controls the infrastructure outweighs convenience. An independent ICT assessment board backed that call. It’s a governance finding with no technical benchmark behind it. There’s no published cost for the new plan and no named open-source products. So there’s no evidence base for anyone else to follow yet.
The lessons that do transfer:
- Decide where data lives before you migrate seats. The authority changed course after 5,000 of 47,500 users had moved. That left it with a split estate. Settle sovereignty questions at the design stage.
- Separate the hosting decision from the software decision. The Dutch changed the hosting and plan to reuse existing licences where they can. Most shops can make those calls one at a time.
- Keep a real exit plan. The cloud plan’s exit strategy was a reduced-capability legacy HCL environment. That beats nothing, but it’s thin. If your Microsoft 365 fallback is “we’d figure it out,” fix that first.
What it costs an IT shop: Copying this exact model means running Microsoft mail on your own hardware plus a separate open-source collaboration stack. You pay for servers, a UPS and storage at each site, patching, backups, and staff time for parallel systems. The Dutch haven’t shared their numbers, so nobody can give you the ratio.
A small pilot is the sensible middle ground, as long as you’re clear about what it tests. A Nextcloud instance on a spare mini PC can show how a handful of users’ file and sharing habits translate, and how cleanly data exports. It won’t tell you anything about identity integration, backup, security, availability, compliance, or support at scale. Test those separately before drawing conclusions.
Optional: a quick DNS check on your own mail routing
Before any sovereignty talk, it helps to know which of your domains route mail through Microsoft’s cloud. MX and Autodiscover DNS records give fast clues. Replace example.com with your domain.
Windows (PowerShell 5.1 or 7.x)
# MX record shows where inbound mail is delivered
Resolve-DnsName -Name example.com -Type MX
# Autodiscover CNAME shows where Outlook looks up mailbox settings
Resolve-DnsName -Name autodiscover.example.com -Type CNAMEA domain on Exchange Online usually returns something like this:
Name Type TTL Section NameExchange Preference
—- —- — ——- ———— ———-
example.com MX 3600 Answer example-com.mail.protection.outlook.com 0Name Type TTL Section NameHost
—- —- — ——- ——–
autodiscover.example.com CNAME 3600 Answer autodiscover.outlook.com
Linux (Ubuntu 24.04 / Debian 12)
# dig ships in the dnsutils package on Debian/Ubuntu
sudo apt install -y dnsutils
# +short prints only the answer section
dig +short MX example.com
dig +short CNAME autodiscover.example.comThe typical Exchange Online pattern looks like this:
0 example-com.mail.protection.outlook.com.
autodiscover.outlook.com.
An MX record pointing at mail.protection.outlook.com means inbound mail is routed through Microsoft’s cloud. An MX pointing at your own hostnames suggests on-prem mail or a third-party gateway. DNS only shows routing and discovery, though. A filtering gateway can hide the real mailbox host, and Autodiscover can also be set up through other mechanisms. Confirm where mailboxes actually live in your tenant and server configuration.
Wrapping Up
The Dutch tax office is moving email and calendars onto servers it controls in 2027, reusing existing licences where possible. European open-source storage and collaboration tools should follow in 2027 and 2028. The €14.4 million covers the old program’s spending through early 2026. Treat this as a strong governance signal, and wait for published costs and named open-source products before calling it a blueprint.
| Step | Action | Applies To |
|---|---|---|
| 1 | Map which workloads hold sensitive data before migrating seats | Any Microsoft 365 rollout |
| 2 | Check MX and Autodiscover records to see where mail is hosted | Windows and Linux admins |
| 3 | Document a real exit plan that goes beyond a degraded legacy fallback | Regulated and public-sector orgs |
| 4 | Run a small workflow and data-portability pilot before committing to an alternative | IT teams evaluating alternatives |
| 5 | Wait for published costs before quoting the Dutch case in a budget | IT decision makers |