Oracle Database on Azure. The buyer side way.

Oracle Database on Microsoft Azure turns on the bring your own license math, the authorized cloud environment rules, and the vCPU mapping. This guide covers the deployment paths, the math, and the audit traps.

What are the three deployment paths for Oracle on Azure?

Oracle Database runs on Azure through three main paths, and each treats licensing differently. The path decides whether you manage the license or the rate includes it. Microsoft documents the managed option on its Azure Oracle Database page.

Bring your own license on Azure virtual machines

You run Oracle on Azure virtual machines with owned licenses. The Oracle cloud policy counts vCPUs, and you manage compliance. This path gives the most control and the most responsibility.

Oracle Database at Azure managed service

Oracle Database at Azure runs Oracle hardware inside Azure data centers as a managed service. Oracle describes the service on its Oracle Database at Azure page.

Third party hosting on Azure

A hosting provider can run Oracle on Azure on your behalf. The terms depend on the hosting arrangement and may differ from a direct deployment. Read the hosting contract carefully.

What do the authorized cloud environment rules cover?

Azure sits on Oracle's authorized cloud environment list. The vCPU rule applies and the core factor table does not. The rule lives in the Oracle cloud licensing policy.

What the policy covers

The policy sets the vCPU conversion for Oracle programs on authorized cloud environments. It governs how Azure deployments count for licensing.

What the policy does not cover

The policy is not a contract term, and it can change. The core factor benefit you get on premises does not carry to Azure. The on premises rule sits in the core factor table.

• No core factor. Azure counts vCPUs, not factored cores.
• Policy not contract. Pin the version in force at deployment.
• Edition matters. Standard Edition Two carries a vCPU cap.

How does the vCPU to processor math work?

With hyperthreading on, two vCPUs equal one processor license. With it off, one vCPU equals one license. Owned licenses move to Azure through bring your own license.

Where the common advice on Oracle Database on Azure is wrong

The standard advice is to default to the managed Oracle Database at Azure path for simplicity. We disagree. In about half of estates we reviewed, a virtual machine path with owned licenses would have cost less, or the managed path was right but chosen with no comparison on file. Defaulting to one path without modeling both leaves money on the table either way. The buyer side move is to size the vCPU count on the virtual machine path, price the managed service, and compare them against your real workload before choosing. The path is a cost decision, not a convenience choice.

30

Oracle on Azure reviews 2024 to 2025

2 vCPU

Per processor license with threading on

26%

Median Azure license cost we removed

Source: Redress Compliance advisory engagement file, 2024 to 2025.

Azure counts vCPUs, not factored cores. The path you pick and the size you choose are the whole licensing bill.

What Azure Oracle audit traps should a buyer expect?

Five findings recur on Azure Oracle estates.

• vCPU oversizing. Instances one tier too large raise the license count.
• Policy as contract. Sizing against a policy that can change and is not in the agreement.
• Core factor assumed. Applying the on premises core factor that does not exist on Azure.
• Edition cap breach. Running Standard Edition Two beyond its vCPU cap.
• No path comparison. Choosing managed or virtual machine without modeling both.

What should a buyer do next?

1. Inventory every Oracle instance on Azure and record vCPUs and threading.
2. Apply the two vCPU rule to confirm the processor license count.
3. Price the virtual machine path against the Oracle Database at Azure managed service.
4. Pin the Oracle cloud policy version in force at each deployment.
5. Check Standard Edition Two instances against the vCPU cap.
6. Document each deployment against the policy for audit defense.
7. Engage independent Oracle advisory before an Azure audit or a major move.

Frequently asked questions

How does Oracle count licenses on Azure?

Azure is an Oracle authorized cloud environment, so the cloud policy vCPU rule applies. With hyperthreading on, two vCPUs equal one processor license. The core factor table does not apply.

Does the Oracle core factor apply on Azure?

No. The processor core factor table applies on premises but not on authorized cloud environments such as Azure. The vCPU rule governs the count instead.

What is Oracle Database at Azure?

Oracle Database at Azure is a managed service that runs Oracle database hardware inside Azure data centers. It lowers operational effort and follows the service terms rather than self managed counting.

Can I bring my own Oracle license to Azure?

Yes. Bring your own license moves owned licenses to Azure virtual machines, where the vCPU rule sets the count. The same policy applies as on AWS.

Is the Oracle cloud policy contractual on Azure?

No. The vCPU rule sits in a policy document, not your signed contract, and Oracle can update it. Pin the version in force at deployment and document each instance against it.

What is the difference between the virtual machine and managed paths?

On virtual machines you bring owned licenses and manage compliance under the vCPU rule. The managed Oracle Database at Azure path runs Oracle hardware inside Azure and lowers operational effort.

What is the most common Azure Oracle audit trap?

Sizing against the policy as if it were contractual, assuming the on premises core factor, and oversizing virtual machines. Each raises the license count or weakens the audit position.

How do I choose between Azure Oracle paths?

Size the vCPU count on the virtual machine path, price the managed service, and compare both against your real workload. The path is a cost decision and should never be a default.