Summary Yes, a Member State or Union entity can leave the EuroCloud Federation because participation is explicitly voluntary under Article 34(1) of the proposed Cloud and AI Development Act (CADA). However, exiting does not erase financial liabilities. Article 36(2) mandates that any initial establishment costs borne by the EU budget must be reimbursed by members over a period of up to three years; this obligation would persist even if a member withdraws before the period ends. While the primary text establishes the right to leave, the specific administrative procedures for withdrawal (such as notice periods and transition plans) are expected to be detailed in future implementing acts adopted by the Commission.

Detail

The EuroCloud Federation represents a key mechanism in the proposed CADA for fostering a sovereign, resilient, and interoperable public-sector cloud ecosystem. It allows Union entities and public-sector bodies to share data centre and cloud computing services. For national administrations, understanding the "exit clause" is as critical as understanding the entry requirements, particularly regarding the balance between strategic flexibility and financial commitment.

The Principle of Voluntary Participation

The legal foundation for the Federation's openness is found in Article 34(1) of the CADA proposal. The text states clearly: "The European public sector cloud federation (the 'EuroCloud Federation') is hereby established. The EuroCloud Federation shall be open for the participation of Union entities and public sector bodies on a voluntary basis."

This phrasing is deliberate. In EU legislative drafting, "voluntary basis" signifies that no Member State or Union entity is legally compelled to join, nor is it legally bound to remain indefinitely. If a national government determines that its cloud strategy no longer aligns with the Federation's objectives, or if it prefers a different sovereign cloud pathway (such as a purely national solution or a direct procurement from a non-federation provider), it retains the autonomy to withdraw. There is no "lock-in" clause in the primary regulation that forces indefinite membership.

Financial Obligations: The Reimbursement Trap

While the decision to join or leave is voluntary, the financial framework is binding. The Federation is designed to be cost-neutral for the EU budget in the long run, relying on a cost-recovery model.

Article 36(2) addresses the reimbursement of initial costs. The proposal acknowledges that "initial establishment costs may be borne by the general budget of the Union." However, it immediately qualifies this by stating: "they shall be reimbursed by the EuroCloud members over a period not exceeding three years from the date on which the costs were borne by the Union."

For a Member State considering exit, this creates a specific and potentially significant financial liability:

  • Pre-financed Costs: If the EU budget covers the setup of the platform or initial operational costs, these are treated as a loan to the members, not a grant.
  • Reimbursement Period: The law sets a maximum window of three years for this repayment.
  • Exit Liability: If a Member State joins and then decides to leave before the three-year reimbursement period has elapsed, it does not escape the debt. The exiting member would likely be required to settle its outstanding share of the pre-financed costs immediately or as part of the exit settlement. The regulation does not provide a "free exit" from financial commitments incurred during the membership period.

Procedural Gaps and Implementing Acts

The CADA proposal establishes the right to participate and the obligation to pay, but it does not yet provide a step-by-step administrative manual for resignation. Article 34(4) empowers the Commission to adopt implementing acts to "specify the procedure to participate in the EuroCloud Federation and template concerning the content and other details of the request for participation."

While Article 34(4) explicitly mentions the request for participation, the logical extension of a voluntary framework is that the same regulatory instrument (or a complementary one) will define the conditions and procedures for withdrawal. Until these implementing acts are adopted, the precise mechanics of leaving remain undefined in the primary text.

Procurement officers and legal teams should anticipate that these future acts will likely cover:

  1. Notice Periods: The minimum advance notice required to trigger a withdrawal (e.g., 6 or 12 months) to allow for service continuity planning.
  2. Transition Plans: Requirements for migrating data and workloads to ensure that public services are not disrupted during the exit process.
  3. Final Financial Settlement: The exact methodology for calculating the final reimbursement payment under Article 36(2), ensuring the EU budget is fully repaid before the member's status is formally terminated.

Strategic Implications

The voluntary nature of the EuroCloud Federation serves as a safeguard for national sovereignty, ensuring that the initiative remains a cooperative tool rather than a coercive mandate. However, the financial structure acts as a stabilizer. The requirement to reimburse pre-financed costs under Article 36(2) creates a "sunk cost" barrier that discourages frivolous or abrupt withdrawals. It encourages Member States to view membership as a medium-to-long-term strategic commitment rather than a short-term experiment.

What this means for you

For public-sector procurement officers, IT directors, and national cloud strategists, the voluntary nature of the EuroCloud Federation offers flexibility but demands rigorous financial and operational planning.

  1. Model the Total Cost of Ownership (TCO): Before joining, do not just calculate membership fees. Model the potential liability under Article 36(2). If your administration's cloud needs are short-term or highly experimental, the obligation to reimburse EU pre-financed costs within three years might make membership less attractive than a direct commercial procurement.
  2. Ensure "Exit Readiness": If you join the EuroCloud Federation, ensure your cloud architecture remains interoperable with non-federation providers. Avoid proprietary lock-in within the Federation's shared platforms. This reduces the operational risk and cost if you decide to withdraw later.
  3. Monitor Implementing Acts: Pay close attention to the implementing acts adopted by the Commission under Article 34(4). These documents will define the exact notice periods and administrative steps for withdrawal. Failure to follow these future procedural rules could complicate an otherwise legal exit.
  4. Coordinate with National Competent Authorities: Since the Federation involves national and European cloud initiatives, any decision to exit should be coordinated with your national competent authority for cloud sovereignty (designated under Article 25 of CADA) to ensure it aligns with national risk assessments and sovereignty strategies.

Common misconceptions

"The EuroCloud Federation is mandatory for all public sector cloud spending."

  • Correction: False. Article 34(1) clearly states participation is voluntary. While CADA encourages the use of sovereign cloud services (Union assurance levels), it does not force all public bodies into the EuroCloud Federation. Public bodies can procure sovereign cloud services from non-federation providers if they meet the required assurance levels.

"You can leave the Federation at any time without financial consequence."

  • Correction: False. Article 36(2) creates a binding financial obligation to reimburse initial EU budget contributions. Exiting early may trigger an immediate demand for the remaining balance of these reimbursable costs, regardless of the voluntary nature of the membership.

"There is a simple 'unsubscribe' button."

  • Correction: False. As a complex infrastructure federation involving data sovereignty and critical public services, exit will involve formal administrative procedures, likely defined in secondary legislation (implementing acts), to ensure data security, service continuity, and proper financial settlement.

Related

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