Dutch university staff will begin testing SURF’s Nextcloud-based “SURF Works” environment in July 2026 as a limited pilot for about 100 participants, offering an open-source alternative to parts of Microsoft 365, including Teams-like collaboration, files, office documents, and shared workspaces. The experiment is small, but the politics around it are not. Europe’s long-running argument over digital sovereignty has moved from speeches and procurement papers into the daily muscle memory of office work.
The most important thing about the Erasmus University pilot is not that it will replace Microsoft Teams next month. It will not. The important thing is that a mainstream university is testing whether the Microsoft 365 stack can be unbundled in practice.
That distinction matters because Microsoft’s grip on institutions is rarely maintained by one killer feature. It is maintained by the compound convenience of Outlook, Teams, SharePoint, OneDrive, Word, Excel, PowerPoint, Entra ID, and the administrative machinery around them. Once a university starts asking whether parts of that stack can be swapped out, the question stops being ideological and becomes operational.
SURF, the Dutch cooperative IT organization for education and research, is therefore running more than a software trial. It is staging a controlled confrontation between two models of institutional computing. One model says the safest path is to buy the integrated platform from a hyperscale vendor and accept the jurisdictional, contractual, and dependency trade-offs. The other says public institutions should retain more control over hosting, code, data location, and procurement leverage, even if that means more complexity.
Erasmus University’s version of the pilot is scheduled to run for a year from July, with room for roughly 100 participants. Other Dutch institutions have described related SURF Works activity running through 2026, which suggests this is not an isolated campus experiment but part of a broader national probe into whether open-source collaboration software can survive contact with enterprise reality.
That is where sovereignty becomes difficult. It is easy to say that public-sector data should be under European control. It is harder to recreate the collaborative convenience that made Microsoft 365 so sticky in the first place.
Modern office work is not just file storage. It is presence indicators, shared calendars, meeting links, comments in documents, permissions that follow organizational charts, mobile notifications, search, retention policies, guest access, and the informal expectation that “everyone already has it.” A serious alternative has to compete not with Word as a standalone word processor, but with an ecosystem that has spent years compressing collaboration into a few reflexive clicks.
Nextcloud is one of the few open-source platforms with a plausible answer to that challenge. Nextcloud Hub brings together file sync, document collaboration, chat, video calling, groupware, office editing, workflows, and integrations. It can be self-hosted or hosted by a trusted provider, and its open-source nature lets institutions inspect, modify, and contribute to the software rather than simply consume it.
That does not make it a drop-in Microsoft 365 clone. In fact, pretending it is one would be the fastest way to kill the pilot. The better framing is that SURF and participating universities are testing whether they can redesign collaboration around controlled infrastructure rather than imported convenience.
The issue is not that every Teams chat is about to be vacuumed up by Washington. Serious risk analysis should avoid melodrama. The problem is that public universities, hospitals, ministries, and research bodies increasingly have to explain why core institutional communications are dependent on foreign hyperscalers subject to foreign legal orders.
Microsoft has spent years trying to answer that concern with data boundary commitments, European cloud programs, contractual safeguards, and compliance tooling. Those measures are not meaningless. Large customers have real audit requirements, and Microsoft’s enterprise compliance machine exists because governments and regulated industries demand it.
But the SURF pilot points at a more stubborn problem: hosting and software are bundled. As Mira Bückmann of Erasmus University put it in the university’s own account, institutions cannot simply ask Microsoft for the Microsoft 365 software and install it themselves on their own infrastructure. Microsoft 365 is a service, and the service model gives Microsoft both technical control and strategic leverage.
Nextcloud changes that equation because it separates software from the place where it runs. If SURF hosts the environment on Dutch infrastructure for Dutch education and research, the institutional risk profile changes. The point is not that open source magically eliminates legal risk; it is that it gives universities more architectural choices than “accept the vendor’s cloud or leave.”
Instead, SURF is offering a managed environment based on Nextcloud for education and research. That distinction is crucial. Most users do not care whether a tool is open source; they care whether it works, whether their colleagues are there, and whether it makes their workday easier or harder. Most IT departments do not want ideological purity if it means multiplying support tickets.
The promise of a SURF-hosted Nextcloud environment is that institutions may be able to get some of the operational benefits of a cloud service while retaining more public-sector control over governance, hosting, and development priorities. That is the sweet spot European governments and universities keep circling: not “everyone becomes their own cloud provider,” but “critical public collaboration infrastructure should not be wholly dependent on a handful of US platforms.”
Nextcloud itself is well positioned for that argument because it is not merely a file sync product anymore. Nextcloud Hub includes Files, Talk, Groupware, Office, and workflow components. It can connect to existing storage and identity systems, and it has accumulated enough enterprise features to be considered seriously by organizations that would never adopt a hobbyist tool for core collaboration.
Still, credibility is not the same as inevitability. The hardest part for Nextcloud is not demonstrating that it has a feature list. The hardest part is proving that its features work together under the social pressure of real institutional collaboration.
A Teams replacement without calendar integration is not really competing with Teams yet. It is competing with the idea of Teams. In most organizations, the meeting invite is the starting point for the collaboration object: it creates the room, the attendee list, the recurrence, the notes, the chat, the files, and often the post-meeting follow-up. If that object still originates in Outlook, Microsoft remains the default coordination layer.
This is why the pilot’s recommendation that participants join in groups of close colleagues is more than practical advice. It is an admission that collaboration tools only become useful when a working unit adopts them together. A lone user in an alternative suite is not sovereign; they are isolated.
The Outlook gap also illustrates why Big Tech displacement happens unevenly. File sharing may move first. Shared document editing may follow for some workflows. Team chat and video may work in defined groups. But email, calendar, directory integration, and identity are harder because they sit at the boundary between every workflow and every user.
If SURF can close that gap during the pilot, the trial becomes much more interesting. If it cannot, the experiment may still produce useful knowledge, but it will remain a partial alternative rather than a credible daily workspace for most staff.
That convenience is expensive in the long run. It centralizes dependency, makes price increases harder to resist, and turns technical roadmap decisions into vendor roadmap decisions. But it is still convenience, and any alternative has to beat or justify the loss of it.
For universities, the trade-off is especially sharp. Academic institutions contain many different kinds of work under one brand: teaching, research, HR, finance, student services, international collaboration, legal records, grant administration, and sensitive personal data. A tool that works beautifully for a research group may not satisfy the needs of central administration. A tool that satisfies compliance may feel clumsy to students and lecturers.
Microsoft’s advantage is that it already sits across those boundaries. Teams may be unloved in plenty of offices, but it is present. Outlook may be overburdened, but it is canonical. SharePoint may confuse users, but it is integrated into permissions and retention structures. Inertia is not laziness; it is the accumulated cost of coordinating thousands of people.
That is why pilots matter. They let institutions find the workloads where the alternative is not merely morally preferable but practically good enough. The first victories are likely to be bounded: research projects, working groups, committees, departments with strong data sovereignty requirements, or teams that already prefer open-source workflows. The grand migration, if it ever comes, will be built from those smaller proofs.
A sovereign Microsoft alternative may not be a single monolithic replacement. It may be a federation of services: Nextcloud Hub for collaboration, SURF Drive for personal and departmental storage, Research Drive for large research datasets, existing identity systems for authentication, and Outlook until mail and calendaring are integrated. That architecture is messier than Microsoft 365, but it may also be more controllable.
The open question is whether users experience that federation as flexibility or fragmentation. IT architects may appreciate modularity. Ordinary staff may see only that their files are in one place, meetings in another, chat in another, and calendar in Microsoft anyway.
The success of SURF Works will therefore depend heavily on product integration, onboarding, and support. If the environment feels like a coherent workspace, the sovereignty argument gains practical force. If it feels like a politically worthy maze, Microsoft wins by default.
This is where European open-source projects often stumble. They can match capability on paper but underinvest in the boring connective tissue: migration tools, mobile polish, single sign-on reliability, documentation, training, search, and support escalation. Microsoft’s software is not always elegant, but its ecosystem is relentlessly integrated. To compete, alternatives need not mimic every feature, but they must reduce the number of times users have to think about the tool.
That makes them frustrating customers, but useful ones. A university pilot will expose weaknesses that a more homogeneous organization might hide. Researchers will test external sharing. Lecturers will test real-time collaboration. Administrative teams will test calendar and document workflows. IT staff will test identity, provisioning, auditability, backup, retention, and support burden.
Dutch higher education is an especially interesting arena because SURF already provides shared infrastructure and services for the sector. That gives the pilot a governance structure that many countries lack. A single university trying to leave Microsoft is one customer with limited leverage. A national research and education IT cooperative can aggregate demand, coordinate requirements, and participate in upstream open-source development.
That last point is easy to underestimate. The best version of this model is not simply “Europe buys European software.” It is that public-sector users help shape software that they can inspect, influence, and reuse. If SURF’s participation feeds improvements back into Nextcloud and related projects, the pilot becomes part of a broader commons rather than a bespoke procurement workaround.
A Nextcloud pilot does not change that overnight. Even if it succeeds, Microsoft will remain deeply embedded in university infrastructure. Outlook is still present. Office file formats remain the lingua franca of documents. Windows endpoints are still everywhere. Entra ID, Intune, Defender, Power Platform, and Azure services may sit beneath the visible productivity layer.
That reality should not be read as defeat. It should be read as a warning against theatrical migration promises. The credible path away from Big Tech is not a single leap; it is the gradual recovery of optionality.
Optionality is valuable even when institutions do not fully exercise it. If universities can credibly move some workflows to open platforms, they gain leverage in vendor negotiations. If they can host sensitive collaboration outside US cloud platforms, they reduce legal exposure. If they can fund improvements in open-source alternatives, they help create a market where future procurement choices are less binary.
The strategic win is not “delete Microsoft.” The strategic win is “Microsoft is no longer the only realistic answer.”
The concrete stakes are already visible.
The Microsoft Exit Starts With a Pilot, Not a Press Conference
The most important thing about the Erasmus University pilot is not that it will replace Microsoft Teams next month. It will not. The important thing is that a mainstream university is testing whether the Microsoft 365 stack can be unbundled in practice.That distinction matters because Microsoft’s grip on institutions is rarely maintained by one killer feature. It is maintained by the compound convenience of Outlook, Teams, SharePoint, OneDrive, Word, Excel, PowerPoint, Entra ID, and the administrative machinery around them. Once a university starts asking whether parts of that stack can be swapped out, the question stops being ideological and becomes operational.
SURF, the Dutch cooperative IT organization for education and research, is therefore running more than a software trial. It is staging a controlled confrontation between two models of institutional computing. One model says the safest path is to buy the integrated platform from a hyperscale vendor and accept the jurisdictional, contractual, and dependency trade-offs. The other says public institutions should retain more control over hosting, code, data location, and procurement leverage, even if that means more complexity.
Erasmus University’s version of the pilot is scheduled to run for a year from July, with room for roughly 100 participants. Other Dutch institutions have described related SURF Works activity running through 2026, which suggests this is not an isolated campus experiment but part of a broader national probe into whether open-source collaboration software can survive contact with enterprise reality.
Europe’s Sovereignty Debate Has Reached the Calendar Invite
For years, “digital sovereignty” sounded like a Brussels phrase in search of a helpdesk ticket. It meant different things depending on who used it: data residency, open standards, European suppliers, reduced US cloud exposure, or simply frustration with procurement lock-in. The Teams alternative pilot gives the phrase a more concrete shape: can a lecturer, researcher, administrator, or project team do everyday work without defaulting to Microsoft?That is where sovereignty becomes difficult. It is easy to say that public-sector data should be under European control. It is harder to recreate the collaborative convenience that made Microsoft 365 so sticky in the first place.
Modern office work is not just file storage. It is presence indicators, shared calendars, meeting links, comments in documents, permissions that follow organizational charts, mobile notifications, search, retention policies, guest access, and the informal expectation that “everyone already has it.” A serious alternative has to compete not with Word as a standalone word processor, but with an ecosystem that has spent years compressing collaboration into a few reflexive clicks.
Nextcloud is one of the few open-source platforms with a plausible answer to that challenge. Nextcloud Hub brings together file sync, document collaboration, chat, video calling, groupware, office editing, workflows, and integrations. It can be self-hosted or hosted by a trusted provider, and its open-source nature lets institutions inspect, modify, and contribute to the software rather than simply consume it.
That does not make it a drop-in Microsoft 365 clone. In fact, pretending it is one would be the fastest way to kill the pilot. The better framing is that SURF and participating universities are testing whether they can redesign collaboration around controlled infrastructure rather than imported convenience.
The CLOUD Act Is the Spark, but Lock-In Is the Fuel
The Erasmus report foregrounds a familiar concern: Microsoft is an American company, and Microsoft 365 data is therefore entangled with US law, including the CLOUD Act. The law allows US authorities, under certain conditions and legal processes, to seek data from US-based service providers even when that data concerns foreign customers. For European public institutions, that has become a recurring source of legal and political discomfort.The issue is not that every Teams chat is about to be vacuumed up by Washington. Serious risk analysis should avoid melodrama. The problem is that public universities, hospitals, ministries, and research bodies increasingly have to explain why core institutional communications are dependent on foreign hyperscalers subject to foreign legal orders.
Microsoft has spent years trying to answer that concern with data boundary commitments, European cloud programs, contractual safeguards, and compliance tooling. Those measures are not meaningless. Large customers have real audit requirements, and Microsoft’s enterprise compliance machine exists because governments and regulated industries demand it.
But the SURF pilot points at a more stubborn problem: hosting and software are bundled. As Mira Bückmann of Erasmus University put it in the university’s own account, institutions cannot simply ask Microsoft for the Microsoft 365 software and install it themselves on their own infrastructure. Microsoft 365 is a service, and the service model gives Microsoft both technical control and strategic leverage.
Nextcloud changes that equation because it separates software from the place where it runs. If SURF hosts the environment on Dutch infrastructure for Dutch education and research, the institutional risk profile changes. The point is not that open source magically eliminates legal risk; it is that it gives universities more architectural choices than “accept the vendor’s cloud or leave.”
Nextcloud’s Best Argument Is Control, Not Nostalgia
Open-source advocates sometimes weaken their own case by sounding as if the goal is to return to a pre-cloud age of local servers, heroic sysadmins, and manually patched collaboration stacks. That is not what the Dutch pilot appears to be testing. The project is not asking every department to run its own mail server under a desk.Instead, SURF is offering a managed environment based on Nextcloud for education and research. That distinction is crucial. Most users do not care whether a tool is open source; they care whether it works, whether their colleagues are there, and whether it makes their workday easier or harder. Most IT departments do not want ideological purity if it means multiplying support tickets.
The promise of a SURF-hosted Nextcloud environment is that institutions may be able to get some of the operational benefits of a cloud service while retaining more public-sector control over governance, hosting, and development priorities. That is the sweet spot European governments and universities keep circling: not “everyone becomes their own cloud provider,” but “critical public collaboration infrastructure should not be wholly dependent on a handful of US platforms.”
Nextcloud itself is well positioned for that argument because it is not merely a file sync product anymore. Nextcloud Hub includes Files, Talk, Groupware, Office, and workflow components. It can connect to existing storage and identity systems, and it has accumulated enough enterprise features to be considered seriously by organizations that would never adopt a hobbyist tool for core collaboration.
Still, credibility is not the same as inevitability. The hardest part for Nextcloud is not demonstrating that it has a feature list. The hardest part is proving that its features work together under the social pressure of real institutional collaboration.
The Missing Outlook Link Is Not a Footnote
The Erasmus pilot has one obvious limitation at launch: email and calendar integration are not fully in place. Participants who want to invite colleagues still need to use Outlook, with the missing link expected later during the pilot period. That sounds like a manageable gap until one remembers that calendars are the circulatory system of office life.A Teams replacement without calendar integration is not really competing with Teams yet. It is competing with the idea of Teams. In most organizations, the meeting invite is the starting point for the collaboration object: it creates the room, the attendee list, the recurrence, the notes, the chat, the files, and often the post-meeting follow-up. If that object still originates in Outlook, Microsoft remains the default coordination layer.
This is why the pilot’s recommendation that participants join in groups of close colleagues is more than practical advice. It is an admission that collaboration tools only become useful when a working unit adopts them together. A lone user in an alternative suite is not sovereign; they are isolated.
The Outlook gap also illustrates why Big Tech displacement happens unevenly. File sharing may move first. Shared document editing may follow for some workflows. Team chat and video may work in defined groups. But email, calendar, directory integration, and identity are harder because they sit at the boundary between every workflow and every user.
If SURF can close that gap during the pilot, the trial becomes much more interesting. If it cannot, the experiment may still produce useful knowledge, but it will remain a partial alternative rather than a credible daily workspace for most staff.
Microsoft’s Real Moat Is Habit at Institutional Scale
Microsoft 365 is often criticized as if institutions buy it only because procurement departments have been hypnotized by Redmond. That misses the stronger explanation: Microsoft has made itself administratively convenient. It gives large organizations one vendor, one licensing framework, one identity model, one compliance surface, and one familiar set of applications that users already know, or at least tolerate.That convenience is expensive in the long run. It centralizes dependency, makes price increases harder to resist, and turns technical roadmap decisions into vendor roadmap decisions. But it is still convenience, and any alternative has to beat or justify the loss of it.
For universities, the trade-off is especially sharp. Academic institutions contain many different kinds of work under one brand: teaching, research, HR, finance, student services, international collaboration, legal records, grant administration, and sensitive personal data. A tool that works beautifully for a research group may not satisfy the needs of central administration. A tool that satisfies compliance may feel clumsy to students and lecturers.
Microsoft’s advantage is that it already sits across those boundaries. Teams may be unloved in plenty of offices, but it is present. Outlook may be overburdened, but it is canonical. SharePoint may confuse users, but it is integrated into permissions and retention structures. Inertia is not laziness; it is the accumulated cost of coordinating thousands of people.
That is why pilots matter. They let institutions find the workloads where the alternative is not merely morally preferable but practically good enough. The first victories are likely to be bounded: research projects, working groups, committees, departments with strong data sovereignty requirements, or teams that already prefer open-source workflows. The grand migration, if it ever comes, will be built from those smaller proofs.
The Storage Limitation Reveals the Architecture Behind the Politics
The pilot’s storage space is limited, so Erasmus participants are not being invited to dump their entire document history into Nextcloud Hub. SURF’s recommendation is to use SURF Drive or Research Drive for heavier document management, with staff storage reaching one terabyte in SURF Drive and more capacity available through Research Drive. That may sound like a technical caveat, but it reveals the more realistic architecture of the project.A sovereign Microsoft alternative may not be a single monolithic replacement. It may be a federation of services: Nextcloud Hub for collaboration, SURF Drive for personal and departmental storage, Research Drive for large research datasets, existing identity systems for authentication, and Outlook until mail and calendaring are integrated. That architecture is messier than Microsoft 365, but it may also be more controllable.
The open question is whether users experience that federation as flexibility or fragmentation. IT architects may appreciate modularity. Ordinary staff may see only that their files are in one place, meetings in another, chat in another, and calendar in Microsoft anyway.
The success of SURF Works will therefore depend heavily on product integration, onboarding, and support. If the environment feels like a coherent workspace, the sovereignty argument gains practical force. If it feels like a politically worthy maze, Microsoft wins by default.
This is where European open-source projects often stumble. They can match capability on paper but underinvest in the boring connective tissue: migration tools, mobile polish, single sign-on reliability, documentation, training, search, and support escalation. Microsoft’s software is not always elegant, but its ecosystem is relentlessly integrated. To compete, alternatives need not mimic every feature, but they must reduce the number of times users have to think about the tool.
Universities Are the Right Test Bed Because They Are Difficult Customers
If an open-source collaboration platform can work in higher education, it has a better chance elsewhere. Universities are decentralized, politically aware, internationally connected, and full of users who resist top-down IT mandates. They are also legally sensitive environments that handle personal data, research data, intellectual property, and cross-border partnerships.That makes them frustrating customers, but useful ones. A university pilot will expose weaknesses that a more homogeneous organization might hide. Researchers will test external sharing. Lecturers will test real-time collaboration. Administrative teams will test calendar and document workflows. IT staff will test identity, provisioning, auditability, backup, retention, and support burden.
Dutch higher education is an especially interesting arena because SURF already provides shared infrastructure and services for the sector. That gives the pilot a governance structure that many countries lack. A single university trying to leave Microsoft is one customer with limited leverage. A national research and education IT cooperative can aggregate demand, coordinate requirements, and participate in upstream open-source development.
That last point is easy to underestimate. The best version of this model is not simply “Europe buys European software.” It is that public-sector users help shape software that they can inspect, influence, and reuse. If SURF’s participation feeds improvements back into Nextcloud and related projects, the pilot becomes part of a broader commons rather than a bespoke procurement workaround.
Big Tech Will Not Be Displaced by Moral Victory
There is a temptation in European tech policy to treat dependency on US platforms as a problem that can be solved by naming it. But dependency is not a slogan; it is an operating model. Microsoft, Google, Amazon, Apple, and other platform companies dominate because they combine technical capability with procurement reach, developer ecosystems, security programs, and relentless commercial execution.A Nextcloud pilot does not change that overnight. Even if it succeeds, Microsoft will remain deeply embedded in university infrastructure. Outlook is still present. Office file formats remain the lingua franca of documents. Windows endpoints are still everywhere. Entra ID, Intune, Defender, Power Platform, and Azure services may sit beneath the visible productivity layer.
That reality should not be read as defeat. It should be read as a warning against theatrical migration promises. The credible path away from Big Tech is not a single leap; it is the gradual recovery of optionality.
Optionality is valuable even when institutions do not fully exercise it. If universities can credibly move some workflows to open platforms, they gain leverage in vendor negotiations. If they can host sensitive collaboration outside US cloud platforms, they reduce legal exposure. If they can fund improvements in open-source alternatives, they help create a market where future procurement choices are less binary.
The strategic win is not “delete Microsoft.” The strategic win is “Microsoft is no longer the only realistic answer.”
The July Pilot Turns Sovereignty Into a Support Ticket
The SURF Works trial will be judged less by ideology than by daily annoyances. If participants can create a shared document, discuss it, meet around it, find it later, and bring colleagues into the workflow without friction, the pilot will feel serious. If they keep falling back to Outlook and Teams, it will become another worthy experiment that proves how hard the problem is.The concrete stakes are already visible.
- The pilot gives Dutch university staff a controlled way to test Nextcloud Hub as an alternative to parts of Microsoft 365 during 2026.
- The project is explicitly tied to reducing dependency on large US technology vendors and the legal exposure that comes with foreign cloud services.
- The initial lack of full email and calendar integration means Outlook remains a practical dependency at launch.
- The storage limits mean participants will need to combine Nextcloud Hub with SURF Drive or Research Drive rather than treating it as a one-stop replacement.
- The recommendation to join in groups is a recognition that collaboration software succeeds at the team level, not the individual level.
- The most important outcome may be institutional leverage and architectural choice, even if Microsoft 365 remains widely used.
References
- Primary source: Erasmus Magazine
Published: 2026-06-17T08:42:10.371660
Loading…
www.erasmusmagazine.nl - Related coverage: ru.nl
Loading…
www.ru.nl - Related coverage: surf.nl
Loading…
www.surf.nl - Official source: marketplace.microsoft.com
Loading…
marketplace.microsoft.com - Related coverage: windowscentral.com
EuroOffice emerges as Europe’s sovereignty‑focused alternative to Microsoft 365
Europe’s biggest tech players debut EuroOffice, a sovereign suite designed to challenge Microsoft 365’s dominance.
www.windowscentral.com