The cloud clause checklist for ULA holders.

Seven checks that tell you whether your cloud estate becomes permanent entitlement or counts for nothing at exit. Work through them early, while every answer still has a move attached.

By Daniel Voss · Ex Oracle LMS · 4 June 2026

The short answer

To know whether your cloud deployments count toward certification, work through seven checks: whether public cloud is permitted to count, whether your provider is named, whether a continuous running requirement applies, whether you can evidence it, whether the clause is silent on anything you use, what the move is for each finding, and whether you have runway to make it. Run the checklist twelve to eighteen months before exit, because almost every outcome needs time to act on.

A working checklist, not a theory

How do I know if my cloud deployments count toward certification?

You answer it with a checklist, not a guess. Cloud counting is set entirely by your contract, so the only reliable way to know your position is to test your estate against your wording, item by item. The seven checks below form the Cloud Clause Checklist we use at the start of any cloud aware exit. Each one ends in a clear answer, and each answer points to a move you can make while there is still time. If you cannot answer an item, that uncertainty is itself the finding, and it becomes the first thing to resolve.

The Cloud Clause Checklist

  1. Is public cloud permitted to count? Find the certification provisions and confirm whether deployments in any public cloud are allowed to count toward the baseline at all. If they are excluded, the estate will not count as it stands.
  2. Is your provider named as authorised? Check whether the clause names AWS, Azure, or the providers you actually use. A provider that is not named may not be covered, even if public cloud generally is.
  3. Does a continuous running requirement apply? Look for a threshold such as 365 continuous days. Where it applies, only estate that has run that long qualifies, which makes timing decisive.
  4. Can you evidence continuous operation? Confirm you hold records that prove each cloud deployment ran across the required period. A qualifying deployment still has to be provable.
  5. Is the clause silent on anything you use? Note any provider or configuration the agreement does not address. Silence is not inclusion, and a gap is a question to resolve, not an assumption to lean on.
  6. What is the move for each finding? Map every answer to an action: keep and evidence, ensure the threshold is met, relocate to a counting environment, or clarify a silent clause.
  7. Do you have runway to make it? Confirm there is enough time before the term ends to act. Most moves need many months, and a finding without runway is a constraint you simply absorb.
The Meridian principle

A cloud clause checklist is only worth running while every answer still has a move attached. Run it early and each finding is a decision. Run it at the window and each finding is a regret. Time is the variable that turns the same clause into an opportunity or a loss.

Reading the results, indicative

The table below maps common checklist outcomes to the move they call for, using an anonymized example. The mapping is indicative and exists to show the logic, not to represent any real engagement, and your move depends entirely on your own wording and timeline.

Checklist result The move
Counts, threshold met, evidenced Keep, document, and certify
Counts, threshold not yet met Hold estate in place until it qualifies
Public cloud excluded Repatriate on premises or move to OCI
Silent or provider not named Analyse, clarify, or relocate before the window

Indicative only. The right move for your estate depends entirely on your cloud clause and your timeline. The checklist is the method. The contract supplies the answers.

The next step

The checklist turns an uncertain cloud position into a set of decisions you can act on, and it is most valuable run early with an independent eye on the wording. If your window is approaching, an independent cloud clause review is the fastest way to a clear position. For the AWS specific reading, see does AWS count toward your certification, learn the full reading method in auditing your cloud clause before exit, and ground the approach in our ULA exit strategy guide.

Turn the checklist into a plan

Run the seven checks. Then make the move.

Book a ULA assessment and we will run the Cloud Clause Checklist against your agreement, tell you exactly what counts, and map the moves that keep your cloud estate in the certified number.

Book a ULA assessment