Licensing Oracle Database on Microsoft Azure: The Rules and the Traps

Moving an Oracle database to Microsoft Azure is allowed, and you can bring the licences you already own. What changes is the arithmetic. On Azure, Oracle does not count cores the way it does in your data centre, and the same workload can need twice as many licences after the move. Most of the expensive surprises we see in Azure migrations come from that one difference.

This guide sets out Oracle’s rules for Azure as they stand in Oracle’s cloud licensing policy (in effect 4 September 2026), with worked numbers and the traps to check before you migrate.

In short

• You can bring the Oracle licences you own to Microsoft Azure: it is one of Oracle’s three Authorized Cloud Environments, with AWS and Google Cloud.
• On Azure, two vCPUs count as one processor licence when multi-threading is enabled, and the core factor does not apply, so the same workload can need twice the licences it needed on premises.
• Standard Edition 2 counts one socket per four vCPUs and may only run on instances of up to eight vCPUs.
• Licences under a ULA may be used on Azure, but those deployments cannot be counted at the ULA’s certification.

Azure is an Authorized Cloud Environment

Oracle’s policy “Licensing Oracle Software in the Cloud Computing Environment” names three Authorized Cloud Environments: Amazon Web Services (EC2 and RDS), Microsoft Azure and Google Cloud Platform. On these, you may run Oracle programs under licences you already hold, a model usually called bring your own licence.

Enterprise Edition: two vCPUs are one licence

The policy says to count the maximum vCPUs of an instance type. On Azure, two vCPUs count as one Oracle processor licence when multi-threading is enabled, and one vCPU counts as one licence when it is not. The Oracle Processor Core Factor Table does not apply.

That last sentence is where the cost changes. On your own Intel or AMD servers, 8 physical cores with hyper-threading present 16 threads, and you license 8 × 0.5 = 4 processors. On Azure, a 16-vCPU virtual machine with multi-threading counts as 8 processors. The same compute needs twice the licences.

If your existing licences were sized for the on-premises count, the move can leave you under-licensed on day one.

Standard Edition 2: sockets by the four vCPUs, eight at most

For programs with “Standard Edition” in the name, the policy counts sockets by instance size. An instance with four or fewer vCPUs is one socket. Above that, every four vCPUs, rounded up to the next multiple of four, is one socket. Standard Edition 2 may only be licensed on instances of up to eight vCPUs, and by Named User Plus the minimum is 10 per eight vCPUs.

So an 8-vCPU instance needs two Standard Edition 2 processor licences, $35,000 at list. A 16-vCPU instance cannot run Standard Edition 2 under this policy at all.

Named User Plus minimums follow the vCPU count

Named User Plus licensing works on Azure, but the minimums are worked out from the processor count above. Database Enterprise Edition needs at least 25 Named User Plus per processor, so a 16-vCPU instance with multi-threading needs at least 8 × 25 = 200 Named User Plus.

Licences from a ULA cannot be certified from Azure

The policy allows licences under an Unlimited License Agreement to be used in Authorized Cloud Environments, but customers may not include those deployments in the certification at the end of the ULA. If you are in a ULA and migrating to Azure, every database moved before certification is a database you will not own licences for afterwards. Plan the order of migration and certification together. Our ULA certification work starts with that timeline.

Oracle Database@Azure is a different model

Oracle Database@Azure runs Oracle’s own Exadata and Autonomous Database services inside Azure data centres, operated by Oracle and bought through the Azure Marketplace. It is licensed on Oracle Cloud Infrastructure’s terms, either licence-included or bring your own licence on Oracle’s cloud metrics, not by the vCPU rule above. Compare the two models on your actual workload before choosing. The cheapest option depends on database size, the options you use and whether you have licences to bring.

Traps to check before you migrate

• Constrained-vCPU sizes. Azure offers virtual machine sizes that keep the memory of a large size with fewer active vCPUs, such as Standard_E32-8s_v5, and Microsoft promotes them for licensed databases. Oracle’s policy counts the maximum vCPUs of an instance type. Settle how Oracle will count your chosen size, in writing, before you rely on it.
• Resizing later. The licence requirement follows the size you run. Scaling a virtual machine up for month-end raises the count for as long as it runs at that size.
• Test, staging and standby copies. Each one with Oracle installed and running is counted like production.
• Options and packs. Partitioning, Diagnostics and Tuning packs are licensed per processor too. Enterprise Manager or a monitoring tool can use a pack without anyone deciding to.
• Azure Hybrid Benefit. It covers Windows Server and SQL Server licences, and some Linux subscriptions. It does not cover Oracle.

Questions we are asked about Oracle licensing on Azure

Can I use my existing Oracle licences on Azure?

Yes. Azure is an Authorized Cloud Environment, so licences you own can be used there, counted under Oracle’s cloud policy rather than the core factor table.

How many Oracle licences do I need for an Azure virtual machine?

For Enterprise Edition, one processor licence per two vCPUs when multi-threading is enabled, or per vCPU when it is not, based on the maximum vCPUs of the instance type.

Does the Oracle core factor apply on Azure?

No. The policy states that the core factor table does not apply in Authorized Cloud Environments.

Can I run Oracle Standard Edition 2 on Azure?

Yes, on instances of up to eight vCPUs, counting one socket for every four vCPUs.

Does Azure Hybrid Benefit cover Oracle Database?

No. It applies to Windows Server and SQL Server licences and some Linux subscriptions, not to Oracle licences.

A migration is the best moment to get Oracle licensing right, and the worst moment to find out it is wrong. Before you move, book an hour with our Advisor on Call, or talk to us about a review of what you plan to run and what you own.