Summary Under the proposed Cloud and AI Development Act (CADA), joining the EuroCloud Federation is a voluntary process for Union entities and public sector bodies. There is no automatic enrollment. To join, an eligible entity must submit a formal request to the European Commission. The specific procedural steps and the exact content of the application will be defined by the Commission through implementing acts, which will also provide a standardized request template. These acts will be adopted via the examination procedure under Article 46(2), ensuring Member State oversight before the rules are finalized.

Detail

The EuroCloud Federation represents a significant shift in how the EU public sector manages cloud infrastructure, moving from isolated national silos to a federated model for sharing capacity. As proposed in COM(2026) 502 final, the legal mechanics for accession are strictly defined in Article 34 of the draft Regulation. Understanding these mechanics is essential for public procurement officers and IT directors planning future infrastructure strategies.

The Voluntary Nature of Accession

The foundational principle of the Federation is that participation is not mandatory. Article 34(1) explicitly establishes the Federation as open for participation "on a voluntary basis." The text states: "Union entities and public sector bodies may request the Commission to join the EuroCloud Federation."

This phrasing is critical. It confirms that:

  1. No Automatic Membership: Upon the Regulation's entry into force, no entity becomes a member by default.
  2. Active Request Required: Eligible bodies must take the initiative to apply.
  3. Commission as Gatekeeper: The request is not submitted to a peer body or a national authority; it is directed specifically to the European Commission.

This voluntary framework respects the principle of subsidiarity, allowing Member States and Union entities to assess their own readiness and strategic needs before committing to the shared infrastructure.

The Application Procedure: Defining the Mechanics

While Article 34(1) grants the right to request membership, it deliberately leaves the administrative details to secondary legislation. The primary text does not specify whether the application is digital, paper-based, or what specific data fields are required.

Article 34(4) addresses this by empowering the Commission to adopt implementing acts to flesh out the process. These acts will specify two key elements:

  1. The Procedure: The exact steps an entity must follow to participate, including submission channels, review timelines, and decision-making workflows.
  2. The Template: A standardized template concerning the "content and other details of the request for participation."

This delegation ensures that the application process can be adapted to technical realities and administrative best practices without requiring a full revision of the Regulation. Until these implementing acts are adopted, the precise administrative pathway remains undefined. However, the legal requirement for a template implies a standardized, harmonized application process across all Member States to ensure fairness and comparability.

The Examination Procedure: Member State Oversight

The adoption of these implementing acts is not a unilateral Commission decision. Article 34(4) mandates that the acts be adopted "in accordance with the examination procedure referred to in Article 46(2)."

This procedure involves a committee composed of representatives from all Member States. Before the Commission can finalize the rules for joining the Federation, this committee must review and approve the draft acts. This ensures that:

  • National Interests are Protected: Member States have a direct say in the criteria and process for joining a pan-European infrastructure.
  • Legal Certainty: The rules are vetted by national experts before becoming binding, reducing the risk of procedural errors or legal challenges later.
  • Transparency: The committee process provides a formal channel for Member States to raise concerns or suggest improvements to the application template.

Scope and Purpose of the Federation

Understanding the application process requires context on what is being joined. Article 34(2) clarifies that the Federation's purpose is to "facilitate the sharing of public sector data centre services and cloud computing services between Union entities and public sector bodies under the conditions set out in Articles 35 and 36."

Therefore, the request to join is effectively an application to participate in a resource-sharing mechanism. Once a member, an entity can act as a "sharing entity" (providing idle capacity) or a "using entity" (consuming capacity). Article 34(3) further mandates the Commission to establish a platform for the Federation, including a catalogue of available services and a service platform for the orchestration of computing, storage, and network resources. The application template will likely require entities to declare their capacity to share or their intent to use, aligning with these operational goals.

The Role of the Commission in Membership

The Commission acts as the central administrator of the Federation. Under Article 34(3), it must establish the platform that will host the membership registry and facilitate the technical exchange of services. When an entity submits its request under the template provided in the implementing acts, it is asking to be integrated into this Commission-managed ecosystem.

It is important to distinguish between joining the Federation and sharing services. While the request to join is governed by Article 34, the actual act of sharing services (e.g., a Member State offering idle capacity to another) is governed by Article 35. Under Article 35(3), a sharing entity must demonstrate to the Commission that it fulfills specific technical, operational, and organizational measures before it is allowed to share. Thus, the Commission's role is twofold: first, to process the membership request, and second, to assess the specific conditions for sharing if the member intends to provide services.

What this means for you

For public sector bodies and Union entities, the accession process under the proposed CADA requires proactive planning. Here is how to prepare for the implementation of Article 34:

  1. Monitor the Examination Procedure: Since the specific procedure and template are not yet in force, you must track the progress of the implementing acts under Article 34(4). These acts will be subject to the examination procedure under Article 46(2). Stakeholders should engage with their national representatives in the committee to ensure the final template is practical and aligned with national administrative systems.
  2. Prepare for the Standardized Template: Do not draft internal application policies based on assumptions. Wait for the Commission's implementing acts, which will provide the definitive template. This template will likely require detailed information on your current cloud infrastructure, security posture, and capacity to share or use services.
  3. Assess Your "Sharing" Capability: If your organization intends to act as a "sharing entity" (providing capacity), you must be ready to demonstrate compliance with Article 35(2). This requires putting in place "appropriate technical, operational and organisational measures to ensure an effective, secure and resilient provision of services." Audit your infrastructure now to ensure it can meet these standards before the application window opens.
  4. Budget for Administrative Fees: While joining is voluntary, it is not cost-free. Article 36(1) states that costs arising from the Commission's activities "shall be jointly financed by the members of the EuroCloud Federation through fees levied by the Commission." Procurement officers should anticipate these fees in their long-term IT budgets. The exact amount will be determined by subsequent implementing acts under Article 36(4).
  5. Strategic Alignment: Evaluate if your cloud strategy aligns with the Federation's goals of sharing idle capacity and enhancing sovereignty. If your organization relies heavily on non-EU providers for critical workloads, joining the EuroCloud Federation could be a strategic move to access sovereign, EU-based capacity from other public bodies. However, ensure your data classification and security requirements match the assurance levels available within the Federation.

Common misconceptions

"Membership is mandatory for all public bodies."

  • Reality: Article 34(1) explicitly states participation is on a "voluntary basis." No public sector body is forced to join. However, non-members may miss out on the cost efficiencies and resilience benefits of shared sovereign capacity.

"Private cloud providers can join the EuroCloud Federation."

  • Reality: The Federation is strictly for Union entities and public sector bodies. Article 35(1) and the broader context of Title IV Chapter III emphasize that this is a public-sector cooperation mechanism. Private providers can offer services to members, but they cannot be members of the Federation itself. The sharing of services must be between members of the Federation.

"The Commission approves the technical security of each member's cloud."

  • Reality: The Commission facilitates the platform and the membership request. However, the responsibility for demonstrating that technical, operational, and organizational measures are in place lies with the sharing entity (Article 35(2)). The Commission assesses whether these conditions are fulfilled to allow sharing, but the primary burden of proof and ongoing compliance rests with the member public body.

"Joining is free."

  • Reality: Article 36(1) clearly establishes a fee-based financing model. Members must pay fees to cover the Commission's administrative and platform costs. These fees are designed to recover costs, not to generate profit, but they are a real budgetary consideration.

Related

This is general information about a draft EU regulation, not legal advice.