Oracle cloud licensing policy, 2026 read.

A buyer side read of the Oracle cloud licensing policy document for 2026, covering the counting rules, the Authorized Cloud Environment list, and the practical impact on real cloud deployments.

Every Oracle cloud deployment lives under a policy document, not just a contract clause. The contract paper sets the floor and the policy adds the modifications.

What is the Oracle cloud licensing policy and is it a contract?

It is a policy Oracle publishes and revises, not a document you sign. Oracle hosts the current version as Licensing Oracle Software in the Cloud Computing Environment.

Why is the policy unilateral?

Customers do not countersign the policy, so Oracle can change it without consent. That is why the version date matters as much as the rules inside it.

Which clouds are on the authorized list?

• Oracle Cloud Infrastructure: the strongest BYOL alignment.
• Amazon Web Services: recognized for EC2 and RDS for Oracle.
• Microsoft Azure: recognized for VMs and Oracle Database@Azure.
• Google Cloud: not on the Authorized list at policy parity.

How does Oracle count licenses on authorized clouds?

Counting uses vCPU, not sockets. On hyperthreaded instances two vCPUs equal one Processor license. Where hyperthreading is off, one vCPU equals one Processor license.

What edition limits apply on cloud?

• Standard Edition 2 is capped at sixteen vCPUs per instance.
• Enterprise Edition has no instance cap.
• The Java Universal Subscription does not change based on cloud deployment.

How does counting work on OCI and Oracle Database@Azure?

OCI counts in OCPU, and one OCPU equals one Processor license with no core factor reduction. Oracle Database@Azure follows the same OCI rules. Oracle documents the OCI model on its OCI pricing pages.

What is the OCPU mapping in practice?

An OCPU is two threads of a hyperthreaded core, or one thread of a non hyperthreaded core. License Included rolls the database fee into the bill, while BYOL strips it and applies your existing licenses.

Where the common advice on the Oracle cloud policy is wrong

The common advice is to treat the cloud policy as a settled rulebook you can plan against for years. We disagree. The policy is unilateral, and in the 2026 refresh Oracle tightened the hard partitioning language without changing a single contract. In roughly a quarter of the estates we reviewed, an architecture that was compliant under last year's wording was exposed under this year's. The buyer side move is to pin the dated policy version into the contract at renewal, so a future revision cannot reprice an existing deployment mid term.

The cloud policy is not a contract. The contract paper sets the floor. The policy moves around it. Read both, and pin the version that applies.

What changed in the 2026 policy refresh?

The 2026 refresh tightened the hard partitioning language and clarified Oracle Database@Azure. The list of authorized clouds did not grow.

What counts as hard partitioning now?

Only the technologies named in the Oracle Partitioning Policy reduce the metric. Most cloud instance shapes do not qualify, so the count follows the full vCPU mapping.

What should you pin at renewal?

• The dated policy version that applies to existing entitlements.
• The counting rule for each cloud you actually deploy on.
• A flag on any Google Cloud workload as a contract paper exception.

What to do next

1. Pull the current Oracle cloud licensing policy document and save a dated copy.
2. Cross check the policy against the active Oracle Master Agreement.
3. Map every cloud workload to the counting rule for the cloud it runs on.
4. Flag any Google Cloud Oracle workload as a contract paper exception case.
5. Update internal architecture guidance to reflect the 2026 refresh.
6. Add a clause that pins the counting rule for the next renewal term.
7. Brief cloud architects on the soft partitioning recognition rules.

White Paper · Oracle

Cut Oracle Spend 30 to 50%: The 5 Year Playbook

The five year buyer side playbook that cuts Oracle spend across Database, Java, Apps, OCI, and support, and the math behind a 30 to 50 percent cut. Read it free.

Read the white paper

Frequently asked questions

Is the Oracle cloud policy document part of my contract?

Indirectly. The contract usually references the policy, but the policy itself is unilateral and Oracle can revise it. Always pin the dated version that applies to your entitlements.

Does the cloud policy override the Oracle Master Agreement?

No. The Oracle Master Agreement is the floor. The policy modifies how counting works in cloud contexts under that agreement, so you read both together.

Why is Google Cloud treated differently?

Google Cloud is not on the Authorized Cloud Environment list at policy parity. Workloads there need contract paper clarity on a case by case basis rather than the standard cloud counting rules.

How does the vCPU to processor mapping work?

On authorized clouds with hyperthreading on, two vCPUs equal one Processor license. Where hyperthreading is off, one vCPU equals one Processor license. The core factor table does not apply to cloud counting.

How does counting work on OCI?

OCI counts in OCPU, and one OCPU equals one Processor license with no core factor reduction. An OCPU is two threads of a hyperthreaded core or one thread of a non hyperthreaded core.

Did the 2026 policy refresh add new clouds?

No. The Authorized Cloud Environment list did not expand. The refresh tightened the hard partitioning language and clarified that Oracle Database@Azure follows OCI counting rules.

Can we pin the policy version in our contract?

Yes. Push for a clause that references the dated policy version and prevents Oracle from applying a future revision to existing entitlements for the contract term.

Does soft partitioning reduce the license count on cloud?

No. Soft partitioning is not recognized on any cloud. Only the technologies named in the Oracle Partitioning Policy document reduce the metric, and most cloud instance shapes do not qualify.