BYOL vs. Licence-Included on Azure
Choosing the Right Oracle Licensing Strategy for Cost, Control, and Compliance
📖 This article is part of the Oracle OCI & Cloud Infrastructure Licensing pillar series. Related guides include BYOL vs. Licence-Included on OCI, Oracle BYOL — Comprehensive Guide, and Oracle Licensing on Azure — Full Guide.
The Two Models: BYOL and Licence-Included
Bring Your Own Licence (BYOL) means deploying Oracle software on Azure using perpetual licences you already own or purchase separately from Oracle. Azure is an Oracle-authorised cloud environment, so Oracle permits BYOL deployment. You pay Microsoft only for Azure infrastructure (compute, storage, networking). Oracle receives nothing from Microsoft. You maintain your existing Oracle support contract and remain subject to Oracle’s standard audit rights.
Licence-Included means the Oracle software licence is bundled into the service price. You pay a single hourly or monthly rate that covers both infrastructure and the Oracle licence. There is no separate licence purchase, no Oracle support contract to maintain, and no Oracle audit exposure for that specific deployment. The primary vehicle for this on Azure is Oracle Database@Azure, launched in late 2023 as a joint Microsoft-Oracle managed service.
🏛️
BYOL: You Own the Licence
Perpetual right to use Oracle software. You control the asset, pay annual support (22%), and can redeploy across environments. Subject to Oracle audits.
💳
Licence-Included: You Rent
Time-bound usage right included in the hourly rate. No upfront purchase, no support contract, no audit exposure. When you stop paying, the right ends.
📊
BYOL: Lower Long-Term Cost
Upfront investment plus annual support. Over multi-year periods, total cost is typically 25–40% lower than cumulative licence-included charges for 24/7 workloads.
⚡
Licence-Included: Maximum Flexibility
Start and stop at will. No commitment beyond usage. Ideal for variable, short-term, or experimental workloads where the total run-time is under 12–18 months.
“The BYOL vs. licence-included decision is fundamentally a question of time horizon and utilisation. If you know the workload will run continuously for more than 18 months, BYOL almost always wins financially. If the workload is variable, temporary, or experimental, licence-included avoids the risk of purchasing an expensive perpetual asset you may not need long-term.”
BYOL on Azure: Rules, Requirements, and Cost Structure
Azure is listed in Oracle’s “Licensing Oracle Software in the Cloud Computing Environment” policy as an authorised cloud provider. This means you can deploy Oracle Database, Middleware, and Applications on Azure VMs using your existing perpetual licences without requiring special permission from Oracle.
| Azure VM Size | vCPUs | Oracle DB EE Licences Required | List Licence Cost | Annual Support (22%) |
|---|---|---|---|---|
| E2s_v5 | 2 | 1 Processor | $47,500 | $10,450 |
| E4s_v5 | 4 | 2 Processor | $95,000 | $20,900 |
| E8s_v5 | 8 | 4 Processor | $190,000 | $41,800 |
| E16s_v5 | 16 | 8 Processor | $380,000 | $83,600 |
Oracle counts 2 Azure vCPUs = 1 Processor licence. On-premises core factors do NOT apply. All allocated vCPUs count, regardless of actual utilisation.
Key BYOL requirements and considerations:
- Active Oracle Support: Licences must be under active support to be eligible for BYOL on Azure. Running Oracle on an unsupported licence in the cloud violates Oracle’s terms and creates compliance exposure.
- No core factor: Oracle’s on-premises core factor table (which reduces licence requirements for certain processor types) does not apply in any public cloud, including Azure. Every vCPU counts at the flat 2:1 ratio.
- Named User Plus (NUP): NUP licensing is permitted on Azure, subject to Oracle’s standard minimums (25 NUP per Processor for Enterprise Edition). NUP can be cheaper for systems with a small, defined user population, but the minimum-per-Processor floor often makes Processor licensing more practical for production workloads.
- VM resizing risk: If you vertically scale an Azure VM to more vCPUs (e.g., upgrading from E4s to E8s for performance), your Oracle licence requirement doubles. This is a common compliance trap. Operations teams resize VMs without notifying the licensing function. Implement Azure Policy to restrict Oracle-tagged VMs to approved sizes.
BYOL Financial Profile
The BYOL cost profile is front-loaded: a large capital expenditure for the licence purchase, followed by a relatively stable annual support payment. Over time, the cumulative BYOL cost grows slowly (support only), while licence-included costs grow linearly with usage hours. The break-even point — where cumulative BYOL cost equals cumulative licence-included cost — typically falls between 12 and 24 months for 24/7 workloads, depending on the specific Oracle product and Azure service pricing.
Evaluate Your Oracle Cloud Strategy: Our free Oracle Cloud Licensing Risk Assessment helps you identify compliance gaps and cost savings across BYOL and licence-included deployments.
Start AssessmentLicence-Included on Azure: Oracle Database@Azure
Oracle Database@Azure is the primary licence-included option for Oracle on Azure. It provides Oracle Exadata-based database infrastructure running natively within Azure data centres, managed by Oracle but provisioned and billed through Azure.
Licence-Included
Best for Variable & Short-Term Workloads
Oracle licence cost is embedded in the hourly OCPU rate. No perpetual licence purchase. No separate Oracle support contract. Billing stops when the database is stopped or terminated. Ideal for dev/test, seasonal workloads, and projects with a defined end date.
BYOL on DB@Azure
Best for Existing Licence Holders
Bring your perpetual licences to the managed service. Microsoft charges a lower infrastructure-only rate (no Oracle licence premium). You continue paying Oracle support separately. Provides managed-service benefits at BYOL cost.
IaaS BYOL
Best for Full Control
Deploy Oracle on standard Azure VMs with your own licences. Maximum architectural flexibility — you choose the OS, storage, networking, and patching schedule. No managed-service convenience, but no managed-service constraints either.
The licence-included model eliminates Oracle audit exposure for the covered deployment because Oracle’s licence is provided through the service agreement, not through a customer-owned perpetual licence. This is a significant compliance advantage for enterprises that want to minimise Oracle audit risk while still running Oracle workloads.
However, licence-included pricing carries a substantial premium for steady-state workloads. Over a 3-year continuous run, the cumulative licence-included cost typically exceeds the equivalent BYOL cost (licence purchase + support) by 30–50%. The premium pays for flexibility, managed-service convenience, and the absence of a capital commitment — but CIOs must model the numbers explicitly to determine whether that premium is justified for each workload.
Cost Comparison: 3-Year and 5-Year TCO Models
The following model compares BYOL and licence-included costs for an Oracle Database Enterprise Edition deployment on an 8-vCPU Azure instance running 24/7.
| Cost Component | BYOL (IaaS VM) | Licence-Included (Database@Azure) |
|---|---|---|
| Upfront licence | $190,000 (4 Processor × $47,500) | $0 |
| Year 1 support | $41,800 | Included in hourly rate |
| Year 1 Oracle software cost | $41,800 (support only) | ~$140,000 (estimated hourly rate × 8,760 hrs) |
| 3-year total (Oracle only) | $315,400 | ~$420,000 |
| 5-year total (Oracle only) | $399,000 | ~$700,000 |
| Azure infrastructure | ~$25,000/year (separate) | Included in service rate |
At the 3-year mark, BYOL saves approximately $105,000 (25%) compared to licence-included. By year 5, the savings grow to approximately $301,000 (43%) because the BYOL licence cost is fully amortised and only annual support continues, while licence-included charges accumulate linearly.
Mini Case Study — Financial Services Firm: $420K Saved by Converting Licence-Included to BYOL
Situation: A financial services company deployed Oracle Database EE on Database@Azure in licence-included mode for a new trading analytics platform. After the first year, the system was running 24/7 and the annual Oracle cost had reached $145,000.
Analysis: Independent TCO modelling showed that purchasing 4 Processor licences ($190,000 at negotiated discount of $152,000) and switching to BYOL mode on Database@Azure would save $420,000 over the remaining 4 years of the projected system life.
Result: The firm purchased BYOL licences, converted to BYOL pricing on Database@Azure, and redirected the savings to fund additional Azure infrastructure for a secondary DR environment.
Lesson: Start with licence-included for uncertain workloads. Once a workload stabilises as 24/7 production, model the BYOL conversion — the financial case is almost always compelling beyond the 18-month horizon.
Break-Even Sensitivity Analysis
The break-even point shifts based on utilisation. For a workload running 24/7, break-even occurs at approximately 14–20 months. For a workload running only during business hours (approximately 2,000 hours/year), the break-even point extends to 4–6 years — making licence-included the better choice. For dev/test environments that run fewer than 1,000 hours annually, licence-included is almost always cheaper than purchasing perpetual licences. CIOs should model each workload’s expected utilisation pattern individually rather than applying a blanket BYOL or licence-included policy across all Oracle deployments.
Compliance and Audit Considerations
The licensing model you choose determines your Oracle audit exposure on Azure.
1
BYOL: Full Oracle Audit Exposure
BYOL deployments are subject to Oracle’s standard audit rights. Oracle can request evidence of licence allocation, Azure VM configurations (vCPU counts), and deployed options/packs. Common audit findings on Azure BYOL include: VMs resized to larger instances without corresponding licence adjustments, options enabled on the database that are not separately licensed, and developers spinning up Oracle VMs in non-production subscriptions without licence coverage.
2
Licence-Included: No Direct Oracle Audit Exposure
Deployments on Database@Azure in licence-included mode are covered by the service agreement. Oracle’s licence is provided through Microsoft, not through a customer-owned perpetual licence. This eliminates the risk of Oracle auditing those specific deployments. However, if you run other Oracle software on Azure VMs under BYOL alongside licence-included Database@Azure, Oracle can still audit the BYOL deployments.
3
Mixed-Model Risk: Double-Paying
The most common compliance mistake in mixed environments is accidentally double-paying — running Oracle on a licence-included service while also allocating BYOL licences to the same instance. This does not create audit risk, but it wastes money. Equally, running Oracle on a standard Azure VM without allocating BYOL licences (assuming licence-included covers it) creates compliance risk — IaaS VMs are not licence-included. Maintain a clear register of which deployment model applies to each Oracle instance.
“The audit risk differential between BYOL and licence-included is one of the most underappreciated factors in the Oracle-on-Azure decision. For enterprises that have historically experienced Oracle audit pressure — particularly those with complex, distributed Azure estates — the compliance simplification of licence-included can be worth the premium, even when the raw TCO favours BYOL.”
Concerned About Oracle Audit Risk on Azure? Our Oracle Audit Risk Assessment identifies compliance gaps across your cloud and on-premises estate before Oracle does.
Start AssessmentHybrid Strategy: Combining BYOL and Licence-Included
Most enterprises benefit from a hybrid approach rather than committing entirely to one model. The decision framework is straightforward: match the licensing model to the workload’s utilisation pattern and strategic importance.
🎯 Workload-Based Licensing Decision Framework
→
24/7 production, >18-month horizon → BYOL
The financial case is clear. Purchase (or reallocate existing) perpetual licences and deploy on Azure VMs or Database@Azure BYOL mode.
→
Business-hours only (8×5), stable → Model the break-even
At ~2,000 hours/year, licence-included may still win over a 3-year period. Run the numbers for your specific Oracle product and Azure pricing.
→
Dev/test, <1,000 hours/year → Licence-included
The cost of a perpetual licence is almost never justified for intermittent non-production use.
→
Short-term project (<12 months) → Licence-included
Avoid capital commitment for temporary workloads. Convert to BYOL if the project extends beyond the break-even horizon.
→
Uncertain duration or variable → Start licence-included
Monitor actual usage for 6 months. If the workload stabilises as steady-state, model the BYOL conversion.
→
Disaster recovery standby → Evaluate OCI
OCI’s licence-included pay-per-hour model is often cheaper than either Azure BYOL or Azure licence-included for DR instances that run only during testing or failover. See Oracle on Azure for HA & DR.
Enterprises with large Oracle estates on Azure should conduct an annual portfolio review — categorising every Oracle deployment by utilisation pattern and comparing the actual cost against the alternative model. Workloads that started as temporary often become permanent. Dev/test environments that ran continuously may now be dormant. The optimal licensing model shifts as usage patterns change, and failing to adjust creates either unnecessary cost (paying licence-included for 24/7 production) or unnecessary compliance risk (running unlicensed Oracle on Azure VMs).
Contract and Procurement Considerations
When deploying Oracle on Azure under BYOL, ensure your Oracle contract explicitly recognises cloud deployment rights. While Oracle’s public policy authorises Azure BYOL, obtaining written confirmation in your ordering document or master agreement eliminates any ambiguity during audits. Key contract provisions to negotiate include: explicit cloud deployment authorisation, confirmation that the 2 vCPU = 1 Processor counting rule applies, and the right to reassign licences between on-premises and Azure environments without restrictions or waiting periods. See Oracle Contract Negotiation Service for expert support.
For licence-included deployments on Database@Azure, review the Azure terms of service and the Oracle-Microsoft service agreement to understand liability boundaries, data sovereignty commitments, and support escalation paths. Database@Azure is a joint service — understanding which entity (Microsoft or Oracle) is responsible for infrastructure, patching, and support ensures you have clear escalation paths when issues arise.
Enterprises contemplating large-scale Oracle-on-Azure migrations should also evaluate whether an Oracle ULA (Unlimited Licence Agreement) could provide more favourable economics than purchasing individual licences. A ULA grants unlimited deployment rights for a defined product set during the agreement term, followed by a certification that quantifies your deployed licences. This can be advantageous for enterprises expecting significant Oracle growth on Azure — the ULA covers all BYOL deployments during the term, and the certification locks in the licence count at the end.
Strategic Recommendations for CIOs
🎯 Oracle-on-Azure Licensing Checklist
✓
Model TCO for every Oracle workload
Compare BYOL vs. licence-included over 3–5 years with realistic utilisation assumptions. Do not apply a blanket policy across all workloads.
✓
Use BYOL for 24/7 production
The financial advantage is clear and grows with time. Reallocate underutilised on-premises licences where possible.
✓
Use licence-included for dev/test and short-term
Avoid committing capital for temporary or intermittent workloads.
✓
Monitor and convert
Review licence-included deployments every 6 months. Convert to BYOL when workloads stabilise beyond the break-even horizon.
✓
Restrict Azure VM sizes for Oracle
Implement Azure Policy to prevent operations teams from resizing Oracle VMs beyond licensed vCPU counts.
✓
Maintain a licence-to-VM register
Document which Oracle licences are allocated to which Azure VMs. Update immediately after any change.
✓
Negotiate cloud rights in Oracle contracts
Obtain explicit Azure BYOL authorisation, vCPU counting confirmation, and reassignment flexibility in writing.
✓
Evaluate Database@Azure BYOL mode
Combines managed-service convenience with BYOL economics. Best of both worlds for licence holders who want operational simplicity.
✓
Consider OCI for DR
Oracle’s licence-included per-hour pricing on OCI is often significantly cheaper than either Azure model for intermittent DR.
✓
Engage independent advisers
The intersection of Oracle licensing rules and Azure cost optimisation requires specialist expertise. Avoid relying solely on Oracle sales or Microsoft account teams. See Oracle Advisory Services.
📚 Oracle Cloud & Azure Licensing Guides
Article Series: Oracle OCI & Cloud Licensing
Oracle OCI & Cloud Infrastructure Licensing (Pillar) BYOL vs. Licence-Included on Azure (This Article) BYOL vs. Licence-Included on OCI Oracle BYOL — Comprehensive Guide Oracle Cloud & BYOL Strategy Playbook Managing Licences in OCI Environments Oracle Cloud Contracts & Credits OCI Cost Optimisation StrategiesFrequently Asked Questions
When is BYOL cheaper than licence-included on Azure?
+
For workloads running 24/7, BYOL typically becomes cheaper after 14–20 months (the break-even point). Over a 3-year period, BYOL saves approximately 25% compared to licence-included; over 5 years, savings reach 40%+. For workloads running less than 2,000 hours per year (business hours only), licence-included may remain cheaper for 3–5 years. Model each workload individually using actual utilisation data.
Do on-premises core factors apply when licensing Oracle on Azure?
+
No. Oracle’s on-premises core factor table does not apply in any public cloud environment, including Azure. The cloud counting rule is a flat 2 vCPUs = 1 Processor licence, regardless of the underlying processor type. This is a common miscalculation — enterprises that apply the 0.5 core factor (standard for Intel processors on-premises) to Azure vCPUs will under-count their licences by 50%.
Can I switch between BYOL and licence-included on Database@Azure?
+
Database@Azure supports both BYOL and licence-included pricing modes. Switching between them may require reprovisioning the database instance or contacting Microsoft/Oracle to adjust the billing model. It is not typically a self-service toggle in the Azure portal. Plan your initial deployment model carefully and build conversion procedures into your operational runbook if you anticipate switching.
Does Oracle audit licence-included deployments on Azure?
+
No — licence-included deployments on Database@Azure are covered by the Microsoft-Oracle service agreement, not by a customer-owned perpetual licence. Oracle’s audit rights apply to your own perpetual licences, not to services where the licence is provided through a third-party agreement. However, any BYOL deployments on standard Azure VMs remain fully subject to Oracle audit rights. See Oracle Audit Defense Service.
Can I use an Oracle ULA to cover Azure BYOL deployments?
+
Yes — during an active ULA term, you can deploy unlimited Oracle instances on Azure under BYOL without counting individual licences. This is a significant advantage for enterprises planning large-scale Azure migrations. When the ULA ends and you certify, all Azure deployments count toward your total. Ensure every Azure Oracle VM is included in your ULA certification to maintain post-ULA compliance.
What happens if I resize an Azure VM running Oracle under BYOL?
+
Resizing to a larger VM with more vCPUs increases your Oracle licence requirement immediately. A 4-vCPU VM requires 2 Processor licences; resizing to 8 vCPUs requires 4. If you do not have the additional licences, you are non-compliant from the moment of the resize. Implement Azure Policy to restrict Oracle-tagged VMs to approved sizes and require licensing team approval before any resize operation.
Should I use licence-included for Oracle DR on Azure?
+
For DR instances that run infrequently (quarterly tests, rare failovers), licence-included can be cost-effective because you pay only for active hours. However, OCI’s licence-included pricing is typically lower than Azure’s for Oracle workloads. Consider the Azure-OCI interconnect to run DR on OCI at a fraction of the Azure licence-included cost while keeping your primary workload on Azure. See Oracle on Azure for HA & DR.
Optimising Oracle Licensing on Azure?
Redress Compliance helps enterprises choose the right licensing model, negotiate Oracle contracts for cloud deployment, and avoid the compliance traps that catch most organisations. We work completely independently of Oracle and Microsoft.
Related Resources
Pillar Guide
Oracle OCI & Cloud Licensing
Related Guide
Oracle Licensing on Azure
Related Guide
Oracle on Azure for HA & DR
Related Guide
Oracle Cloud Negotiations
Service
Oracle Advisory Services
Service
Oracle Contract Negotiation
Knowledge Hub
Oracle Licensing Hub
Case Studies
Oracle Advisory Case Studies
FF
Fredrik Filipsson
Co-Founder, Redress Compliance
Fredrik Filipsson is the co-founder of Redress Compliance, a leading independent advisory firm specialising in Oracle, Microsoft, SAP, IBM, and Salesforce licensing. With over 20 years of experience in software licensing and contract negotiations — including tenures at IBM, SAP, and Oracle — Fredrik has helped hundreds of organisations, including numerous Fortune 500 companies, optimise costs, defend against audits, and secure favourable terms with major software vendors.
← Back to Oracle Knowledge Hub