Cloud is one of the easiest places to lose certified processors, because the rules are contract specific and the errors are quiet. Assuming cloud does not count, missing a continuous run date, decommissioning too early, or failing to evidence the vCPUs each removes real capacity from the number you declare.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
Because cloud counting is contract specific and the conditions are easy to miss. On premises deployment is visible and stable, but cloud is dynamic, governed by a clause many teams never read, and subject to timing rules that quietly disqualify capacity. The result is a count that should include cloud and does not, surrendering perpetual entitlement that cost nothing to certify. These errors are avoidable, because every one of them comes down to reading the cloud clause early and managing the window deliberately. The mechanics of how cloud does count sit in counting vCPUs in authorized cloud environments.
Cloud that qualifies and is left out is free entitlement surrendered. Because support stays flat at certification, every cloud processor you fail to count is value given up for nothing, and capacity you may have to buy again later.
The most expensive assumption is that public cloud is simply outside the count. Many ULAs allow deployments in authorized environments such as AWS and Azure to count toward the baseline when conditions are met. Treating all cloud as excluded without reading the clause throws away qualifying capacity. The opposite error, counting cloud the contract excludes, creates exposure, so the rule is to read, not assume.
Where the contract requires a continuous run period, often 365 days, an instance must have been running long enough by the certification date to qualify. Teams that spin up cloud in the final months find it does not count, because it has not met the condition. The fix is timing: qualifying cloud has to be established well over a year before the exit, which is why this belongs in early planning.
The mirror of the timing problem is shutting down cloud that would have counted. An instance retired or resized before the certification date, or before it completes its continuous run, drops out of the count. During the window, qualifying cloud should be kept running and stable rather than optimised away.
Cloud capacity converts to processor licenses under the cloud policy, commonly two vCPUs to one processor with hyper threading on. Counting vCPUs as processors one for one, or miscounting the instance sizes, understates the cloud contribution. The conversion has to be applied correctly to each instance to claim the full number.
Even qualifying cloud needs proof. Run periods, instance configurations, vCPU counts, and the dates that satisfy any continuous run condition are the evidence that the cloud belongs in the count and survives later scrutiny. Cloud claimed without that file is fragile, which connects to the broader risk we cover in licensing cloud instances post ULA.
| Mistake | What it costs | The fix |
|---|---|---|
| Assuming cloud is out | Qualifying cloud surrendered | Read the cloud clause early |
| Missing the run condition | Cloud disqualified on timing | Establish cloud well before exit |
| Decommissioning early | Qualifying instances dropped | Keep cloud running through the window |
| Wrong vCPU conversion | Understated cloud processors | Apply the policy ratio per instance |
| No cloud evidence | Count fragile under review | Document run periods and configs |
Whether your cloud qualifies depends on your contract language and the cloud policy version that apply, so treat these as the errors to rule out rather than a verdict on your estate.
Take an indicative case. An organisation runs an authorized cloud estate converting to 200 processor licenses. It assumes cloud does not count and excludes all of it. An early read of the clause would have shown that 150 of those processors, on instances that met the 365 day run condition, qualified for the baseline. By excluding them, the count came in 150 processors low, surrendering free entitlement. A separate 50 processors, on instances spun up four months before exit, genuinely did not qualify and were correctly out. The lesson is precise: the loss was not the 50 that could not count, but the 150 that could and were assumed away. The figures are indicative, but the shape, qualifying cloud lost to assumption, is the common one.
Every cloud counting mistake has the same root and the same fix: read the cloud clause early and manage the window on purpose. Identify which instances will meet any continuous run condition by the certification date, keep them running, convert vCPUs correctly, and document the evidence. Where cloud will not count but the workload is permanent, repatriate it on premises or move it to OCI before exit so it does. The full method, including these moves, lives in our pillar, the ULA exit strategy guide.
Cloud shrinks a count quietly, through assumption and timing rather than obvious error. Read the clause, plan the continuous run dates, keep qualifying instances running, convert vCPUs correctly, and evidence everything. Cloud counted right is free entitlement claimed. Cloud assumed away is free entitlement lost, and the only count you keep is the one you defend at exit.
Usually because the team assumes cloud does not count, misses a continuous run condition, decommissions qualifying instances too early, or fails to evidence the vCPUs. Each removes real cloud capacity from the certified number, and because the contract is specific, the loss is avoidable with an early read of the cloud clause.
Read the cloud clause early, identify which instances will meet any continuous run condition by the certification date, keep qualifying instances running through the window, convert vCPUs correctly, and document run periods and configurations as evidence. Where cloud is excluded, repatriate or move to OCI before exit so it counts.
Book a confidential assessment and we will find the cloud capacity your certification is entitled to count before the window closes.