Oracle Licensing in Public Cloud: 2026 Guide

If you read nothing else

The bottom line on Oracle licensing in public cloud

Bottom LineOracle licensing in public cloud is governed by a policy, not your contract. On AWS, Azure, and Google Cloud, Oracle's authorized cloud environment policy counts 2 vCPUs as 1 Processor licence for Enterprise Edition with hyperthreading on, and the Core Factor Table is excluded; on OCI, BYOL maps 1 Processor licence to 2 OCPUs. The trap is that architects size with the on-premises core factor, under-license the estate, and hand Oracle a back-licence claim in the next audit.

Public cloud does not simplify Oracle licensing — it swaps one rulebook for another that most buyers never read. The hardware-based Core Factor Table you used on-premises is gone, replaced by a flat virtual-CPU ratio that Oracle can revise at will because it lives in a policy document rather than your signed agreement. This guide walks the rules cloud by cloud — the AWS/Azure/GCP authorized environments and Oracle's own OCI — and shows where the compliance gaps and audit exposure hide, and how to right-size before you provision a single instance.

Key takeaways

2 vCPUs = 1 Processor licence in authorized clouds. On AWS, Azure, and Google Cloud, Oracle Database Enterprise Edition counts 2 vCPUs as 1 Processor licence when hyperthreading is on, and 1 vCPU as 1 licence when it is off (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026).
The Core Factor Table does not apply in the cloud. In every authorized cloud environment Oracle replaces the core factor with the flat vCPU ratio regardless of chip model, so a workload that licensed at a 0.5 factor on Intel can require more licences in the cloud at the same core count (Oracle, Cloud Computing Environment policy, 2026).
The rules are policy, not contract. The authorized cloud environment ratios sit in a document Oracle publishes and can change unilaterally — they are not in your Oracle Master Agreement. Pin and archive the version in force on the day each workload deploys.
Standard Edition 2 is capped in the cloud. SE2 may only run on instances up to 8 vCPUs; an instance of 4 or fewer vCPUs counts as 1 socket, and by Named User Plus the minimum is 10 NUP per 8 vCPUs (Oracle, Cloud Computing Environment policy, 2026).
Cloud raises audit exposure when the rule is misapplied. Across 600+ Oracle engagements, the average audit claim is 3 to 5 times what the customer actually owes — and misapplied cloud counting is one of the most common root causes (Oracle Licensing Experts engagement data, 2026).

Recommendations by role

What to do before you run Oracle in public cloud, by seat

CIO Strategy

Mandate that no Oracle workload is provisioned in any public cloud until it has a documented licence position under that cloud's specific rule, not the on-premises model.
Treat the cloud counting policy as a moving target: require the architecture team to archive the policy version at each deployment so a later Oracle change cannot be applied retroactively without challenge.
Keep edition choice on the table — Enterprise Edition, Standard Edition 2, and third-party-supported legacy each carry different cloud economics, and the cheapest compliant edition is a strategy decision, not a default.

Head of Infrastructure Deploy

Size every Oracle instance against the flat vCPU rule for its destination cloud before picking a shape; never halve licences on a core-factor assumption that does not apply in the cloud.
Cap autoscaling groups that run Oracle at a licensed ceiling and alert on breach — licensing follows peak provisioned vCPUs, not the average.
Track every database option in use — Partitioning, Advanced Compression, Diagnostics and Tuning Packs — because they travel into the cloud and must be licensed there too.

SAM / ITAM Manager Compliance

Maintain a live entitlement-to-deployment ledger spanning on-premises, BYOL, and License Included estates; mixed deployments are a standard Oracle audit trigger.
Reconcile owned Processor and NUP entitlements before any BYOL claim so the cloud footprint draws only on licences you can prove you hold.
Document hyperthreading state per instance, because it flips the ratio between 2-vCPU and 1-vCPU per licence and is the first thing an auditor checks.

CFO Capital

Compare BYOL against License Included on a fully-loaded basis — owned licences plus their 22% support versus the bundled hourly rate — before approving a cloud database spend.
Budget for the support stream continuing: every perpetual licence you BYOL keeps incurring 22% of net license value per year in parallel with cloud consumption.
Hold a costed fallback — a different edition, third-party support, or staying on-premises — so a cloud commitment is a choice, not a one-way door that hands Oracle the upper hand at renewal.

The framework

The Oracle public cloud licensing framework, question by question

How is Oracle licensed in the public cloud?

By a different rule for each destination. On AWS, Microsoft Azure, and Google Cloud — Oracle's named authorized cloud environments — Oracle counts 2 vCPUs as 1 Processor licence for Enterprise Edition when hyperthreading is enabled, and 1 vCPU as 1 licence when it is off (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026). On Oracle's own OCI, the meter is the OCPU, and BYOL maps 1 Processor licence to 2 OCPUs (Oracle BYOL to PaaS FAQ, 2026). The same software, the same workload, three different counting methods depending on where it runs.

That destination-dependence is the whole game. A buyer who assumes Oracle licensing is portable — that the count travels unchanged from the data centre to AWS — is wrong in both directions: sometimes the cloud rule is cheaper, often it is not. The only defensible approach is to model each workload under the exact rule of its target cloud before provisioning, and to keep that model as the evidence base if Oracle ever asks. Right-sizing is the work; choosing the cloud is the easy part.

✦ Practical Tip

Build one reconciliation sheet before you provision: every Oracle Processor and NUP entitlement you own, the support you pay on each, and the cloud workload it will back under that cloud's vCPU or OCPU rule. That sheet is the only defensible basis for BYOL sizing. See our Oracle license optimization approach.

Why does the Core Factor Table stop applying in the cloud?

Because Oracle says so in the cloud policy, and it works in Oracle's favour. The Core Factor Table is Oracle's on-premises multiplier that scales licence requirements by processor type — a 0.5 factor for most Intel and AMD cores, for example, so two physical cores need one Processor licence. In every authorized cloud environment, Oracle discards that multiplier and substitutes a flat ratio of 2 vCPUs per licence regardless of the underlying chip (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026). There is no 0.5 discount in the cloud.

The consequence catches teams that reason from habit. A workload that needed, say, 8 Processor licences on a 32-core 0.5-factor server does not automatically need 8 in the cloud — it needs as many as the provisioned vCPUs divided by two, which can be more or fewer depending on how the instance is shaped. Assuming the core factor still applies is the single most common way cloud Oracle estates end up under-licensed, and it is exactly the kind of error Oracle's audit process is built to surface.

⚑ Red Flag

If your cloud architects size Oracle instances by halving cores "because they're 0.5-factor," you are under-licensed on AWS, Azure, and GCP from first boot. The authorized cloud policy overrides the core factor entirely — the flat 2-vCPU ratio is the only number that counts in the cloud.

What is an authorized cloud environment, and which clouds qualify?

An authorized cloud environment is Oracle's policy designation for the third-party clouds where its specific cloud counting rules apply. As of mid-2026 that means Amazon Web Services, Microsoft Azure, and Google Cloud Platform; Oracle has at times recognised additional providers in specific regions, but those three are the universally named set. Inside an authorized environment the fixed vCPU-to-licence ratio governs, and the Core Factor Table is explicitly out of scope.

The critical qualifier is where the rule lives. The authorized cloud designation and its ratios are set in a policy document Oracle publishes — not in your Oracle Master Agreement, ordering document, or any signed term. Oracle can revise that policy, add or remove a provider, or change the ratio, and absent a negotiated contractual lock you inherit the change. A hyperscaler's marketing that an instance type is "supported for Oracle" is not the same as a contractual right; only the policy text in force at your deployment, archived, protects you.

? What to Ask Oracle

"Confirm in writing the authorized cloud environment vCPU-to-licence ratio that applies to our Enterprise Edition deployments on [AWS / Azure / GCP] as of today's date, and confirm that the Core Factor Table is excluded. Provide the exact policy document and version you are relying on."

How is Oracle Database Enterprise Edition counted on AWS, Azure, and GCP?

By provisioned vCPUs against the flat ratio. For Enterprise Edition, 2 vCPUs equal 1 Processor licence when hyperthreading is enabled — which it is on most hyperscaler instance families — and 1 vCPU equals 1 licence when hyperthreading is off (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026). An eight-vCPU instance with hyperthreading on therefore requires four Enterprise Edition Processor licences; the same instance with hyperthreading disabled requires eight.

Two practical points follow. First, hyperthreading state is a licensing decision, not just a performance one — turning it off doubles your licence requirement, and auditors check it instance by instance. Second, the count is of provisioned vCPUs, so a stopped instance you can restart, or an autoscaling group's maximum size, can be the number Oracle measures, not your steady-state average. Enterprise Edition options — Partitioning, Advanced Compression, Diagnostics Pack, Tuning Pack — are licensed on the same vCPU basis wherever the database that uses them runs.

▲ OLE Benchmark

Across 600+ Oracle engagements, the most frequent public-cloud compliance gap is core-factor misapplication: estates sized as if the 0.5 multiplier still applied, which under-states the true Enterprise Edition requirement by an average of 1.4 to 2 times on the affected workloads (Oracle Licensing Experts benchmark, 2026). Catching it before Oracle does is the difference between a quiet correction and a seven-figure back-licence claim.

How is Standard Edition 2 licensed in the cloud — and when is it the cheaper play?

Standard Edition 2 is counted by socket-equivalents, not the EE vCPU ratio. In an authorized cloud environment, a SE2 instance with 4 or fewer vCPUs counts as one socket, and above that every 4 vCPUs, rounded up, equals one socket; SE2 may only be deployed on instances up to 8 vCPUs (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026). Licensed by Named User Plus, SE2 carries a minimum of 10 NUP per 8 vCPUs. Those caps make SE2 a deliberately small-footprint edition.

SE2 is the cheaper play when the workload genuinely fits inside the cap and does not need Enterprise Edition features — no Partitioning, no Advanced Compression, no RAC beyond SE2's limited support, no Diagnostics or Tuning Pack. Buyers frequently over-buy Enterprise Edition for workloads that would run compliantly on SE2 at a fraction of the licence cost, then pay 22% support on the inflated base every year. Right-sizing the edition is as important as right-sizing the core count, and it is a decision the cloud move is the right moment to revisit.

◆ Negotiation Lever

If a workload fits SE2's 8-vCPU cap and uses no Enterprise Edition options, model it on SE2 before you accept an EE renewal. The edition downgrade is a legitimate, buyer-side cost reduction Oracle will not volunteer. See our Oracle support cost reduction approach.

What is the difference between BYOL and License Included?

BYOL — Bring Your Own License — applies your existing perpetual Oracle Processor or Named User Plus licences to cloud capacity, so you pay only the infrastructure rate. License Included bundles the Oracle software licence into a higher hourly rate, so you rent the licence with the compute. On OCI, BYOL converts 1 Processor licence to 2 OCPUs, and the BYOL database rate runs far below the License Included rate because it strips the software out of the meter (Oracle BYOL to PaaS FAQ, 2026).

The choice is an arithmetic one, but only if you know what you own. BYOL is decisively cheaper when you already hold entitlements and have reconciled them — but an unverified licence position leaves the benefit unclaimed and risks BYOL-ing licences you cannot actually evidence in an audit. License Included is the right answer for genuine net-new demand where you hold no licences, or for short-lived and bursty workloads where renting beats owning. Many estates run a mix, which is precisely why a clean entitlement ledger matters.

§ Sample Clause

"Customer may apply its owned, fully-supported Oracle Program licences to eligible cloud capacity under Bring Your Own License at the conversion ratio published in Oracle's cloud policy in force on the Effective Date, and such ratio shall not be applied less favourably to Customer's existing deployments by reason of any later revision to that policy."

Does running Oracle in public cloud raise your audit exposure?

Not by the act of deploying — but yes by how easy it is to get the rules wrong. Oracle's License Management Services can read cloud configuration data, and a vCPU count against a published ratio is far simpler to verify than a contested VMware cluster. The most common finding is core-factor misapplication; the second is options pull-through, where Partitioning or the Diagnostics and Tuning Packs run in the cloud unlicensed because they were "always on" in the source environment. Both are routine, both are avoidable with a pre-deployment model.

The buyer-side answer is to make compliance evidence a deliverable of the migration, not a scramble after an audit notice. Keep the entitlement ledger current, archive the policy version per deployment, document hyperthreading and provisioned vCPUs per instance, and reconcile options against entitlements every quarter. An estate that can produce that evidence on demand turns an Oracle audit from an open-ended claim into a short, factual exchange. Where it cannot, the average claim runs 3 to 5 times the real liability. Our Oracle audit defense team works exactly this evidence base.

✦ Practical Tip

Run a self-directed cloud licence review once a quarter: provisioned vCPUs per Oracle instance, hyperthreading state, options in use, and entitlements held. Finding your own gap and fixing it on your terms is always cheaper than letting Oracle find it on theirs.

Decision matrix

Which public cloud licensing path fits your estate?

OCI, BYOL-first

Own EE licences · Oracle-centric estate

Reconcile owned Processor licences and BYOL them at 2 OCPUs each, earning Support Rewards on consumption. Lowest effective rate and native Oracle tooling — the default when your estate is Oracle-heavy and you hold entitlements.

BYOL on AWS / Azure / GCP

Hyperscaler-anchored · own licences

Your apps live in a hyperscaler and you own Oracle licences. License under the 2-vCPU rule, ignore the core factor, pin the policy version. Viable and compliant — but you forgo OCI Support Rewards and carry the full 22% support bill.

License Included

Net-new demand · no owned licences

You hold no spare entitlements, or the workload is short-lived and bursty. Rent the licence with the compute at the bundled rate. Simple and audit-clean, but the most expensive per hour for steady-state workloads.

SE2 / edition right-size

Small workload · no EE options

The workload fits SE2's 8-vCPU cap and uses no Enterprise Edition features. Downgrade the edition before renewing EE. Lowest licence cost, but only valid inside the SE2 caps — confirm no option is silently in use.

Decision matrix: the right path is set by two axes — whether you already own Oracle entitlements, and how Oracle-centric versus hyperscaler-anchored your estate is — not by which incentive a vendor offers this quarter.

Strengths & cautions

Oracle public cloud licensing options, compared

Oracle public cloud licensing paths — counting rule, core factor treatment, support, and the buyer watch-out (Oracle Licensing Experts analysis, 2026)
Path	Counting rule	Core factor	Support & rewards	Watch-out
OCI — BYOL	OCPU-based; 1 Processor = 2 OCPUs (EE)	Not used (OCPU meter)	22% continues; Support Rewards $0.25–$0.33	Reconcile entitlements before BYOL claim
AWS / Azure / GCP — BYOL	2 vCPUs = 1 Processor (EE, HT on)	Excluded	22% continues; no Support Rewards	Core-factor assumptions under-license you
AWS / Azure / GCP — License Included	Bundled in hourly rate	Excluded	Bundled; no separate 22% on rented licence	Most expensive per hour at steady state
Standard Edition 2 (any authorized cloud)	≤4 vCPUs = 1 socket; ≤8 vCPUs max	Not applicable (socket count)	22% on owned SE2; 10 NUP per 8 vCPUs min	Any EE option in use voids SE2 compliance

▲ Engagement Result

A Fortune 500 financial-services firm lifted its Oracle Database estate onto Azure sized with the on-premises 0.5 core factor, leaving it under-licensed before a single audit notice arrived. We re-counted every instance against the authorized cloud 2-vCPU rule, moved two qualifying workloads down to Standard Edition 2 inside the 8-vCPU cap, BYOL'd the remainder against reconciled entitlements, and closed the gap on the customer's terms — cutting the projected three-year Oracle cloud-plus-support cost by 38% and removing the exposure entirely. See related Oracle licensing case studies with hard numbers.

Acronyms

Oracle public cloud licensing glossary

Authorized Cloud Environment: Oracle's policy designation for the third-party clouds where its cloud counting rules apply — AWS, Microsoft Azure, and Google Cloud — where a fixed vCPU-to-licence ratio replaces the Core Factor Table.
vCPU (Virtual CPU): The core-thread unit AWS, Azure, and GCP expose; under Oracle's authorized cloud policy two vCPUs equal one Processor licence for Enterprise Edition when hyperthreading is enabled.
OCPU: Oracle Compute Unit: one physical core with two threads, the OCI metering unit; under BYOL on OCI one Processor licence maps to two OCPUs.
Core Factor Table: Oracle's on-premises multiplier scaling licence requirements by processor type; it does not apply in any authorized cloud environment.
BYOL (Bring Your Own License): Applying existing perpetual Oracle Processor or Named User Plus licences to cloud capacity so you pay only the infrastructure rate, not the License Included rate.
License Included: A cloud pricing model bundling the Oracle software licence into a higher hourly rate, used when owned perpetual licences are not applied via BYOL.
Processor Metric: Oracle's capacity-based licence metric; in the cloud the count derives from vCPUs (authorized clouds) or OCPUs (OCI), not physical cores and the core factor.
Named User Plus (NUP): Oracle's user-based licence metric; in authorized clouds Standard Edition 2 carries a minimum of 10 Named User Plus per 8 vCPUs.
Standard Edition 2 (SE2): A lower-cost Oracle Database edition; in authorized clouds an instance of 4 or fewer vCPUs counts as one socket, capped at 8 vCPUs per instance.
Soft Partitioning: Virtualisation-based capacity limiting Oracle does not recognise for reducing licence counts; in authorized clouds the fixed vCPU rule replaces partitioning arguments entirely.
Support Rewards: An Oracle program granting $0.25 of technology support credit per $1 of OCI consumption ($0.33 for ULA customers), redeemable against the on-premises support bill; OCI only.
Annual Technical Support: Oracle's perpetual-licence support fee, charged at 22% of net license value per year, that continues on every licence you BYOL into the public cloud.

FAQ

Oracle public cloud licensing: frequently asked questions

How is Oracle licensed in the public cloud?

On AWS, Microsoft Azure, and Google Cloud, Oracle's authorized cloud environment policy counts 2 vCPUs as 1 Processor licence for Enterprise Edition when hyperthreading is enabled, and 1 vCPU as 1 licence when it is off. The on-premises Core Factor Table does not apply. On Oracle's own OCI, licensing counts OCPUs, where 1 Processor licence under BYOL maps to 2 OCPUs (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026; Oracle BYOL to PaaS FAQ, 2026).

Does the Oracle Core Factor Table apply in the public cloud?

No. In every authorized cloud environment — AWS, Azure, and Google Cloud — Oracle replaces the Core Factor Table with a fixed vCPU-to-licence ratio regardless of the underlying processor model (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026). A workload that licensed at a 0.5 core factor on an Intel server can require more licences in the cloud at the same core count, because the flat 2-vCPU ratio gives no multiplier discount.

What is an Oracle authorized cloud environment?

An authorized cloud environment is Oracle's designation, set in a policy document, for the third-party clouds where its cloud counting rules apply — currently Amazon Web Services, Microsoft Azure, and Google Cloud Platform. Inside these environments a fixed vCPU-to-licence ratio replaces the Core Factor Table. The designation lives in a policy Oracle controls and can revise unilaterally; it is not a term of your signed contract.

How is Oracle Database Standard Edition 2 licensed in the cloud?

In an authorized cloud environment, a Standard Edition 2 instance with 4 or fewer vCPUs counts as 1 socket, and above that every 4 vCPUs, rounded up, equals one socket; SE2 may only run on instances up to 8 vCPUs. By Named User Plus, the minimum is 10 NUP per 8 vCPUs (Oracle, Licensing Oracle Software in the Cloud Computing Environment, 2026). These caps make SE2 a smaller-footprint option than Enterprise Edition in the cloud.

Is Oracle's cloud licensing policy part of my contract?

No. The authorized cloud environment rules sit in a policy document Oracle publishes and can change at will, not in your Oracle Master Agreement or ordering documents. That distinction matters: Oracle can revise the vCPU ratio, and a favourable rule at deployment is not contractually locked unless you negotiate it in. Pin and archive the policy version in force on the day you deploy each workload.

What is the difference between BYOL and License Included in the cloud?

BYOL (Bring Your Own License) applies your existing perpetual Processor or Named User Plus licences to cloud capacity, so you pay only the infrastructure rate; License Included bundles the Oracle software licence into a higher hourly rate. On OCI, BYOL converts 1 Processor licence to 2 OCPUs (Oracle BYOL to PaaS FAQ, 2026). BYOL is materially cheaper when you already own entitlements, but only if you reconcile what you own first.

Does running Oracle on AWS or Azure trigger an audit?

Running Oracle in public cloud does not itself trigger an audit, but it raises audit exposure because misapplied cloud rules are easy for Oracle to find. The most common finding is architects sizing instances with the on-premises Core Factor Table instead of the flat vCPU rule, which under-licenses the estate. Across 600+ Oracle engagements, the average audit claim is 3 to 5 times what the customer actually owes (Oracle Licensing Experts engagement data, 2026).

Does soft partitioning reduce Oracle licences in the public cloud?

No. Soft partitioning never reduced Oracle licence counts on-premises and is irrelevant in an authorized cloud, where the fixed vCPU rule governs the count directly. You license the provisioned vCPUs of each Oracle instance, not a pa

Oracle Licensing Intelligence

Get the weekly briefing Oracle hopes you never read

Audit tactics, negotiation leverage and licensing traps — decoded by former Oracle insiders. Join 2,000+ buyers. No spam, unsubscribe anytime.

Independent of Oracle Corporation. Not affiliated with Oracle.