Running Oracle Enterprise Applications on Azure: Licensing E-Business Suite, PeopleSoft and More

Why Azure and Oracle Licensing Is More Complex Than It Appears

Oracle officially recognises Microsoft Azure as an "Authorised Cloud Environment," which means you are permitted to run Oracle software on Azure virtual machines using your existing on-premises licenses under the Bring Your Own License (BYOL) model. This sounds straightforward, but the licensing mechanics are significantly more complex than any cloud migration project team typically accounts for.

The complexity has two distinct layers. First, Oracle application licenses — the user or module licenses for E-Business Suite financials, PeopleSoft HCM, JD Edwards manufacturing or Siebel CRM — are largely unaffected by the move to Azure. They travel with you. Second, Oracle technology licenses — particularly Oracle Database and middleware — are directly and materially affected by Azure because the counting methodology changes in a virtualised cloud environment. Getting the second layer wrong is where audit claims originate.

From our advisory work across 200-plus Oracle cloud licensing assessments, more than half of organisations that move Oracle enterprise applications to Azure without independent licensing guidance carry material compliance exposure that Oracle's LMS team can identify within hours of running their collection scripts.

Oracle E-Business Suite on Azure: What You Need to Know

Oracle E-Business Suite (EBS) is one of the most commonly migrated Oracle applications to Azure. EBS application licenses are user-based — you license by named user, Application User metric, or Employee metric depending on the module — and these application licenses do not change when you move to Azure. Your existing user count and module entitlements carry over directly.

The Bundled Database Advantage

A critical licensing benefit of EBS is that Oracle Database licenses are bundled with EBS application licenses under the Applications Unlimited program. When you deploy EBS, the Oracle Database that runs beneath it is covered by the EBS application license — you do not need to separately purchase Oracle Database processor licenses for the database tier powering EBS.

This bundled database benefit applies on Azure, provided the Oracle Database is used exclusively to support the licensed EBS application. Any database use beyond the EBS application footprint — including reporting environments, data warehouses, or connected Oracle applications not covered by the bundle — requires separately licensed Oracle Database processors.

Processor Counting on Azure VMs

For any Oracle software that requires processor licensing on Azure — including Oracle Database used outside the EBS bundle, Oracle Fusion Middleware, Oracle WebLogic, or Oracle SOA Suite — Oracle's cloud licensing policy applies the vCPU-to-processor conversion. One Oracle processor license is required for every two vCPUs on the Azure VM. An Azure VM with 16 vCPUs therefore requires eight Oracle processor licenses.

This conversion appears straightforward, but complications arise from several directions. High-availability configurations that span multiple Azure VMs multiply the processor license count. Development, test and UAT environments are often overlooked — Oracle requires that these environments are also properly licensed. And organisations that resize Azure VMs upward during the migration or post-go-live without reviewing licensing exposure routinely generate compliance gaps.

PeopleSoft on Azure: The Hidden Database Risk

PeopleSoft licensing on Azure contains a trap that catches a significant number of organisations. Unlike EBS, PeopleSoft does not include a bundled Oracle Database license. PeopleSoft application licenses — Application User, Employee User, or Enterprise metric — cover the PeopleSoft application layer only. The underlying database must be separately licensed.

The SQL Server Alternative

This creates a genuinely valuable optimisation opportunity. PeopleSoft supports Microsoft SQL Server as a certified database alternative to Oracle Database. Migrating the PeopleSoft database layer from Oracle to SQL Server eliminates the Oracle Database processor license requirement entirely. For a typical PeopleSoft HCM or Finance deployment running on a four-socket server, this can eliminate $190,000 to $475,000 in Oracle Database license costs plus the associated Oracle support fees that compound at 8% per year.

On Azure, the economics improve further because Azure SQL is the natural database landing zone. The PeopleSoft application continues to run on Azure VMs (using existing PeopleSoft application licenses via BYOL), while the database migrates to Azure SQL or SQL Server on Azure VMs. Oracle has no licensing claim on the database layer once you have moved off Oracle Database.

Organisations That Stay on Oracle Database

If your organisation remains on Oracle Database for PeopleSoft — which is common where there are Oracle Database options deployed such as Advanced Security or Partitioning — you must license every Oracle Database processor in the Azure environment at the vCPU divided by two rate. This includes non-production environments. Oracle's audit scope covers development, test, QA, disaster recovery and training environments, not only production.

JD Edwards EnterpriseOne on Azure

JD Edwards EnterpriseOne shares the same structural profile as PeopleSoft: application licenses are user-based or by module, and Oracle Database is not bundled. JD Edwards supports Oracle Database, IBM DB2, and Microsoft SQL Server as certified database platforms.

The Azure migration decision for JD Edwards therefore mirrors PeopleSoft: the critical licensing question is whether to migrate the database layer to SQL Server (eliminating Oracle Database license requirements) or to retain Oracle Database and manage the associated processor licensing on Azure VMs. Where JD Edwards deployments have Oracle Database options deployed — particularly Advanced Security for encrypting manufacturing or financial data — the migration to SQL Server requires careful assessment of whether equivalent functionality is available and at what cost.

JD Edwards on Azure also commonly surfaces compliance exposure in distributed enterprise deployments where regional installations share database tiers. Each Azure region where a JD Edwards database instance runs constitutes a separately licensable deployment, and organisations managing multi-region ERP footprints frequently undercount their Oracle Database processor requirements.

Siebel CRM on Azure

Siebel CRM is increasingly a migration candidate as organisations plan their eventual transition to Salesforce or Oracle Fusion CX. Running Siebel on Azure in a hybrid or transitional state is feasible but carries specific licensing risks.

Siebel application licenses are user-based (Named User or CPU). Oracle Database is not bundled and must be separately licensed. The processor counting rules on Azure apply identically: vCPU divided by two equals required Oracle Database processor licenses. Siebel deployments frequently include Oracle WebLogic Server as the application server layer, which is a separately licensed Oracle Fusion Middleware component requiring its own processor license count.

Organisations maintaining Siebel on Azure during a CRM transition must carefully document all Oracle software deployed across the environment. WebLogic, Oracle Database, Oracle Internet Directory, and Oracle Identity Manager are all separately licensed components that Oracle's LMS team looks for when conducting a compliance review of Siebel environments.

Oracle Database@Azure: A New Option

In 2024, Oracle and Microsoft announced Oracle Database@Azure, a service that runs Oracle Exadata infrastructure physically inside Azure data centres. This creates a new licensing pathway for Oracle enterprise applications on Azure that differs materially from standard BYOL deployments.

Under Oracle Database@Azure, customers consuming Oracle Database through the managed service (OCIs) do not count processors using the vCPU divided by two rule. Instead, the Oracle Cloud Service (OCS) subscription covers the database licensing. This can simplify compliance management for organisations running Oracle Database-intensive workloads, but it introduces new contract risks: OCS subscription terms, auto-renewal clauses, and consumption commitments require careful negotiation. Oracle Database@Azure is not automatically cheaper than BYOL — a full cost and contract comparison is required before committing.

Six Compliance Risks Every Azure Migration Team Must Address

1. Non-Production Environments: Oracle requires that development, test, QA, UAT, disaster recovery and training environments are fully licensed. Azure's ease of spinning up new environments means non-production sprawl is common and frequently unlicensed.

2. VM Resizing Post-Migration: Azure VMs are frequently resized upward after go-live as performance requirements become clear. Each vCPU increase changes the Oracle processor license requirement. Migration teams rarely have a process to link Azure VM resizing events to licensing reviews.

3. High-Availability and Disaster Recovery VMs: Oracle's standard licensing terms require that passive failover instances are licensed if they can be activated within ten seconds. Azure's high-availability configurations frequently include warm standby VMs that Oracle considers licensable.

4. Middleware Overlooked: Oracle WebLogic, SOA Suite, Data Integrator and Identity Management components are separately licensed Fusion Middleware products. They appear as standard application server or integration components in Azure deployments and are routinely missing from license counts.

5. Oracle Java on Azure VMs: Any Azure VM running Oracle JDK or a Java SE subscription requires licensing under Oracle's post-2023 employee-based Java licensing model. Application server VMs running Oracle Java need Java SE Universal Subscription coverage.

6. Support Fee Increases: Oracle's annual support fees increase by 8% per year. A migration that pushes support fees higher through additional processor licensing in Azure will see those costs compound significantly over a three to five year cloud commitment period.

How to Structure an Audit-Safe Azure Migration

The pre-migration phase is when licensing decisions are cheapest to make and most impactful. Before any Azure deployment begins, the organisation should conduct a complete entitlement review — mapping every Oracle license in the estate to its metric, version, and authorised use — and model the Azure deployment architecture against those entitlements.

This includes sizing every Azure VM that will run Oracle software, calculating the vCPU-to-processor license count for each, identifying all non-production environments and their licensing requirements, and evaluating whether PeopleSoft or JD Edwards database layers should migrate to SQL Server.

Post-migration, organisations should establish a cloud licensing governance process that links Azure VM provisioning and resizing events to a licensing review. Without this, compliance exposure accumulates invisibly as the Azure environment evolves.

Oracle support fees should be budgeted at 8% annual increase for the full duration of the Azure commitment. Do not use Oracle's historic 4% projection — Oracle's contractual right to increase support fees by 8% per year is exercised regularly and materially affects total cost of ownership calculations.