Why cloud counting is contested
When ULAs were first written, almost all Oracle deployment ran on hardware the customer owned, and counting was a question of processors in a data centre. As enterprises moved workloads to AWS, Microsoft Azure, and Google Cloud, a new question arose: when the customer certifies, do the Oracle instances running in those public clouds count toward the perpetual entitlement. The answer matters enormously, because a company that has shifted a large share of its Oracle estate to the cloud could find that the most important part of its deployment is the part Oracle declines to count. The foundational mechanics are covered in the Oracle ULA pillar guide, and the operational side of running Oracle in the cloud during the term is covered in the ULA cloud deployments guide.
Oracle has responded to the cloud shift by tightening certification language. Many newer agreements limit how public cloud counts, and some exclude it from the certified figure altogether or cap it at the quantity running on a defined date or averaged across a final period. Because the policy has moved over time, two customers with apparently similar ULAs can face entirely different cloud counting outcomes depending on when and how their agreements were drafted.
Authorized cloud environments and the metric
Oracle defines a set of authorized cloud environments, historically AWS and Microsoft Azure, where its licensing rules for counting cloud vCPUs are published. Under that policy, licensing in authorized clouds is generally measured by counting vCPUs, with a conversion that treats a pair of vCPUs as equivalent to a processor licence where hyper threading is enabled, and one vCPU as a processor where it is not. This counting method is distinct from the on premises core factor table and applies specifically to recognised public clouds. The detail and current scope of recognised providers is set out in the authorized cloud environments guide.
In the cloud the unit is the vCPU, not the core, and the rule that converts vCPUs to licences is the rule that converts your cloud estate into permanent entitlement, or fails to.
Within a ULA the vCPU method governs how a cloud instance would be measured, but the prior question is whether the agreement permits cloud to be counted at all. Where it does, the customer counts cloud vCPUs at certification alongside on premises processors. Where the agreement is silent or restrictive, the same instances may be excluded regardless of how many vCPUs they consume.
What clauses decide ULA cloud counting?
Three contractual elements determine the outcome. The first is the certification clause itself, which defines what may be declared. Older clauses that simply count deployed processors of in scope products often allow cloud to be included on the vCPU basis. The second is any cloud specific language, which newer agreements increasingly add to limit or exclude public cloud from the count, sometimes permitting only the average quantity deployed over the final twelve months rather than a peak figure. The third is the definition of authorized environments, which controls which clouds are even eligible.
Reading these clauses together is essential, because a permissive certification clause can be overridden by a restrictive cloud rider. The organisation should establish, early in the term, exactly which of three regimes its ULA falls under: cloud fully countable, cloud countable subject to a cap or averaging rule, or cloud excluded. That determination shapes the entire cloud deployment strategy and should be confirmed with the same rigour applied to the certification mechanics generally.
Common cloud counting scenarios
The practical outcomes cluster into a handful of patterns that recur across engagements.
| ULA regime | Cloud at certification | Implication |
|---|---|---|
| Legacy, no cloud rider | Generally countable on vCPU basis | Deploy cloud freely and count it |
| Averaging clause | Average of final year counts | Keep cloud running steadily, not just at the end |
| Snapshot date clause | Quantity on a fixed date counts | Ensure cloud is at peak on that date |
| Cloud excluded | Cloud does not count | Weight permanent estate toward on premises |
| Authorized clouds only | Only recognised providers count | Avoid relying on non authorized clouds |
The averaging clause is the trap that catches the most organisations. A company that plans a large cloud migration for the final quarter, expecting to count a peak, discovers that the agreement counts the average across the year and that its late surge barely moves the figure. Where an averaging rule applies, cloud deployment must be brought forward and sustained so the annual average is high, not concentrated at the end. This interacts directly with the deployment timing discipline described in the deployment maximization guide.
Strategy for maximising cloud at certification
The strategy follows from the regime. Where cloud is fully countable, the organisation should treat authorized cloud the same as on premises and deploy in scope products there throughout the term, ensuring instances are live and evidenced at the cut off. Where an averaging or snapshot rule applies, the deployment schedule must be engineered to that rule, sustaining cloud capacity across the measured period rather than spiking it late. Where cloud is excluded, the organisation should keep the permanent core of its estate on premises during the ULA and treat cloud as a post certification destination supported by bring your own licence rights.
That last point connects cloud counting to bring your own licence economics. The perpetual entitlement certified from a ULA can later be carried into authorized clouds under BYOL, so even where cloud does not count at certification, the on premises licences the customer captures can still fund a cloud future. Sequencing the on premises count first and the cloud migration second is often the value maximising path when the agreement excludes cloud from certification.
What happens to cloud after certification
After certification the customer holds a fixed perpetual quantity and the unlimited right is gone. Cloud instances that were counted convert to entitlement; cloud instances that were not counted must be supported by the certified licences under Oracle cloud policy or licensed afresh. A common post certification pattern is to redeploy certified licences into authorized cloud under BYOL, applying the vCPU conversion to stay within the certified quantity. Exceeding that quantity in the cloud creates a new licensing requirement and a fresh audit exposure.
The interaction between the certified count, ongoing cloud growth, and any successor agreement is a core negotiation question. Organisations expecting continued cloud expansion after a ULA should model that growth against the certified ceiling before they certify, a planning step handled within the ULA negotiation service so the endgame is designed rather than discovered.
The buyer side view
The buyer side view is that cloud counting is decided by contract language, not by assumption, and that the single most valuable early action is to read the cloud and certification clauses and classify the agreement. Once the regime is known, deployment can be engineered to it: count cloud freely where permitted, sustain it across the measured period where averaging applies, and weight the permanent estate on premises where cloud is excluded. The organisations that lose value are those that migrate aggressively to the cloud without checking whether the cloud they are building will actually count.
Classify your ULA cloud regime now, read the authorized cloud environments guide for the vCPU mechanics, and align your cloud migration timetable with the certification rule rather than with infrastructure convenience alone.
Oracle ULA cloud counting: frequently asked questions
Do public cloud deployments count toward an Oracle ULA certification?
It depends on the agreement. Legacy ULAs often allow authorized cloud to count on a vCPU basis, but newer agreements increasingly cap or exclude public cloud at certification. The contract language decides. See the ULA pillar guide.
How is cloud measured for Oracle licensing?
In authorized clouds Oracle counts vCPUs, generally treating two vCPUs as one processor where hyper threading is on and one vCPU as one processor where it is off. See the authorized cloud environments guide.
What is a ULA cloud averaging clause?
A clause that counts the average quantity of cloud deployed over the final year rather than a peak. It defeats a late migration surge, so cloud must be deployed early and sustained across the measured period to count fully.
Can certified ULA licences be used in the cloud later?
Yes. Certified perpetual licences can be carried into authorized clouds under bring your own licence rights, applying the vCPU conversion, even where cloud did not count at certification. See the BYOL guide.