Most buyers who win the argument about the policy lose the argument about the number

Every Oracle cloud deployment sits under two documents. Your ordering document and master agreement set the floor; the cloud licensing policy describes how Oracle intends to apply that floor to somebody else's infrastructure. The policy is unilateral, undated in your contract, and changeable without notice, and reading only one of the two documents is how migrations get mispriced.

Prepared by Redress Compliance · August 10, 2026 · Oracle advisory. Based on 40 to 55 Oracle cloud licensing reviews, 2024 to 2025.

• Applying the core factor to cloud instances. It does not apply on an Authorized Cloud Environment, and using it understated the requirement by half on hyperthreaded shapes.
• Assuming a cloud is in or out of the policy without reading the current version. In about one review in three someone had assumed wrongly, in either direction, usually from guidance predating the Google Cloud addition.
• Relying on soft partitioning to cap the count. A quarter of estates did, and none of it held, because the partitioning policy decides what Oracle accepts as a boundary and Oracle writes that too.
• Rebuilding instances without recording the licensing consequence. A shape change alters the vCPU count and therefore the requirement, and nothing in the cloud console flags it.
• Running past the Standard Edition 2 cap. Eight vCPUs, with four counting as one socket, so a twelve vCPU instance is an unbudgeted Enterprise Edition deployment.

There is a clever reading of the cloud policy that circulates widely and costs money.

It runs like this: the policy says it is for educational purposes, may not be incorporated into any contract, and is subject to change without notice, therefore it does not bind you, therefore Oracle cannot rely on it. The first half of that is correct and the conclusion is not.

Oracle genuinely cannot hold up the policy and declare your count settled, because it has to argue that your agreement's own definition of Processor, applied to your actual deployment, produces the number in the table, and that is an argument rather than an automatic outcome.

But the disclaimer is not a shield you can pick up, because if the policy does not bind then its favourable parts do not bind either, and the fallback is the on premises rule: count the physical cores in the host.

In a multi tenant public cloud that rule is unanswerable, since you cannot count cores in a machine the provider will never show you and cannot control which machine your instance lands on. That is the trap.

Buyers who win the argument about whether the policy applies routinely lose the argument about what the number is, and they lose it in a worse position than the one they started from.

The productive move is neither to accept the policy as contract nor to dismiss it, but to price against it, verify every shape against it, and negotiate an amendment that pins a dated version for the term.

The commitment side of an Oracle cloud deal sits in the cloud negotiation guide, and the reference rates in the technology price list.

Across roughly 40 to 55 Oracle cloud licensing reviews we ran between 2024 and 2025, the customer's own licence position was off by 20 to 35 percent before anyone from Oracle asked a question, and four patterns repeated:

Teams applied the core factor to cloud instances, understating the requirement by half on hyperthreaded shapes. Roughly one review in three carried an untested assumption about whether a cloud was covered. A quarter of estates relied on soft partitioning that did not hold.

And instance rebuilds changed vCPU counts with nobody recording the licensing consequence.

The buyer side move is to read the two documents together rather than either alone, verify every shape against the current dated policy version, treat soft partitioning as unavailable unless your paper says otherwise, put a change record against every rebuild.

And negotiate an amendment that pins the policy version for your term.

Is the Oracle cloud licensing policy a contract?

No. Oracle drafts, dates, posts, and revises it without your signature, and it states on its face that it is for educational purposes, may not be incorporated into any contract, and is subject to change without notice.

Your ordering document does not usually incorporate it by reference, which is why the version date matters as much as the rules.

How are Oracle licences counted on the major clouds?

By vCPU. Two vCPUs equal one Processor licence where hyperthreading is enabled, and one vCPU equals one Processor licence where it is not.

The Processor Core Factor Table does not apply, so a 32 core workload needing 16 Processor licences on your own hardware needs 32 in an Authorized Cloud Environment.

Which clouds are Authorized Cloud Environments?

Four named services across three providers: Amazon Elastic Compute Cloud, Amazon Relational Database Service, the Microsoft Azure Platform, and Google Cloud Platform. Nothing else.

Google Cloud belongs on that list, and guidance written before it was added is still widely quoted, which leads teams to price Google workloads under the wrong rule.

Why is Oracle Cloud Infrastructure not on the list?

Because it is Oracle's own cloud and runs under Oracle's own service terms and OCPU conversion rather than under the third party cloud policy.

That distinction matters when comparing quotes, since the counting unit and the governing document are both different from the ones that apply to a workload on someone else's infrastructure.

Can we rely on the disclaimer to reject the policy?

Not usefully. Oracle cannot simply hold up the policy and declare your count settled, since it has to argue your agreement's definition of Processor produces that number.

But if the policy does not bind, its favourable parts do not bind either, and the fallback is counting physical cores in a multi tenant host the provider will never show you.

Does soft partitioning cap the count in the cloud?

No. Roughly a quarter of the estates we reviewed relied on it and none of it held, because what Oracle accepts as a partitioning boundary is set by the partitioning policy, which Oracle also writes and revises unilaterally.

Treat soft partitioning as unavailable unless your own contract says otherwise in writing.

What is the Standard Edition 2 limit in the cloud?

Eight vCPUs, with four vCPUs counting as one socket. A twelve vCPU instance is therefore an Enterprise Edition deployment, which is a materially different licence position and one nobody budgeted for. Shape changes at rebuild are the usual way estates cross that line without noticing.

What is the strongest protection to negotiate?

An amendment that pins a dated policy version for the term of your agreement. It converts a document Oracle can revise without notice into one that is fixed for both parties, and it is considerably cheaper to obtain than the licences a later revision could require. Very few buyers ask for it.