Last updated: June 2026
You bought Oracle's Bring-Your-Own-License promise: keep your existing licenses, run them on AWS or Azure, pay nothing extra. Then the audit notice arrives — and Oracle counts your vCPUs by a policy that isn't in your contract and isn't in cloud documentation. This survival guide shows you the rules Oracle applies, where they have no contractual force, and how to architect so a future audit finds nothing to claim.
The trap most enterprises walk into: Oracle's "Licensing Oracle Software in the Cloud Computing Environment" document is a policy, not a contract term — yet Oracle's GLAS team treats it as binding. It tells you to count 2 vCPUs as 1 Processor license when hyperthreading is on, but says nothing about the cost-cutting shapes that change the math entirely. Get the counting wrong on a 64-vCPU instance and you owe licenses for an entire database estate you thought was covered.
"Oracle's cloud counting rules live in a PDF that Oracle can revise unilaterally and that your Master Agreement never references. We have seen audit claims collapse the moment a customer asks Oracle to identify the contract clause that obligates the policy. Knowing the difference between Oracle's policy and your actual entitlement is the single most valuable thing in a cloud audit."
"On Azure, a constrained-vCPU VM size runs the same memory and I/O as its full-core sibling but exposes a fraction of the cores for licensing. For Oracle Database licensed by Processor, that is a legitimate route to cut the license count by up to 75% — and most enterprises migrate without ever configuring it."
"The failover rule lets you run an unlicensed standby for up to ten separate days per year — not a continuous 90-day block, as Oracle's sales team often implies. Misread it, leave a standby running past the limit, and you've created production deployment exposure on infrastructure you thought was free."
54 pages. Immediate access. No spam — only buyer-side Oracle licensing intelligence from our advisory team.
Oracle's GLAS team will count your vCPUs by a policy your contract never agreed to. Our Cloud & OCI Advisory service validates your BYOL position before you migrate, architects for the lowest defensible license count, and represents you if Oracle disputes it. Explore our Oracle Cloud Licensing Guide for the full picture.