Authorized Cloud Environment rules across AWS, Azure, Google Cloud, and OCI. vCPU counting, hyper threading, license mobility, and the buyer side framework for the next cloud migration.
Oracle multicloud licensing in 2026 has four destinations. AWS. Azure. Google Cloud. Oracle Cloud Infrastructure. Each carries a distinct counting rule, a distinct support posture, and a distinct cost trajectory. The Authorized Cloud Environment construct is the legal frame. The vCPU counting math is the commercial frame.
This article reads as a buyer side framework. Use it with the Oracle practice, the OCI licensing piece, the Cloud at Customer guide, the Database licensing calculator, and the Oracle license types reference.
Enterprise Oracle estates moved off purely on premises footprints between 2020 and 2025. The destination splits between four hyperscalers and Oracle Cloud Infrastructure. The licensing rules differ on each cloud. A buyer who deploys to AWS using OCI counting math triples the audit exposure on the same workload.
The Oracle Authorized Cloud Environment policy is a published document. The policy names AWS, Microsoft Azure, and Google Cloud as authorized destinations for Oracle BYOL. The policy sets the counting rule on hyper threaded x86 instances. The policy excludes other public clouds and most private clouds.
The ACE policy does not cover Oracle applications, Java SE subscriptions, Oracle Linux, or Oracle Engineered Systems software. Each of these runs under separate cloud licensing rules. Read the product specific cloud licensing page before any deployment.
The ACE counting rule is the commercial heart of the policy. On hyper threaded x86 instances two vCPUs equal one Oracle Processor. On non hyper threaded instances one vCPU equals one Oracle Processor. The rule applies to AWS EC2, Azure Virtual Machines, and Google Cloud Compute Engine.
| Instance type | vCPUs | Hyper threaded | Oracle Processor count |
|---|---|---|---|
| AWS m5.4xlarge | 16 | Yes | 8 Processors |
| AWS m5.metal | 96 | No, bare metal | 96 Processors at 0.5 Core Factor equals 48 |
| Azure D16s_v5 | 16 | Yes | 8 Processors |
| GCP n2 standard 16 | 16 | Yes | 8 Processors |
| OCI VM.Standard3.Flex | 16 OCPU | OCPU equals one physical core | 16 Processors at OCI native math |
AWS hosts Oracle Database under BYOL on EC2 instances and under License Included on Amazon RDS for Oracle. The BYOL route requires underlying on premises Oracle support. The License Included route bundles the Oracle license fee into the RDS hourly rate.
Azure hosts Oracle Database under BYOL on Azure Virtual Machines. Azure also runs Oracle Database services through the OCI Interconnect partnership. Oracle Database at Azure runs the database in OCI managed regions inside the Azure data center. The licensing rules follow the Oracle service agreement.
Google Cloud hosts Oracle Database under BYOL on Compute Engine. Google Cloud also runs Oracle Database services through the Oracle and Google partnership for Oracle Database at Google Cloud. The BYOL path follows the standard ACE rules. The service path follows the Oracle service agreement.
Oracle Cloud Infrastructure runs on a different counting math. One OCPU equals one physical core which equals one Oracle Processor. The OCI native math is half the count on hyper threaded x86 instances at the same compute scale. OCI BYOL is the most license efficient destination for an Oracle Database workload.
The table below sits at the core of the multicloud decision. Read every row before committing to a cloud destination for the Oracle workload.
| Cloud | BYOL counting | License Included available | Service offering |
|---|---|---|---|
| AWS | Two vCPU equals one Processor | RDS for Oracle, Standard Edition 2 only | No native Oracle Database service |
| Microsoft Azure | Two vCPU equals one Processor | No, Azure does not bill Oracle license | Oracle Database at Azure via OCI Interconnect |
| Google Cloud | Two vCPU equals one Processor | No, GCP does not bill Oracle license | Oracle Database at Google Cloud |
| Oracle Cloud Infrastructure | One OCPU equals one Processor | Yes on Database Cloud Service | Database Cloud Service, Autonomous Database |
On a 32 vCPU equivalent workload AWS counts 16 Oracle Processors at Core Factor 0.5 equals 8 Processors. OCI counts the same workload at 16 OCPUs at one to one equals 16 Processors. The OCI count is higher but the underlying support and operating efficiency on Exadata is structurally lower cost. Run the three year TCO before choosing.
The eight step checklist below moves an Oracle cloud migration from a slide deck to a defensible licensing position. Open it before any cloud deployment scope is locked.
No formal approval is required. The Authorized Cloud Environment policy is the standing authorization for AWS, Microsoft Azure, and Google Cloud. The buyer must hold active Oracle support on the deployed Processor count. The deployment must use the published counting rules and stay inside the ACE product list.
BYOL ends. The Authorized Cloud Environment policy requires active Oracle support on the licenses brought to the cloud. Drop the support and the cloud deployment runs out of compliance. The workload either moves to License Included or moves off Oracle.
No. Oracle Database at Azure runs in OCI managed cloud regions co located inside Azure data centers via the OCI Interconnect partnership. The service agreement defines the licensing. The construct is closer to OCI Database Cloud Service than to BYOL on an Azure Virtual Machine.
The Oracle Core Factor Table applies to BYOL on the hyperscalers. The rule is two vCPUs equal one Processor on hyper threaded x86 already accounts for the Core Factor of 0.5. On bare metal instances the underlying physical cores apply with the Core Factor. Confirm the calculation at the time of deployment.
Java SE runs on its own subscription model since the 2023 universal subscription change. The Authorized Cloud Environment policy does not cover Java SE. A buyer running Java SE on AWS or Azure needs the Java SE Universal Subscription separately, sized to the Employee metric on the enterprise.
OCI uses the OCPU as the native metric. One OCPU equals one physical core which equals one Oracle Processor. The OCI count is higher on the same vCPU equivalent workload, but the underlying compute and the Exadata service economics are structurally different. Run the three year total cost of ownership before choosing.
Redress runs the Oracle multicloud assessment as a four to six week workstream. The work inventories every Oracle workload, maps the deployment to the target cloud, computes the vCPU to Processor count on each, prices BYOL versus License Included, and lands the cloud licensing position for each workload.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the Oracle Unlimited License Agreement decision. Certification math, multicloud deployment scope, renewal posture, and the certify out path under BYOL.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for Oracle Database, Java, and applications customers running on AWS, Azure, GCP, or OCI.
Open the white paper in your browser. Corporate email only.
Open the Paper →We split a 320 core Oracle Database footprint across OCI Exadata, AWS EC2 BYOL, and RDS License Included. The OCI block carried the high availability workloads. The AWS block carried the variable dev test estate. The cloud licensing position landed 31 percent below the projected three year envelope.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Multicloud BYOL signals, OCI Interconnect movement at Azure and Google Cloud, OCPU counting patterns, and the wider Oracle commercial signals across every renewal cycle.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
