After you certify, your unlimited right is gone and every Oracle workload in public cloud must be covered by a perpetual license you actually hold. Because cloud counting is contract specific, the same vCPUs that were free under the ULA can become your largest source of exposure the day after exit.
During the ULA, cloud deployment was unlimited and free. After certification it is licensed like everything else, under Oracle's authorized cloud policy for other providers and under separate terms for OCI. The risk is that nobody re reads the rules when the unlimited right ends.
Inside the ULA term you could deploy Oracle into AWS or Azure without counting anything, because the right was unlimited. The certification letter ends that. From the signing date your entitlement is the fixed perpetual count you certified, and any cloud instance running an in scope Oracle product consumes that entitlement exactly as an on premises server does. Nothing about the cloud workload changed. The licensing rule under it did.
This is also where the certification baseline matters. Whether those cloud instances counted toward the number you certified is a contract question. Many agreements require a deployment in an authorized cloud to have run for 365 continuous days before the certification date to count toward the baseline. If your busiest cloud estate was stood up four months before exit, it may have added nothing to your certified line while still consuming entitlement afterward. That is the gap to find before Oracle does.
Cloud is where unlimited habits survive longest. The teams running workloads in AWS, Azure, or OCI rarely see the certified count, so the first control after exit is making the line visible to them.
For non Oracle clouds, Oracle's authorized cloud policy converts virtual processors to a license requirement. The standard treatment counts two vCPUs as one processor license where hyperthreading is on, and one vCPU as one processor where it is not. OCI is governed by separate terms that are generally more favourable for core counting. Public cloud that is not named in the policy, and GCP in particular under many older contracts, sits in a grey zone where your specific agreement language governs. The figures below are indicative and show the shape of the conversion, not a quote for any estate.
| Environment | Deployed | Indicative license need |
|---|---|---|
| AWS, hyperthreading on | 64 vCPU | 32 processor licenses |
| Azure, hyperthreading on | 32 vCPU | 16 processor licenses |
| OCI OCPU | 16 OCPU | 16 processor licenses |
Read the conversion against your certified line, not against your old unlimited comfort. Sixteen here and thirty two there adds up quickly, and it is consumed from the same fixed pool that covers your data centre.
Inventory every Oracle workload in every cloud account, including the accounts owned by business units that never report to central IT. Convert each to its processor requirement under the policy that applies to that provider. Reconcile the total cloud requirement plus on premises against your certified line. Where you are over, decide deliberately: buy licenses to cover the workload, move it to OCI where core counting is kinder, repatriate it on premises where you already hold entitlement, or shut down what is not needed. Where you are clean, document it, because the audit two years out will ask you to prove exactly this.
Cloud compliance after exit is not a one time clean up. It is a control you run continuously, because cloud is the easiest place to drift back above the line. Set the inventory, set the conversion, and set the review cadence early. The wider playbook sits in our post certification audit defense guide, and two companion notes connect directly to this one: growth after certification and the compliance line and the annual self review that prevents findings.
It depends on your contract. Many ULAs require an authorized cloud deployment to run for 365 continuous days to count toward the certification baseline, some exclude public cloud entirely, and many are silent on certain providers. Silence is not inclusion.
After certification your unlimited right is gone, so cloud instances are licensed under Oracle's authorized cloud policy, which converts vCPUs to a processor requirement. You must hold enough perpetual licenses from your certified count, or buy more, to cover what runs.
Oracle treats its own cloud, OCI, under separate terms that are usually more favourable for core counting than the authorized cloud policy for other providers. That difference can change where it is cheapest to run a workload after exit.
We inventory every Oracle workload across your cloud accounts, convert it to a defensible license requirement, and reconcile it to your certified line. Book a confidential assessment.