For Windows and Microsoft 365 administrators, the lesson is about coexistence. Sovereign messaging is arriving as a complement to Teams, not as a drop-in replacement.
What Matrix is, in admin terms
Matrix launched in 2014 as an open messaging standard for decentralized communications. Like email, it lets users send messages between compatible apps from different vendors, including Element, Rocket.Chat and Automattic's Beeper.
Think of it as SMTP for chat. Organizations can pick different clients, hosting arrangements and vendors, and the protocol connects them.
Matthew Hodgson is a Matrix Foundation co-founder and the CEO of Element. Computerworld quotes him saying 65 "national- and international-scale" Matrix deployments are being tracked in Europe. That figure comes from a vendor-aligned source, so read it as an ecosystem count rather than an audited market share.
The headline event: a five-party federation demo
Computerworld reports that Kenneth Edwall took part in a live federation demo during the conference. He is an IT architect at Försäkringskassan, the Swedish Social Insurance Agency. The demo connected Matrix applications at the European Commission, France's DINUM, Försäkringskassan, NATO, and the authority for Germany's state of Schleswig-Holstein.
Computerworld describes it as a proof of concept. It was not a production cross-border government network.
Element is a Matrix vendor and a conference sponsor, and it published its own account of the demo. Its account is useful for technical detail, but it is vendor reporting. It says:
- The five organizations ran separate deployments and apps. These included DINUM's Tchap, built on community Synapse, and NATO's setup, which used FluffyChat and ESS Pro in the demo environment.
- The demo ran in environments hosted on the same infrastructure as the participants' actual deployments.
- The configurations varied widely. Element's table lists the Commission, NATO and Schleswig-Holstein as running ESS Pro with open network filtering and no extra enterprise control. It lists Försäkringskassan as ESS Classic with IP-based filtering plus geo-blocking, accessible only to MDM-enrolled devices, with file transfer blocked.
That last detail matters to Intune and endpoint admins. One participant tied access to managed devices, and another left its deployment open. Federation joins the servers, but it does not make their security postures equal.
Federation does not mean open to everyone
Element says that in government use, federation does not mean open to everyone. Deployments typically run as private or closed federations, where only explicitly approved servers can connect and nothing is exposed to the public Matrix network. This is Element's description of a typical model. It is not proof that the Malmö demo was a governed production federation.
Edwall's own caveat points the same way. He said the demo was technically realistic, noting it is "only a few firewalls away to France and Germany." The harder questions are governance ones. As Computerworld reports it, they are who should interoperate, how open the network should be, and who is allowed in.
The Commission: evaluating, not committing
The Commission's position is where the story is easiest to overstate. Computerworld reports that the Commission is assessing the technical feasibility of federation across EU institutions and member states, and that no decision has been made. Diana Gheorghe is head of sector for Communication and Collaboration Services in the Commission's Digital Workplace Foundations team. She called federation "an unwritten story" and said there is no firm decision, with security and regulations such as GDPR among the considerations.
The Commission's Element rollout itself is further along. Computerworld's coverage says the Commission recently rolled out Element's Matrix-based application, with the eventual goal of enabling secure internal communications for more than 40,000 employees. It also says the project began in summer 2025, with a proof of concept completed in December.
Gheorghe's stated aims were resilience, business continuity, data control and ownership of the platform. She also named "contractual leverage" in procurement. That last point is easy to overlook in sovereignty debates.
Computerworld reports several practical problems:
- Users had difficulty finding colleagues across different servers.
- The Commission disabled the live presence feature after performance problems.
- Element will "complement" existing workplace apps, not replace Teams at this stage.
- Gheorghe warned there is "no one-to-one parity" with Teams, which sits on a broader platform.
- Computerworld notes a recent Politico article on Commission staff reaction, which it says compared the Element rollout unfavorably with Teams.
This fits earlier reporting by Euractiv. A Commission spokesperson described Matrix as a "complement and backup solution" to existing internal communications software, and Euractiv concluded there were no plans to replace Teams. Treat that as background. It is not a statement of the Commission's current position.
Sweden: the more concrete federation story
Sweden has the more tangible federation result. Computerworld reports that Försäkringskassan belongs to eSam, a program that supports digital transformation across 42 Swedish agencies. Its Matrix-based SAFOS Chatt service is used by 19 Swedish public authorities.
eSam's own announcement is the stronger primary source here. It reported on 22 May 2026 that federation between Försäkringskassan's Element-based chat and Trafikverket's Rocket.Chat had started. Users at the two agencies can chat directly despite using different tools. eSam said it planned to expand the pilot after summer 2026 and that participants need a Matrix-capable solution. It named Rocket.Chat, Element and Mattermost as examples.
Computerworld adds that the proof of concept met most of its requirements, although some capabilities still need improvement. eSam will publish a final report in spring 2027.
Why Sweden turned to federation
Edwall's account of the background will sound familiar to anyone who lived through the Skype for Business sunset:
- Five years ago, most eSam members used Skype for Business, so staff at different agencies could talk to each other.
- As Microsoft prepared to end support for older versions, agencies moved to a range of different apps, and cross-agency communication broke.
- Today there are three broad approaches. Many larger agencies run Teams alongside a separate platform for sensitive information. Others have chosen sovereign systems instead of public cloud. Relying entirely on public cloud such as Teams or Zoom is less common.
- Without interoperability, staff may need guest accounts on other agencies' platforms. That creates the offboarding and access-governance problems any identity administrator will recognize.
Edwall was blunt about priorities. The goal, he said, is sovereignty, not matching Teams feature for feature: "we can live with not having the latest, coolest feature."
Teams bridges are limited
Computerworld notes that bridges between some Matrix apps and Teams or Slack are possible, but access to certain features is limited. It also reports that Element no longer offers its Teams and Slack bridges to new customers. Anyone planning a mixed estate should not assume a bridge will cover day-to-day needs.
Why replacing Teams is the harder problem
Forrester's Maisto expects more adoption of open-source sovereign tools, as primary or backup platforms, but warns that "This is not a shift that will happen overnight." His reasoning, as Computerworld reports it, includes:
- Sunk cost. Many organizations moved heavily to cloud communications during the pandemic, and some projects are still running. He said an organization still amortizing that spend is unlikely to start a €10 million project.
- Resources. Not every organization can develop missing features or maintain open-source software.
- Ecosystem gravity. If Microsoft's productivity suite handles everything else, a sovereign chat tool alone does little for overall sovereignty.
- A realistic path. He sketched a progression from proof of concept to production alongside proprietary tools, and only later possibly to full migration.
He also called business continuity a sensible starting point, with a caveat: starting there may surface much more to consider.
What IT teams can take from this
This is analysis, not a procedure drawn from the sources. A few practical points follow from the reporting:
- Treat Matrix as a resilience layer first. The Commission and many Swedish agencies use it alongside Teams, not instead of it.
- Settle governance before technology. Decide which counterparties you trust, what content may cross the boundary, and who owns audit logs.
- Expect uneven security postures. The demo shows how different federated partners can be. Device-management requirements, file-transfer rules and network filtering can all vary between partners.
- Budget for feature gaps. Presence, user discovery and parity with Teams' broader collaboration features all came up as friction points.
- Plan for the whole stack. Chat is one piece of a sovereignty strategy that also includes identity, documents and email.
Bottom line
The reporting supports four points:
- A live five-party Matrix federation demo took place.
- Sweden has a real two-agency federation, with a final report due in spring 2027.
- The Commission is assessing federation and has made no decision.
- Analysts expect gradual change, not a Teams exodus.
Matrix is clearly establishing itself as an interoperable, sovereign messaging layer for European public bodies. For Microsoft shops, the near-term picture is a mixed estate in which Teams stays and Matrix fills specific gaps.
References
- Matrix gains ground in Europe’s public sector — but replacing Teams is another matter - Computerworld Computerworld · 2026-10-23T11:57:32+00:00
- “Matrix, come here.” The world’s first cross-border government federation demo element.io
- Sweden goes live with Matrix-based federation! element.io