Editorial photo of a cloud architect reviewing policy documents
Oracle Policy

Oracle cloud licensing policy, 2026 read.

The Oracle cloud policy document read from the buyer side, with the counting rules, the Authorized Cloud Environment list and the practical contract moves.

Contact Us Oracle Practice
500+Enterprise clients
$2B+Under advisory
Download the Oracle ULA Decision Framework · Oracle ULA exit moves, Java audit defence posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate. Download →
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Home › Oracle Hub › Oracle Cloud Licensing Policy 2026 Oracle Practice BYOL Pillar Hub
Portrait placeholder for Fredrik Filipsson, Co Founder and Group CEO
Written by Fredrik Filipsson Co Founder & Group CEO · ex Oracle, IBM, SAP
PublishedMay 17, 2026
Last updatedMay 17, 2026

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.

Key takeaways

  • The cloud policy document is not a contract. It is a unilateral policy that Oracle can revise without customer agreement.
  • Authorized Cloud Environments today are OCI, AWS and Azure. The list does not include Google Cloud at policy parity.
  • Counting on Authorized Cloud Environments uses a vCPU to Processor mapping, not a per socket mapping.
  • OCI uses a one to one OCPU mapping, no core factor reduction.
  • Soft partitioning is not recognized on any cloud.

Every Oracle cloud deployment lives under a policy document, not a contract clause.

The policy can change. The contract paper sets the floor, the policy adds the modifications.

This page summarizes the 2026 policy as it applies to typical enterprise cloud moves.

What is the Oracle cloud licensing policy document?

Unilateral, not contractual

The policy is published by Oracle and revised periodically.

Customers do not sign it. Oracle can change it without customer consent.

Authorized Cloud Environment list

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

How does counting work on Authorized Cloud Environments?

Hyperthreaded mapping

Two vCPUs equal one Processor license on hyperthreaded x86 instances.

Non hyperthreaded instances count one vCPU as one Processor license.

Edition limits

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

Oracle counting rules by cloud, 2026 policy.

Cloud Counting unit Hyperthreaded rule BYOL recognized
OCIOCPU1 OCPU = 1 ProcessorYes
AWS EC2vCPU2 vCPU = 1 ProcessorYes
AWS RDSvCPU2 vCPU = 1 ProcessorYes
Azure VMvCPU2 vCPU = 1 ProcessorYes
Oracle Database@AzureOCPU1 OCPU = 1 ProcessorYes
Google CloudNot on Authorized list at policy parityPer contract paperCase by case
The cloud policy is not a contract. The contract paper sets the floor. The policy moves around it. Read both.

How does counting work on OCI?

OCPU mapping

One OCPU equals one Processor license, with no core factor reduction.

An OCPU is two threads of a hyperthreaded x86 core, or one thread of a non hyperthreaded core.

License Included versus BYOL

License Included rolls the Oracle Database fee into the OCI bill.

BYOL strips the database fee and lets customers apply existing licenses.

What changed in the policy in 2026?

Tighter language on hard partitioning

The 2026 policy refresh tightened the language on what counts as hard partitioning in cloud contexts.

Only the technologies listed in the Oracle Partitioning Policy document reduce the metric.

Clarity on Oracle Database@Azure

  • Oracle Database@Azure runs under OCI counting rules.
  • BYOL is supported with the same Processor mapping as OCI native.
  • Reserved Instances and Hybrid Benefit do not apply.

Suggested reading

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 policy refresh.
  6. Add a contract clause that pins the counting rule for the term of the next renewal.
  7. Brief cloud architects on the soft partitioning recognition rules.
  8. Plan an annual policy refresh review tied to the contract anniversary.

Frequently asked questions

Is the policy document part of my contract?

Indirectly. The contract usually references the policy. The policy is unilateral and can change. Always pin the version that applies.

Does the policy override the OMA?

No. The OMA is the floor. The policy modifies how counting works in cloud contexts under the OMA.

Why is Google Cloud treated differently?

Google Cloud is not on the Authorized Cloud Environment list at policy parity. Workloads need contract paper clarity on a case by case basis.

Did the 2026 policy add new clouds?

Oracle Database@Azure clarity was added. The Authorized Cloud Environment list itself did not expand.

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.

Oracle ULA Decision Framework

The full oracle ula decision framework framework from the Oracle Practice.

Oracle ULA exit moves, Java audit defence posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the Oracle Java license calculator against your estate in under five minutes.
Open the Tool →
4 Clouds
Covered
2:1
vCPU Map
16
SE2 Cap
500+
Enterprise Clients
100%
Buyer Side
“

The cloud policy is not a contract. The contract paper sets the floor. The policy moves around it.

Fredrik Filipsson
Co Founder and Group CEO, Redress Compliance
Deep Library

More on this topic.

Oracle Practice →
Oracle ULA decision framework on a desk
Oracle
Oracle ULA Decision Framework
Renew, certify or exit. The structured decision framework used across more than one hundred Oracle ULA renewal cycles.
12 min read
Oracle Java licensing change on a screen
Oracle
Oracle Java Licensing 2026
The Employee metric explained, audit posture, and the buyer side moves to flatten the Java bill.
10 min read
Oracle audit defense playbook on a boardroom table
Oracle
Oracle Audit Defense Playbook
What to do on day one of an Oracle audit, the LMS process, and how to compress a six figure finding.
11 min read
Oracle Database licensing explained on a screen
Oracle
Oracle Database Licensing Explained
Processor, NUP, options and packs. The full licensing model with the buyer side moves at every step.
9 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

Contact Us Vendor Shield

Get the Oracle cloud brief

Monthly brief on Oracle cloud policy moves, OCI pricing benchmarks and the buyer side moves across cloud migrations. Independent. Buyer side. Never sponsored.