Oracle multicloud, one license under three rulebooks
The same perpetual Oracle license is governed by three different rulebooks depending on where it lands, and only one of them is a contract. This is the portability question: which entitlements can move to which cloud, at what conversion, and what quietly stops working on the way.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 20 to 28 multicloud engagements advised 2024 to 2025.
Executive summary
Who operates the infrastructure decides the rulebook.
Hyperscaler compute runs under the Authorized Cloud Environments policy, educational only by Oracle's own language; Oracle operated services inside those clouds, Oracle Database at AWS, at Azure, at Google Cloud, run under contractual service descriptions.
And native OCI runs under your order. The same Enterprise Edition license lands under a contract in one place and under an educational policy a few racks away, and buyers who assume one set of cloud rules get the conversion wrong in at least one of the three.
The conversions differ by product and destination. One EE Processor license covers two vCPUs on hyperscaler compute with multithreading on, up to two OCPUs on Exadata Database Service at AWS, up to eight ECPUs on Autonomous for EE and sixteen for Standard Edition.
In our engagements, vCPU counts on the target shape were misjudged in roughly half the moves, swinging the requirement 25 to 60 percent, because a case built on one Processor equals one cloud unit is wrong before it starts.
Eligibility breaks quietly. BYOL requires active Oracle support, so a license moved to third party support stops qualifying, and eligibility broke in close to a third of our cases because support had lapsed or moved.
Application specific and embedded licenses, ASFU and ESL, carry their restrictions with them and mostly do not travel at all: nobody had checked whether the entitlement type itself was portable, only whether the numbers worked.
The destination decides what the spend earns back. OCI and the Oracle operated multicloud services accrue Support Rewards at 25 cents per consumption dollar, 33 for ULA holders, against the technology support invoice; the same database on plain EC2 or an Azure VM earns nothing.
That is a real term in the destination comparison and it is almost never in the migration business case.
The three regimes, and what governs each
| Where the workload runs | Governed by | Contractual? | Counting basis |
|---|---|---|---|
| AWS EC2, RDS, Azure, Google Cloud compute | The Authorized Cloud Environments policy | No: Oracle states it is educational only | vCPU: two per license with multithreading, one without |
| Oracle Database at AWS, Azure, or Google Cloud | Oracle's service descriptions for that service | Yes: contract documents | OCPU or ECPU, published per service |
| Native OCI | Your order and the Universal Credits service descriptions | Yes | OCPU or ECPU |
| Everything else, including private cloud | Your original license agreement | Yes | Physical cores with the core factor |
The policy sentence that changes your risk profile.
The ACE document states it is for educational purposes only, may not be incorporated into any contract, and commits Oracle to nothing: the rules your cloud position rests on can change, and the version in force at audit is the version published then, not the one you modeled against.
The defense is not to argue with the policy; it is to get the specific conversion you rely on written into an ordering document or amendment for the products that matter most.
The conversion table, one EE Processor license by destination
| Destination | Unit | Published conversion | Source type |
|---|---|---|---|
| AWS, Azure, or Google Cloud compute | vCPU | 2 vCPUs with multithreading on, 1 without | Policy, not contractual |
| Exadata Database Service at AWS | OCPU | Up to 2 OCPUs, with 25 NUP for the same | Service description |
| Autonomous services, Enterprise Edition | ECPU | Up to 8 ECPUs | Service description |
| Autonomous services, Standard Edition | ECPU | Up to 16 ECPUs | Service description |
| On premises, unchanged | Physical core | The core factor applies | Your license agreement |
The Oracle multicloud and Universal Credits brief
The commitment vehicles above the portability question: MUC versus Universal Credits, the credit expiry mechanics, and the sizing discipline that survives the move.
Get the white paper →What travels, and what quietly stops working
Travel cleanly: full use Processor and Named User Plus licenses on active support, at the destination conversion; options and packs, provided every processor running the base program licenses the option too; Enterprise Edition, which carries no vCPU ceiling.
And Java subscriptions, counted by employee and indifferent to where code runs.
Do not travel: application specific full use licenses and embedded licenses, whose restrictions ride with them; SE2 beyond its eight vCPU ceiling; and any license whose support has moved, because BYOL requires active Oracle support and third party support ends eligibility.
The counting mechanics in each destination sit in the cloud environments guide, and portability runs both ways: coming back on premises restores the core factor, which can cut the requirement the cloud inflated.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across multicloud engagements, 2024 to 2025
Across roughly 20 to 28 Oracle multicloud engagements Fredrik Filipsson advised in 2024 and 2025, the licensing surprise almost always arrived after the workload had already moved:
Target shapes counted wrong, swinging the license requirement 25 to 60 percent either way.
Support lapsed or moved to a third party, ending the bring your own license right nobody rechecked.
The governance finding compounds the rest: a license carried into an Oracle operated multicloud service is recorded against an Oracle service description while the invoice arrives from a hyperscaler marketplace, so entitlement records and billing records live in different systems.
And the AWS variant's credits document adds that prepaid unused amounts are forfeited at the end of the yearly credit period.
The Support Rewards guide carries the earn back mechanics, and the MUC versus Universal Credits comparison the commitment vehicle decision that sits above all of it.
Your first five moves
- Map every workload to its rulebook: policy, service description, or order, because the regime decides the conversion before the numbers do.
- Confirm the ratio per product, in writing, before the business case signs: the conversions differ by product and service tier.
- Check entitlement portability, not just arithmetic: ASFU, ESL, SE2 ceilings, and support status all break moves the spreadsheet approved.
- Count Support Rewards in the destination comparison, 25 to 33 cents per dollar on one side and zero on the other.
- Write the conversions you depend on into an ordering document, because the policy can move and your contract cannot be moved for you. The Oracle cloud negotiation practice runs the position with you.
Frequently asked questions
What rules govern Oracle licenses in the cloud?
One of three rulebooks, decided by who operates the infrastructure: hyperscaler compute runs under the non contractual Authorized Cloud Environments policy counting vCPUs, Oracle operated services like Oracle Database at Azure run under contractual service descriptions counting OCPUs or ECPUs.
And native OCI runs under your order.
Private clouds and unnamed providers stay on the original agreement with the core factor.
How do Oracle license conversions differ by cloud?
Materially: one EE Processor license covers two vCPUs on AWS, Azure, or Google Cloud compute with multithreading enabled, up to two OCPUs on Exadata Database Service at AWS, up to eight ECPUs on Autonomous for Enterprise Edition, and sixteen for Standard Edition.
The ratios come from different documents with different legal weight, so confirm each one in writing per product.
Does third party support affect Oracle BYOL?
It ends it: bring your own license requires active Oracle support, so a license moved to third party support stops qualifying, and in close to a third of our engagements eligibility had broken because support lapsed or moved.
The BYOL check belongs before the migration plan, not after the workload lands.
Do all Oracle license types move to the cloud?
No. Full use Processor and NUP licenses on active support travel at the destination conversion, and Java subscriptions travel freely since they count employees.
Application specific full use and embedded licenses carry their restrictions with them and mostly cannot move, and SE2 hits its eight vCPU ceiling. The entitlement type check is the one nobody runs.
What are Oracle Support Rewards worth in a multicloud decision?
25 cents per dollar of OCI and Oracle operated multicloud consumption, 33 cents for ULA holders, accrued against the technology support invoice.
The same database on plain EC2 or an Azure VM earns nothing, which makes the rewards a real term in the destination comparison that migration business cases almost never include.
Is Oracle's cloud policy binding on Oracle?
No: it states it is educational only, may not be incorporated into any contract, and commits Oracle to no terms, so the rules can change and the audit runs on the version published then.
Both directions of that cut the same way: get the specific conversions you rely on written into an ordering document or amendment.
