Oracle converts vCPUs in authorized public cloud to processor licenses, commonly counting two vCPUs as one processor where hyper threading is on. Whether that cloud counts toward your certification baseline is contract specific, because many ULAs require a continuous run period and some exclude public cloud entirely.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
Oracle counts cloud capacity through its cloud licensing policy, which maps virtual processors in authorized environments to the processor metric used on premises. The widely applied rule treats two vCPUs as one Oracle processor license where hyper threading is enabled, and one vCPU as one processor where it is not. So an instance presenting 16 vCPUs with hyper threading on counts as 8 processor licenses for the named product running on it. That conversion is the mechanical part. The part that decides whether those processors reach your certified number is your contract, because the cloud policy governs how cloud is licensed, while the ULA governs what counts toward the certification baseline.
The cloud policy tells you how vCPUs convert to processors. The ULA tells you whether that cloud counts toward certification, and on what conditions. Reading one without the other produces a number that does not hold.
There is no universal answer to whether cloud counts, because ULAs treat it differently. Many agreements allow deployments in authorized public cloud such as AWS and Azure to count toward the certification baseline only if they have run for a defined continuous period, frequently 365 days, by the certification date. The intent is to count durable production capacity rather than instances spun up at the last moment. Some agreements exclude public cloud from the baseline entirely, meaning vCPUs there will not lift the certified number however large they are. And contracts are often silent on specific providers, where the safe reading is that silence is not inclusion. The only reliable way to know your position is to read the cloud clause in your own agreement.
Where a continuous run period applies, timing becomes a planning problem. An instance that needs 365 continuous days to qualify must be running well over a year before the certification date, which means cloud capacity intended for the count cannot be left until the final months. This is one of the strongest reasons to begin the exit work early, so qualifying cloud is established in time.
Oracle's policy distinguishes authorized cloud environments, which currently include AWS and Azure, from other providers. The conversion rule and the ability to count apply to authorized environments. For providers the contract does not name, you cannot assume the same treatment, and you should not count them toward the baseline without confirming the position. We work through what to do when cloud does not count in the cloud counting mistakes that shrink your count.
Take an indicative estate. A named database runs across three authorized cloud instances: one with 32 vCPUs, one with 16, and one with 8, all with hyper threading enabled. At two vCPUs to one processor, that is 16, 8, and 4 processor licenses, for 28 in total. If the contract requires a 365 day continuous run and all three have met it by the certification date, those 28 processors can count toward the baseline. If only the first two have met the condition, only 24 count and the third does not until it qualifies. The figures are indicative, but they show how the conversion and the contract condition combine to produce the number that actually reaches your count.
| Cloud instance | vCPUs (HT on) | Processor licenses |
|---|---|---|
| Instance A | 32 | 16 |
| Instance B | 16 | 8 |
| Instance C | 8 | 4 |
| Total qualifying | 56 | 28 |
The conversion ratio and the counting conditions depend on the cloud policy version and the contract language that apply to you, so confirm both before relying on a figure.
Cloud can be a meaningful part of a certified count, but only when the conversion is done correctly and the contract conditions are met. Read the cloud clause early, identify which instances will satisfy any continuous run requirement by the certification date, and document the vCPU counts and run periods as evidence. Where cloud is excluded, there are still options, including repatriating workloads on premises or moving them to OCI before exit so they count, which we cover in licensing cloud instances post ULA. The full exit method sits in our pillar, the ULA exit strategy guide.
Counting vCPUs in authorized cloud is two steps: convert vCPUs to processor licenses under the cloud policy, then confirm the contract lets that cloud count toward your baseline. The conversion is mechanical. The counting is contract specific, often gated by a continuous run period and sometimes excluded outright. Read both documents together, plan for the timing, and document the evidence, because cloud counted wrongly either surrenders value or creates exposure.
Under Oracle's cloud licensing policy, vCPUs in authorized public cloud are converted to processor licenses, commonly counting two vCPUs as one processor where hyper threading is on. The exact conversion and whether the cloud counts toward the certification baseline depend on your contract and the policy in force, so both must be read together.
No. Cloud counting is contract specific. Many ULAs require cloud deployments to run for a defined period, often 365 continuous days, to count toward the baseline, and some exclude public cloud entirely. Contracts are frequently silent on certain providers, and silence is not inclusion.
Book a confidential assessment and we will read your cloud clause and measure the vCPUs that genuinely count toward your certification.