The Cloud DR Licensing Map Oracle Does Not Publish
Oracle's disaster recovery licensing rules are complex enough on-premises. In cloud environments — where DR architectures are more dynamic, where instances spin up automatically in failover scenarios, and where the distinction between "active" and "passive" is technically blurred — the compliance risk is compounded. Oracle's licensing rules for DR in AWS, Azure, and OCI differ materially from one another, and from on-premises DR provisions. The differences are not published in a single accessible Oracle document. They are assembled from the Oracle Technology Licence and Services Agreement, the Oracle cloud licensing policy documents, the Processor Core Factor Table, and, in some cases, the specific terms of an enterprise's Oracle licence agreement.
An enterprise that applies on-premises DR licensing assumptions to cloud DR architectures, or that assumes AWS DR rules are the same as OCI DR rules, is creating audit exposure that can surface as a multi-million-dollar claim years after the infrastructure decision was made. This guide provides the cloud DR licensing map that prevents that outcome. For the existing Redress guides that cover related Oracle DR topics, see our Oracle cloud DR challenges guide and our Oracle failover licensing guide. For Oracle WebLogic cloud deployment licensing that often accompanies Oracle Database DR decisions, see our Oracle WebLogic cloud guide. For the broader Oracle 23ai context, see our Oracle 23ai licensing guide. Our Oracle Knowledge Hub and advisory services page cover the full Oracle cloud licensing landscape.
Oracle's Baseline DR Rule: The 10-Day Failover Provision
Oracle's standard licence agreements — for on-premises deployment — permit a "failover" environment where Oracle software may run without additional licence for up to 10 days per year in aggregate. This provision is designed for genuine disaster recovery scenarios: the primary environment fails, the standby takes over, and after restoration the standby returns to passive. For organisations whose DR events genuinely last only a few days per incident and occur rarely, this provision provides meaningful cost reduction.
The 10-day provision has three critical constraints that are frequently misunderstood. First, the 10 days are cumulative across the calendar year — if DR failover is tested quarterly (which most enterprise DR governance frameworks require), four quarterly 2-day tests consume the full annual allowance. Second, the provision applies only to licences running on equivalent hardware capacity — a DR environment running on significantly larger hardware than the production environment may not qualify for passive standby treatment even during the 10-day window. Third, the provision does not apply uniformly to all Oracle products — it is most clearly established for Oracle Database but is less explicitly defined for Oracle Middleware products, Oracle applications, and Oracle Cloud at Customer deployments.
Cloud DR Licensing: AWS vs Azure vs OCI — The Critical Differences
| Dimension | AWS | Azure | OCI |
|---|---|---|---|
| Hard partitioning recognition | Not recognised — full physical host counts as licensed capacity unless BYOL physical isolation achieved | Not recognised for standard VMs — Dedicated Host with Oracle BYOL required for sub-capacity | Recognised — OCI is an authorised cloud environment with Oracle's own partitioning rules |
| Sub-capacity licensing availability | Not available on standard EC2 — full physical host PVU applies unless dedicated hardware used | Not available on standard Azure VMs — full physical core count applies without Dedicated Host | Available — OCI OCPU-based licensing counts only the OCPUs allocated to the instance |
| 10-day failover provision | Applies to BYOL deployments, but physical host capacity rules apply — DR on large EC2 instances may require full host licensing | Applies with same limitations — Dedicated Host required to avoid full physical capacity | Applies — and sub-capacity rules mean DR instances on OCI consume fewer licences than equivalent AWS/Azure DR |
| Active Data Guard DR | Full licence required if ADG standby is on standard EC2 — no sub-capacity relief | Full licence required on standard Azure VMs — Dedicated Host needed to limit exposure | ADG standby on OCI qualifies for sub-capacity OCPU licensing; passive standby provisions apply |
| Oracle's BYOL audit posture | Most aggressive — AWS is not an authorised cloud under Oracle's standard cloud policy, creating the largest compliance uncertainty | Less aggressive than AWS — Microsoft and Oracle have a commercial partnership that influences audit treatment | Least risk — OCI is Oracle's own cloud; Oracle cannot credibly audit OCI customers more aggressively than its own platform allows |
AWS: The Highest-Risk Cloud DR Environment for Oracle Licensing
AWS is the most problematic cloud environment for Oracle Database licensing because Oracle has not designated AWS as an "authorised cloud environment" under its standard cloud licensing policy. This means that Oracle's standard Processor Core Factor Table — which reduces the licence count for certain processor types by a "core factor" of 0.5 or 0.25 — does not apply to Oracle software running on AWS infrastructure. Instead, Oracle's audit position for AWS is that every physical core on the underlying host contributes to licence obligation, regardless of the virtual cores allocated to the customer's EC2 instance.
For Oracle Database DR on AWS, this creates a compounding problem: not only does the physical host rule potentially apply (rather than the vCPU count allocated to the instance), but the 10-day failover provision must be tracked rigorously because any Oracle Database usage on AWS beyond passive standby configuration triggers full licence obligation at the physical core rate. Enterprises running Oracle Database DR on AWS without dedicated physical isolation should treat their DR environment as fully licensed — or immediately review the architecture with expert guidance. Our Oracle cloud DR challenges guide covers AWS-specific mitigation architectures in detail.
Assess Your Oracle Cloud DR Licensing Risk
Our Oracle assessment tools include a cloud DR licensing risk calculator — map your DR architecture across AWS, Azure, and OCI against Oracle's applicable rules to identify your compliance exposure.
Start Oracle DR Assessment →Azure: The Nuanced Middle Ground
Oracle's commercial relationship with Microsoft — including the Oracle Database Service for Azure (OracleDB@Azure, an OCI deployment within Azure datacentres) and cross-cloud database connectivity — has created a more nuanced compliance environment than AWS. Azure is not fully equivalent to OCI for Oracle licensing purposes, but the Microsoft-Oracle partnership means that Oracle's audit posture for Azure BYOL deployments is generally less aggressive than for AWS.
The key technical distinction for Azure DR is the Dedicated Host requirement. Standard Azure virtual machine deployments — where the customer is allocated virtual cores on shared physical infrastructure — do not provide the physical isolation that Oracle recognises as enabling sub-capacity licensing. To achieve sub-capacity Oracle Database licensing on Azure (counting only the vCores allocated to the Oracle instance rather than the full physical host), organisations must deploy on Azure Dedicated Host with BYOL Oracle Database. Azure Dedicated Host is more expensive than standard Azure VMs but the sub-capacity licensing saving — which can reduce Oracle licence count by 70-90% versus full physical host counting on large multi-tenant hosts — typically justifies the infrastructure premium for large Oracle Database deployments.
For Oracle Database DR specifically on Azure, the architecture decision is: Dedicated Host (higher infrastructure cost, sub-capacity licensing relief, lower Oracle audit risk) versus standard VMs (lower infrastructure cost, full physical host Oracle licensing, higher audit risk). The right answer depends on the Oracle licence obligation at stake and the database workload size.
Need Expert Oracle Cloud DR Licence Review?
Our Oracle advisory team reviews cloud DR architectures across AWS, Azure, and OCI — identifying licence exposure, recommending compliance-safe configurations, and representing organisations in Oracle DR-related audit disputes.
Book an Oracle Cloud Advisory Call →OCI: The Path to Lowest Oracle Cloud DR Licensing Risk
Oracle Cloud Infrastructure is Oracle's own authorised cloud environment, and as such it provides the most favourable licensing mechanics for Oracle Database DR deployments. OCI uses an OCPU (Oracle CPU) licensing model under which Oracle Database licence obligation is calculated based on the OCPUs allocated to the database instance — not the underlying physical processor count. This sub-capacity approach means that an Oracle Database DR instance on OCI allocated 4 OCPUs requires 4 OCPUs' worth of Oracle Database licences, regardless of the physical server beneath it.
OCI also qualifies for Oracle's Support Rewards programme — as covered in our Oracle Support Rewards guide — meaning that OCI DR spend generates credits against on-premises support fees. For enterprises with significant on-premises Oracle support obligations, using OCI for DR creates a secondary benefit: the OCI consumption that funds the DR architecture simultaneously generates support cost credits, partially offsetting the OCI infrastructure cost.
Active Data Guard (ADG) in OCI DR architectures qualifies for sub-capacity OCPU licensing for the standby instance when the standby is genuinely passive. This is in contrast to AWS and Azure standard VM environments where ADG standby instances face full physical host licence exposure. For complex Oracle Database environments using ADG for DR — particularly those running Oracle Database 23ai — OCI provides the most commercially defensible DR architecture. To discuss your specific Oracle cloud DR architecture and licensing risk, book a confidential advisory call with our Oracle team.