The Cloud Counting Clause Guide

What is inside

Why cloud counting decides your exit

A ULA grants unlimited deployment of named Oracle products for a fixed term. At the end you certify, and the count you can defend becomes your perpetual entitlement. When a large share of your estate runs in public cloud, the contract language on cloud counting determines whether those deployments add to the number you keep or fall away at the worst possible moment.

The headline finding

Many ULAs require deployments in AWS or Azure to run 365 continuous days to count toward the certification baseline. Some exclude public cloud entirely. Many are silent on GCP, and silence is not inclusion. Where cloud does not count, eligible workloads can be repatriated on premises or moved to OCI before exit so they do.

The clauses the paper unpacks

The authorized cloud environment clause, which names the providers that count and on what terms.
The continuous deployment test, usually 365 days, and how the measurement date interacts with it.
The public cloud exclusion, which removes some or all hyperscaler deployments from the count.
Silence on a provider, most often GCP, and why it does not default to inclusion.
OCI treatment, which many agreements handle more favourably than third party cloud.

How do you make cloud workloads count?

The paper sets out a sequence you run while the unlimited right still applies: read the cloud clause precisely, map every cloud deployment against the eligibility test, start the clock early on workloads that need a continuous run, and where a deployment will never qualify, move it on premises or to OCI before the window closes so it counts. Each step is evidenced for the file that defends the number later.

Indicative table, cloud eligibility at a glance

Provider treatment varies by contract. The values below are indicative and depend on the specific contract language.

AWS or Azure named: often counts if the 365 day continuous test is met by the measurement date.
Public cloud excluded: deployments do not count; repatriate or move to OCI before exit.
GCP not mentioned: treat as not counting unless confirmed in writing; silence is not inclusion.
OCI: frequently the most favourable, but still read the term.

Who should read it

CIOs, IT asset managers, enterprise architects, and general counsel at organisations holding an Oracle ULA, usually within 18 months of expiry, and especially those with material AWS, Azure, GCP, or OCI estates. The framework is vendor neutral and written from the buyer side.