Oracle Database in AWS, Azure, OCI, and Google Cloud carries different counting rules per environment. The buyer side reference. The BYOL math. The authorized cloud environment table. The audit traps.
Oracle Database in the cloud is licensed under three documents. The Oracle Licensing and Services Agreement. The Cloud Policy. The Authorized Cloud Environment policy. The counting rules are vendor specific and quietly punitive. Read the counting rule first, then design the deployment.
This article reads as a buyer side reference. Pair it with the Oracle ULA decision framework, the BYOL comprehensive guide, the Oracle multicloud licensing piece, and the Oracle advisory practice.
Oracle generates over half of audit findings on cloud deployment misalignment. The Authorized Cloud Environment counting rule, the LMS scripts, and the Cloud Policy interact in non obvious ways. The cost of a wrong deployment design is rarely under seven figures on enterprise estates.
The Authorized Cloud Environment list is Oracle's published group of public cloud providers where the simplified counting rule applies. AWS, Azure, and historically certain other providers are on the list. OCI sits outside the list and uses its own counting rule.
The rule does not apply on private clouds, on hosted private clouds, on dedicated tenant hardware, on bare metal in any cloud, on Google Cloud, on Alibaba Cloud, or on any provider not listed in the policy. Those environments default to the on premises core factor rule.
Bring Your Own License lets the buyer apply existing perpetual entitlement or ULA capacity against the cloud workload. The math differs by cloud because the counting rule differs.
| Cloud | Counting rule | Processor licenses needed | Notes |
|---|---|---|---|
| AWS EC2 | Authorized Cloud Environment | 50 | 2 vCPU per license, hyperthreading on |
| Azure | Authorized Cloud Environment | 50 | Same as AWS |
| OCI | OCPU rule | 50 | 2 vCPU per OCPU, one license per OCPU |
| Google Cloud | On premises core factor | 50 to 100 | Depends on core factor table and negotiated terms |
| AWS bare metal | Core factor | 50 to 100 | Treated as on premises hardware |
| Azure Dedicated Host | Core factor | 50 to 100 | Treated as on premises hardware |
The OCI Compute OCPU contains two virtual CPUs with hyperthreading on, which Oracle treats as one full processor license. A 100 vCPU workload on OCI consumes 50 OCPU, which consumes 50 Oracle Database Enterprise Edition processor licenses under BYOL.
OCI, AWS, and Azure all support Oracle Database BYOL. OCI also supports license included Database services where the licenses are bundled in the consumption rate. The choice between routes turns on entitlement availability, on workload predictability, and on the wider commercial relationship.
| Dimension | OCI | AWS | Azure |
|---|---|---|---|
| Counting rule | OCPU one to one | 2 vCPU equals 1 license | 2 vCPU equals 1 license |
| Native database service | Autonomous Database, Exadata Cloud, Base Database | RDS for Oracle, EC2 BYOL | Oracle Database at Azure, Azure VM BYOL |
| License included option | Yes on multiple services | RDS for Oracle | No native license included |
| BYOL discount | Universal Credit Model | Standard EC2 pricing | Standard VM pricing |
| Exadata access | Native | Via Oracle Database at Azure or Oracle Database at AWS | Via Oracle Database at Azure |
| Audit posture | Direct Oracle control | Oracle audits via LMS | Oracle audits via LMS |
The Oracle audit team runs three reliable cloud traps. Each one catches a measurable share of enterprise estates on first audit.
Oracle Software Investment Logic includes a ten day failover allowance per calendar year for disaster recovery environments. The clause is in the LMS scripts but not in the standard contract. Document it in writing in the order form before relying on it.
The cloud deployment is the leverage point for the wider Oracle contract. Two levers matter most. The first is the Authorized Cloud Environment counting rule confirmation. The second is the ten day failover written allowance.
The eight step checklist below moves the Oracle Database cloud estate from an audit risk to a defended deployment.
No. Google Cloud is not listed in the Oracle Authorized Cloud Environment policy. Workloads on Google Cloud default to the on premises core factor counting rule, which is materially more expensive per vCPU than the Authorized Cloud Environment rule. Buyers running Oracle on Google Cloud should negotiate a written counting rule in the contract before deploying production.
OCI is typically lower total cost of ownership for Oracle Database workloads. The OCPU counting rule, the Universal Credit Model discount, and native Exadata access all favor OCI. AWS becomes competitive when the wider cloud strategy anchors on AWS and the broader AWS footprint savings offset the Oracle premium. Run the math on the specific workload mix.
Standard Edition 2 counts by socket equivalent on Authorized Cloud Environment, with four virtual CPUs treated as one socket and a maximum of two sockets per database server. The Standard Edition 2 product itself carries an 8 socket maximum on the on premises rule. The cloud rule differs and the buyer should verify the current policy at quote time.
Yes. BYOL requires active Oracle Premier Support on the entitlement being applied. Lapsed or terminated support voids BYOL eligibility. The buyer must hold the support contract for every license carried into the cloud deployment. Some buyers carry partial support to maintain BYOL eligibility on the deployed portion of the entitlement.
Yes. The Oracle Unlimited License Agreement covers cloud deployments during the ULA term. At certification, the buyer counts the deployed cloud footprint against the Authorized Cloud Environment counting rule for AWS and Azure, against the OCPU rule for OCI, and against the core factor rule for unlisted clouds. ULA certification math should be modeled before the ULA exit.
Oracle has revised the Authorized Cloud Environment policy four times since 2017. The changes have been unilateral and have applied to existing deployments. Buyers should document the counting rule in the order form at signature to lock the rule for the contract term, and refresh the documentation at every contract amendment.
Redress runs the cloud licensing work as a six to eight week assessment. The work pulls the deployment baseline, maps every instance to the counting rule, scores the entitlement, identifies the snapshot footprint, and drafts the four contract levers. The deliverable is a defended cloud licensing position and the order form language.
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 Database cloud licensing decision. Authorized Cloud Environment counting rules, OCI versus AWS versus Azure math, audit trap mapping, and the contract clause set.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for Oracle Database customers running BYOL, ULA, and license included routes across OCI, AWS, Azure, and Google Cloud.
Open the white paper in your browser. Corporate email only.
Open the Paper →The trailing audit pulled the cloud deployment first. We had documented the Authorized Cloud Environment counting rule in the order form, scoped the LMS data request to the in production environments, and capped the audit data window at the agreed contract term. The settlement landed at zero new license purchase.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Authorized Cloud Environment policy changes, OCI commercial trends, BYOL conversion patterns, ULA certification math, and the wider Oracle commercial leverage 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.
