EU Commission’s Self-Hosted Teams Backup Draws Element Pro Usability Complaints

But the important distinction is easily lost beneath the colourful complaints: Teams remains the Commission’s main communications tool. POLITICO’s reporting describes Element Pro as a business-continuity backup, not a completed migration away from Microsoft.

That makes this less a story about Brussels replacing Teams than about whether a sovereign alternative can earn users’ confidence before an emergency demands it.

What officials are complaining about​

POLITICO reports that three officials questioned Element Pro’s usefulness or performance in internal staff discussions. One could not see its added value; another delivered the blunt verdict “absolute shit.” A third argued that its performance against Teams would leave the institution badly exposed in a hypothetical confrontation over access to U.S. technology.

Those reactions are evidence of dissatisfaction, but they are not a technical evaluation. The reporting does not identify specific call failures, message-delivery problems, affected devices, application versions or measured performance differences.

Nor do three anonymous comments establish how the Commission’s workforce as a whole views the system. The criticism deserves attention without being inflated into a finding that Element Pro has failed.

The hypothetical technology shutdown also needs careful handling. An official’s remark is not evidence that Microsoft or the U.S. government plans to disable the Commission’s services.

A backup, not a Teams eviction notice​

According to the internal memo described by POLITICO, Element Pro is intended to preserve Commission communications during disruption. Staff can use it for audio and video calls, file transfers, and project or conversation rooms resembling Teams chats and channels.

The Commission hosts the Element system on its own infrastructure, POLITICO reports. Its July staff memo framed the initiative around greater control over data and systems, reduced risk, and less disruption to work.

Element’s product documentation helps explain the architecture behind that choice. The platform uses the Matrix open standard for real-time communications, and Element Server Suite Pro provides a Matrix-based server platform that organisations can host. Matrix-based interoperability is distinct from reproducing the entire Microsoft 365 collaboration environment.

The practical interpretation is that the Commission is adding a separate communications route. The reporting does not establish that Element Pro replaces every Teams workflow, provides access to existing Teams conversations, or duplicates Microsoft 365 integrations.

A backup does not necessarily need every convenience of the primary system. It does need to perform its assigned job reliably—and users need to know what that job is.

What Element Pro adds for administrators​

Element describes Pro as its workplace client, included with Element Server Suite Pro subscriptions and designed for governments and public-sector organisations. That makes it more than a consumer messenger being pressed into office duty, although the vendor’s positioning is not an independent assessment of quality.

Its advertised administration capabilities include:

• Mobile-device-management support to connect employee apps to the organisation’s server.
• TLS certificate pinning to help ensure connections reach the intended server.
• Internal collection of analytics and user-submitted diagnostic reports.
• Organisation-wide room management with group and role-based access controls.
• Enhanced content scanning intended to support antivirus and data-loss protection.

These features provide concrete context for enterprise IT readers: the product offers controls aimed at managed workplace deployment. They do not establish which controls the Commission has enabled, how its deployment is configured, or whether those controls explain any staff complaints.

Self-hosting likewise answers only part of the sovereignty question. Knowing where the communications system runs does not, by itself, establish the independence of its identity services, endpoints, software supply chain or recovery arrangements.

Element’s response: adjustment takes time​

Element CEO Matthew Hodgson told POLITICO that the Commission was still trialling the software. He attributed some friction to early deployment issues and the difficulty of moving from a familiar application to one with different controls and layouts.

He also said Element was supporting the rollout and wanted both positive and negative feedback. POLITICO reports that the Commission did not immediately respond to its requests for comment.

That defence is plausible, but it remains the supplier’s explanation—not a diagnosis supported by published testing. Unfamiliar buttons can frustrate users; so can genuine defects. Without specific examples, neither explanation can settle the dispute.

The sensible conclusion is narrower: the rollout has generated complaints that deserve investigation, while the available evidence does not determine their cause.

Sovereignty is broader than the chat window​

The Commission’s wider policy provides useful context without proving that this particular deployment is successful. In its June 1, 2026 explanation of its Sovereign Cloud Framework, the Commission said it had awarded a €180 million sovereign-cloud procurement contract to four providers in April 2026. That is a separate procurement, not evidence of funding for Element Pro.

The same framework evaluates sovereignty using 48 criteria across eight categories, including legal and jurisdictional concerns, operational control, supply chains, technology, and security. It also distinguishes levels of data sovereignty, technological autonomy and full sovereignty.

That distinction matters. “Sovereign” is not a magic sticker that makes a system independent, secure and easy to use. The Commission’s own framework treats sovereignty as a collection of attributes rather than a single hosting decision.

The enterprise IT lesson: test the fallback as a fallback​

For Windows and Microsoft 365 administrators, the most useful takeaway is a testing principle, not a recommendation to abandon Teams.

As an operational assessment, a communications backup should be judged against an explicit continuity scenario. Questions worth putting into an acceptance test include:

1. Can staff find and open the approved client on managed PCs and mobile devices?
2. Can they sign in if the service affected by the incident is unavailable?
3. Can an incident team create a room, exchange files and establish a call?
4. Can users follow the procedure without receiving instructions through the failed primary platform?
5. Have administrators defined acceptable performance and rehearsed the process?

These are proposed evaluation questions, not findings about the Commission’s system.

The distinction between strategic control and everyday usability is the heart of this story. The Commission can have a legitimate reason to maintain an alternative while employees can have legitimate complaints about using it. Neither side’s objective cancels the other.

For now, the evidence supports a measured verdict: the Commission has introduced a self-hosted Teams backup, some officials are unimpressed, and its operational readiness remains unresolved by the published reporting. A lifeboat need not have the cruise ship’s amenities. It does, however, need to launch—and everyone should know how to get aboard.