How Oracle's Authorised Cloud Environment Policy Works on Azure, The vCPU-to-Licence Conversion Rules, BYOL vs Licence Included Cost Comparison, Database and WebLogic Licensing Mechanics, The Azure VMware Solution Trap, Database@Azure Options, High Availability and DR Considerations, Common Compliance Pitfalls, and the Optimisation Framework for Oracle on Azure
Microsoft Azure is an Oracle-recognised 'Authorised Cloud Environment,' meaning Oracle has published specific rules for counting processor licences on Azure VMs. The core rule is simple: 2 vCPUs = 1 Oracle Processor licence (with hyperthreading enabled). Oracle's traditional on-premises Core Factor Table does not apply in Azure — the vCPU-based counting replaces it.
This creates genuine cost optimisation opportunities: organisations can right-size Azure VMs to match their licence entitlements, use constrained vCPU SKUs to reduce licence requirements, and leverage BYOL to avoid paying for Oracle software twice. However, Azure also contains significant compliance traps — particularly the Azure VMware Solution (AVS), which Oracle does not recognise as an authorised environment, and Azure Dedicated Hosts, which require licensing the full host capacity regardless of VM size.
For the broader Azure licensing and cost optimisation context, see our pillar guide: Azure Licensing and Cost Optimization: A CIO's Playbook. For a detailed BYOL vs Licence Included cost comparison on Azure, see BYOL vs License Included on Azure.
| Azure Deployment Model | Oracle Licence Rule | Cost Impact | Compliance Risk |
|---|---|---|---|
| Standard Azure VM (shared infrastructure) | 2 vCPUs = 1 Processor licence | Most cost-efficient — licence only the VM's vCPUs | Low if vCPU count is tracked and matched to licences |
| Oracle Database@Azure (managed service) | BYOL or Licence Included option — Oracle Exadata in Azure regions | Licence Included bundles licence into hourly cost; BYOL uses existing licences | Low — Oracle manages the environment |
| Azure VMware Solution (AVS) | Oracle does NOT recognise AVS as authorised — licence all physical cores in the cluster | 10×–30× higher than standard Azure VM licensing | Very high — most organisations are unaware of this rule |
| Azure Dedicated Host | Licence full host capacity (all vCPUs on the dedicated server) | 2×–4× higher than standard shared VM | Medium — organisations assume they only need to licence their VM |
| Constrained vCPU VM SKUs | Licence based on the constrained vCPU count (not the base VM capacity) | Up to 50% licence reduction with same memory/IO | Low — Oracle recognises the SKU's stated vCPU count |
Oracle officially recognises Microsoft Azure as an Authorised Cloud Environment for running Oracle software. This means Oracle has published specific licence counting rules that replace the traditional on-premises Core Factor Table when Oracle runs on standard Azure VMs.
| Azure Licensing Rule | How It Works | Example | Key Distinction from On-Premises |
|---|---|---|---|
| Enterprise Edition: 2 vCPUs = 1 Processor licence | With hyperthreading enabled (standard on Azure), each pair of vCPUs counts as one Oracle Processor licence | 8 vCPU VM = 4 Processor licences | No Core Factor Table — simpler than on-prem counting |
| Standard Edition 2: per-socket model | 1–4 vCPUs = 1 socket (1 licence); 5–8 vCPUs = 2 sockets (2 licences) | 4 vCPU VM = 1 SE2 licence; 8 vCPU VM = 2 SE2 licences | SE2 maximum is 8 vCPUs on Azure — cannot go larger |
| Without hyperthreading (rare) | 1 vCPU = 1 Processor licence | 4 vCPU VM without HT = 4 licences | Double the licence count — verify HT is enabled |
| WebLogic Enterprise Edition | Same 2 vCPU = 1 Processor licence rule | 8 vCPU VM = 4 WebLogic EE licences | Same simplification as database |
| WebLogic Standard Edition | Per-socket: up to 4 vCPUs = 1 licence | 4 vCPU VM = 1 WebLogic SE licence | Cheaper for small single-server deployments |
| Named User Plus (NUP) | NUP minimums still apply: 25 NUP per Processor for DB EE, 10 NUP per Processor for middleware | 4 Processor licences = minimum 100 NUP for DB EE | NUP minimums can make Processor licensing cheaper in cloud scenarios |
For a comparison of how Oracle licensing works on OCI vs Azure vs AWS, see Oracle Licensing on AWS: Top 5 Compliance Risks and Oracle BYOL on OCI.
Azure offers two primary paths for Oracle licensing: BYOL (Bring Your Own Licence) where you use existing perpetual Oracle licences, and Licence Included where the Oracle software cost is bundled into the Azure service price. For the complete cost comparison, see BYOL vs License Included on Azure.
| Dimension | BYOL on Azure | Licence Included (Database@Azure / Marketplace) |
|---|---|---|
| Licence cost | Use existing licences — no new Oracle licence fee; pay only Azure VM costs | Oracle licence fee bundled into hourly/monthly Azure service price |
| Oracle support | Continue paying annual Oracle support (~22% of licence value) | Included in service price — no separate Oracle support invoice |
| Best for | Long-term production workloads where licences are already owned | Short-term projects, dev/test, or organisations without existing Oracle licences |
| Available products | Oracle Database (all editions), WebLogic, middleware, applications | Database@Azure (managed Exadata service); limited marketplace images |
| WebLogic availability | BYOL only — all Azure WebLogic offerings require your own licence | No Licence Included option for WebLogic on Azure |
| Compliance responsibility | Customer must track vCPU usage and maintain sufficient licences | Oracle manages licensing within the service |
| Long-term cost | Lower for steady-state production (licence already owned) | Higher over time — ongoing subscription includes licence premium |
| Flexibility | Tied to licence entitlement — can only deploy what you have licences for | Scale up/down without licence constraints; stop and stop paying |
| Azure VM vCPUs (HT enabled) | DB Enterprise Edition Licences | DB SE2 Licences | SE2 Permitted? | Monthly DB EE Licence Value (at list) |
|---|---|---|---|---|
| 2 vCPUs | 1 | 1 | Yes | $47,500 licence + ~$10,450/yr support |
| 4 vCPUs | 2 | 1 | Yes | $95,000 |
| 8 vCPUs | 4 | 2 | Yes (maximum for SE2) | $190,000 |
| 16 vCPUs | 8 | N/A | No — exceeds SE2 8-vCPU limit | $380,000 |
| 32 vCPUs | 16 | N/A | No | $760,000 |
| 64 vCPUs | 32 | N/A | No | $1,520,000 |
Database Options on Azure: Every Oracle database option or pack enabled on an Azure VM (Diagnostics Pack, Tuning Pack, Advanced Security, Partitioning, RAC, etc.) requires its own processor licences at the same count as the base database. A 4-licence database deployment using 3 options requires 16 total licences (4 base + 4 + 4 + 4). Options are the most commonly under-licensed items in Oracle audits — including Azure deployments. For Oracle HA/DR licensing specifics on Azure, see Oracle Licensing on Azure for HA and DR.
Azure VMware Solution (AVS) allows organisations to run VMware vSphere clusters inside Azure regions. However, Oracle does not recognise AVS as an Authorised Cloud Environment — Oracle treats it identically to an on-premises VMware deployment, applying its soft partitioning policy.
| Deployment | Oracle's Licence Rule | Example (4 vCPU Oracle VM) | Licence Cost at DB EE List |
|---|---|---|---|
| Standard Azure VM (authorised) | 2 vCPUs = 1 licence → licence only the VM's vCPUs | 4 vCPUs = 2 licences | $95,000 |
| Azure VMware Solution (AVS) | Licence all physical cores on ALL hosts in the AVS cluster | 3-host AVS cluster, 36 cores/host = 108 cores × 0.5 = 54 licences | $2,565,000 |
| Azure Dedicated Host | Licence all vCPUs on the dedicated host | Dedicated host with 64 vCPUs = 32 licences | $1,520,000 |
The difference is staggering: a 4-vCPU Oracle database on a standard Azure VM costs $95K in licences. The same database on AVS can cost $2.5M+ because Oracle requires licensing the entire cluster. This makes AVS fundamentally unsuitable for Oracle workloads unless the organisation has a ULA or is prepared for massive licence costs. Always use standard Azure VMs or Database@Azure for Oracle workloads.
All Oracle WebLogic Server deployments on Azure are BYOL — there is no Licence Included option for WebLogic on Azure. This means organisations must hold valid WebLogic licences before deploying on Azure.
| WebLogic Scenario | Licence Requirement | Azure VM Sizing | Key Consideration |
|---|---|---|---|
| WebLogic Enterprise Edition — single instance | 2 vCPUs = 1 Processor licence | Right-size to match available licences | Same EE counting rule as database |
| WebLogic EE — clustered across 3 Azure VMs (8 vCPUs each) | 3 × 4 = 12 Processor licences total | Every cluster node's vCPUs must be licensed | Clustering multiplies licence requirements — each node needs full licensing |
| WebLogic Standard Edition — single instance | Up to 4 vCPUs = 1 licence (per socket) | Use 4-vCPU VMs for maximum licence efficiency | SE lacks clustering; suitable for single-server deployments only |
| WebLogic on AKS (Kubernetes) | Licence the underlying worker node vCPUs hosting WebLogic containers | Worker node vCPU count determines licences | Auto-scaling can create unexpected licence requirements if nodes scale out |
Oracle licensing on Azure creates specific opportunities for cost reduction that are not available on-premises. The key is matching Azure VM sizing to licence entitlements. For broader Azure cost management, see Managing Azure Spend and Commitments and Managing Azure Overages.
| Optimisation Strategy | How It Works | Typical Savings | Consideration |
|---|---|---|---|
| Use constrained vCPU VM SKUs | Azure offers VMs where vCPUs are constrained while maintaining full memory and IO — licence based on constrained count, not base VM capacity | Up to 50% licence reduction with same memory/IO performance | Ensure performance testing confirms the reduced vCPU count is sufficient |
| Right-size VMs to match licences | Select Azure VM sizes that match exactly the number of licences available (e.g., 8 vCPU VM if you have 4 Processor licences) | Eliminates over-provisioning — 0% licence waste | May require workload performance analysis |
| Use SE2 where possible | Standard Edition 2 licences are much cheaper and cover up to 4 vCPUs with 1 licence (up to 8 vCPUs max) | 60–80% licence cost reduction vs Enterprise Edition for eligible workloads | SE2 has feature and scalability limits; verify workload compatibility |
| Consolidate databases on fewer VMs | Run multiple Oracle databases on one larger Azure VM instead of separate smaller VMs | 20–40% licence reduction through shared vCPU allocation | Increases single-point-of-failure risk; requires careful capacity planning |
| Avoid AVS and Dedicated Hosts for Oracle | Use standard shared Azure VMs to benefit from the 2-vCPU = 1-licence rule | 70–95% savings vs AVS; 50–75% vs Dedicated Hosts | Standard VMs provide the most licensing-efficient deployment model |
| Schedule non-production shutdowns | Auto-shutdown dev/test Oracle VMs outside business hours to limit compliance exposure windows | Reduced audit exposure; Azure compute cost savings | Licence still required when VM is running; shutdowns reduce risk, not obligation |
For Azure EA negotiation strategies that incorporate Oracle licensing costs into your Microsoft commitment, see Negotiating Microsoft Azure Enterprise Agreements. For cloud migration licensing implications across Azure, AWS, and GCP, see Microsoft Licensing for Cloud Migration.
Oracle's ability to audit Azure deployments is the same as on-premises — Oracle can request proof that you have sufficient licences for all Oracle software running on Azure VMs. For Oracle audit defence guidance, see our Oracle Audit Defense Service.
| Compliance Pitfall | How It Happens | Oracle's Position | Typical Exposure | Prevention |
|---|---|---|---|---|
| AVS treated as authorised cloud | Organisation runs Oracle on Azure VMware Solution assuming standard Azure rules apply | Licence all physical cores in the AVS cluster under soft partitioning policy | $1M–$10M+ (entire cluster licensed) | Never run Oracle on AVS; use standard Azure VMs or Database@Azure |
| VM resized beyond licence capacity | Admin scales Azure VM to a larger size, exceeding available Processor licences | Oracle counts the VM's maximum vCPU capacity at the time of use | $95K–$500K+ per sizing event | Implement Azure Policy to restrict VM SKU sizes for Oracle VMs |
| SE2 deployed above 8 vCPU limit | Standard Edition 2 database deployed on a VM with more than 8 vCPUs | Oracle requires Enterprise Edition licensing for the entire deployment | $190K–$1M+ (EE licence upgrade for all processors) | Enforce 8-vCPU maximum VM size for SE2 workloads |
| Database options not licensed | Diagnostics Pack, Tuning Pack, or other options enabled without BYOL entitlement | Each option requires same Processor count as base DB licence | $100K–$500K+ per option | Audit option usage on every Azure Oracle instance; disable unused options |
| Dedicated Host over-licensing not anticipated | Organisation deploys Oracle on Azure Dedicated Host assuming VM-level licensing | Licence full host capacity regardless of VM size | $500K–$2M+ per host | Use standard shared VMs for Oracle; avoid Dedicated Hosts |
| Auto-scaling creates compliance gap | WebLogic cluster auto-scales to additional Azure VMs beyond licence capacity | Each active VM's vCPUs must be licensed while running | $95K–$500K+ per auto-scale event | Cap auto-scaling to match licence capacity; restrict VM SKU sizes |
In 2023, Microsoft and Oracle launched Database@Azure — a jointly managed service that deploys Oracle Exadata infrastructure inside Azure data centres, accessible through the Azure portal and billed through Azure. This represents the deepest integration between Oracle and a non-Oracle cloud provider.
| Database@Azure Feature | BYOL Option | Licence Included Option | Key Benefit |
|---|---|---|---|
| Deployment model | Use existing Oracle licences; pay only Azure infrastructure | Oracle licence bundled into hourly Azure service price | Billed through Azure — counts toward MACC/Azure commit |
| Infrastructure | Oracle Exadata hardware in Azure regions — managed by Oracle | Enterprise-grade Oracle infrastructure without managing hardware | |
| Support | Continue paying separate Oracle support | Included in service price | Licence Included simplifies vendor management |
| Support Rewards | Oracle Cloud consumption on Database@Azure may qualify for Oracle Support Rewards credits | Can reduce on-prem Oracle support bills by up to 25% of Azure Oracle spend | |
| Networking | Low-latency connectivity between Oracle databases and Azure services (Azure VNets) | Better performance than cross-cloud architectures | |
| Availability | Available in select Azure regions; expanding | Check region availability before planning deployment | |
Database@Azure is particularly valuable for organisations with large Azure commitments (MACC) who also need Oracle databases — the Oracle spend counts toward Azure consumption. For Azure commitment strategy, see Managing Azure Spend and Commitments. For Windows Server and hybrid Azure benefits that complement Oracle on Azure, see Windows Server Licensing and Azure Hybrid Benefits.
| # | Action | Owner | Frequency | Key Outcome |
|---|---|---|---|---|
| 1 | Inventory all Azure VMs running Oracle software: document VM SKU, vCPU count, Oracle products deployed, editions, and options enabled | SAM / Cloud Operations | Quarterly | Complete Oracle-on-Azure estate visibility |
| 2 | Map every Azure Oracle deployment to its licence source: document which BYOL licences cover each VM | SAM | At provisioning; verified quarterly | Licence-to-VM traceability for audit readiness |
| 3 | Verify no Oracle workloads are running on Azure VMware Solution (AVS): if found, migrate immediately to standard Azure VMs | Cloud Architecture / SAM | Immediately; ongoing monitoring | Eliminate the #1 Azure Oracle compliance risk |
| 4 | Right-size Azure VMs to match licence entitlements: use constrained vCPU SKUs where possible to reduce licence requirements | Cloud Architecture / DBA | At provisioning; quarterly review | No over-provisioned vCPUs consuming more licences than available |
| 5 | Evaluate SE2 vs EE for every Oracle database on Azure: switch to SE2 where workloads fit within SE2 limits (8 vCPU max, no EE options) | DBA / SAM | Annually | 60–80% licence cost reduction for eligible workloads |
| 6 | Audit database option usage on every Azure Oracle instance: disable unused options and ensure every enabled option has a BYOL entitlement | DBA / SAM | Quarterly | No unlicensed options — the most common audit finding |
| 7 | Implement Azure Policy to restrict VM SKU sizes for Oracle-tagged VMs: prevent ad-hoc resizing beyond licence capacity | Cloud Operations / SAM | At deployment; enforced continuously | No accidental VM resizing that creates compliance gaps |
| 8 | Evaluate Database@Azure for new Oracle deployments: compare BYOL on standard VMs vs Database@Azure (BYOL or Licence Included) | Cloud Architecture / Procurement | Every new Oracle deployment decision | Optimal deployment model per workload; MACC alignment |
| 9 | Track Oracle Support Rewards: if using Database@Azure or other Oracle services on Azure, ensure Support Rewards credits are applied | Procurement / Finance | Quarterly | Maximum credit offset against on-prem Oracle support costs |
| 10 | Conduct quarterly Oracle-on-Azure compliance review: verify vCPU-to-licence mapping, check for AVS/Dedicated Host exposure, validate edition and option entitlements | SAM / Advisory | Quarterly | Zero surprise audit findings; continuous Oracle-on-Azure compliance |
For organisations managing Oracle workloads on Azure, Redress Compliance provides advisory through both our Microsoft Advisory Services (for Azure EA and cost optimisation) and Oracle License Management Services (for Oracle licence compliance). For Oracle audit defence, see our Oracle Audit Defense Service.
Yes. Oracle officially recognises Microsoft Azure as an Authorised Cloud Environment. This means specific vCPU-based licence counting rules apply: 2 vCPUs = 1 Oracle Processor licence (with hyperthreading enabled). Oracle's on-premises Core Factor Table does not apply to standard Azure VMs.
For Enterprise Edition products with hyperthreading enabled (standard on Azure): divide the VM's vCPU count by 2 to get the required Processor licences. An 8-vCPU VM requires 4 Processor licences. For Standard Edition 2: 1–4 vCPUs = 1 licence; 5–8 vCPUs = 2 licences; SE2 maximum is 8 vCPUs.
Yes. BYOL is the most common approach for Oracle on Azure. You apply existing perpetual Oracle licences to Azure VMs, paying only the Azure infrastructure cost. You must maintain active Oracle support on those licences and track vCPU usage to ensure compliance.
Database@Azure is a jointly managed Oracle-Microsoft service that deploys Oracle Exadata infrastructure inside Azure data centres. It offers both BYOL and Licence Included pricing, is billed through Azure (counting toward MACC), and provides low-latency connectivity to other Azure services.
Oracle does not recognise AVS as an Authorised Cloud Environment. Oracle treats AVS as standard VMware, requiring licensing of all physical cores across the entire AVS cluster under soft partitioning rules. This can cost 10×–30× more than running the same Oracle workload on a standard Azure VM.
Azure offers VM SKUs where the vCPU count is constrained while maintaining full memory and IO. Oracle licences based on the constrained vCPU count, not the base VM capacity. This can reduce licence requirements by up to 50% while providing the same memory and storage performance.
Yes. Oracle can request proof of sufficient licensing for all Oracle software running on Azure, just as for on-premises deployments. Oracle audits commonly check vCPU counts, edition compliance, database option usage, and whether AVS or Dedicated Hosts are being used.
Yes, but SE2 is limited to a maximum of 8 vCPUs on Azure. Within that limit, SE2 uses per-socket licensing: 1–4 vCPUs = 1 licence, 5–8 vCPUs = 2 licences. SE2 cannot use Enterprise Edition features like Partitioning, RAC, or Advanced Security.
On Azure Dedicated Hosts, Oracle requires licensing the full physical host capacity (all vCPUs), not just the VMs running on it. This eliminates the cost advantage of Azure's shared infrastructure model and can significantly increase licence requirements.
No. All Oracle WebLogic Server offerings on Azure are BYOL only. You must hold valid WebLogic licences before deploying. There is no Licence Included or pay-as-you-go option for WebLogic on Azure.
Every Oracle database option (Diagnostics Pack, Tuning Pack, Advanced Security, Partitioning, RAC, etc.) requires its own Processor licences at the same count as the base database. If a VM requires 4 Database EE licences and uses 3 options, total requirement is 16 licences.
Yes. Oracle's Support Rewards programme provides credits against on-premises Oracle support costs based on Oracle Cloud consumption, including Database@Azure. Up to 25% of Oracle Cloud spend on Azure can be returned as support credits.
Resizing creates an immediate compliance gap. Oracle counts the VM's maximum vCPU capacity at the time of use. Even temporary resizing requires sufficient licences. Implement Azure Policy to restrict VM SKU sizes for Oracle workloads.
No. Oracle's on-premises Core Factor Table does not apply in Authorised Cloud Environments like Azure. The vCPU-based counting rule (2 vCPUs = 1 licence) replaces it. This simplifies calculations compared to on-premises licensing.
This article is part of our Azure Licensing pillar. Explore related guides:
Redress Compliance provides independent Oracle licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic license optimization, audit defense, and contract negotiation.
Explore Oracle Advisory Services →Redress Compliance has helped hundreds of enterprises negotiate better Microsoft EA, CSP, and Azure terms — typically saving 15–30% on renewals.
100% vendor-independent · No commercial relationships with any software vendor
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →