The Irish presidency of the Council of the European Union outlined revisions to proposed cloud and artificial intelligence rules in a November 13 progress report. The revisions address what cloud providers would need to document and how some public buyers would assess services. The report does not create new obligations.
The European Commission put forward the Cloud and AI Development Act in June. The Commission frames it around research and deployment, expanding data center capacity, and reducing exposure to disruptions or decisions outside the EU. The proposal addresses the infrastructure that runs AI systems rather than the behavior of individual applications. Alongside plans to make permitting easier for sustainable data centers, the Commission proposed a common framework to help public buyers compare cloud services against their needs.
What is under discussion
The presidency would clarify how a cloud service earns and can lose recognition at a particular EU assurance level. It proposed reviewing providers’ independent audit opinions every two years instead of annually and extending certain purchasing provisions to organizations already subject to EU procurement rules for utility sectors, such as electricity and water. An assurance level is a rating for what a service can demonstrate about where it runs and who controls key parts of its operation.
The audit and the service rating would answer different questions. An audit looks at the evidence behind a provider’s claims. The rating would give a buyer a way to compare that evidence with what a particular workload needs. A team buying email hosting and a team buying cloud services for a utility control room may care about different kinds of interruptions, even if the two services come from the same supplier.
What buyers and providers can watch
For buyers following the proposal, it helps to distinguish an individual service from a vendor’s whole portfolio. A transit operator, for example, might use one service to process its ticket sales and another to store backup copies. The two services could have different locations, administrators and recovery arrangements. Evidence for one would not tell the buyer much about its backup unless the scope of that evidence actually covered both.
Buyers can make those differences visible by asking three questions: where the information goes, who can act on the service, and what the buyer could take with it if the service had to change. A sample answer should say whether it covers the provider’s support procedures and backup systems as well as its primary servers. Those are procurement questions, not requirements imposed by the progress report.
Delegations are scheduled to discuss revisions on research and data center capacity on November 24. The presidency intends further drafting in December. The roadmap aims for adoption in the fourth quarter of 2027, a target rather than a guarantee.



