Whether Oracle running on Microsoft Azure counts toward your ULA certification depends entirely on the contract. Many ULAs require a public cloud deployment to run for 365 continuous days before the term ends, and some exclude public cloud altogether, so the clause decides the answer.
If a meaningful share of your Oracle estate runs on Azure, the question of whether it counts at certification is worth real money. Cloud workloads can represent hundreds of processors of potential certified value. They can also be excluded by a single clause that nobody read until the exit was weeks away. This article explains how Oracle ULAs typically treat public cloud, why the 365 day rule catches so many teams, and what to do once you know where your contract stands.
It depends on your contract, and that is not a hedge, it is the controlling fact. Oracle ULAs vary in how they treat authorised public cloud environments. A common pattern allows deployments in named providers such as Azure and AWS to count, but only if they were running for the 365 continuous days before certification. Another pattern excludes public cloud entirely, so an Azure workload contributes nothing to the certified number no matter how large it is. A third pattern is silence, where the agreement simply does not address public cloud, and silence is not the same as inclusion. The cloud clause in your specific ULA governs the outcome, not Oracle's general guidance or a sales conversation.
The 365 day rule is the clause that surprises the most organisations. Where it applies, a cloud deployment must have run continuously for the full year ending at certification to be eligible to count. The intent is to stop customers from spinning up large cloud footprints in the final weeks purely to inflate a count. The effect on a legitimate migration is the same: a workload moved to Azure ten months before the term ends may fall short of the 365 day threshold and be excluded, even though it is real, productive, and still running on the day you certify.
This is why the cloud clause has to be read early. If your contract carries a 365 day rule and you want Azure workloads to count, they need to be in place at least a year before the certification date. Discovering the rule with six months left removes the option entirely. The practical deadline for cloud decisions is therefore well ahead of the exit itself, which is the central reason we tell ULA holders to begin the exit review around 18 months out.
Three questions resolve most of the uncertainty, and you can answer them from the contract before you involve anyone else.
Look for defined terms covering public cloud, authorised cloud environments, or named providers. If Azure or a category that includes it is named as eligible, cloud counting is on the table. If the agreement is silent, treat that as exclusion until proven otherwise rather than assuming inclusion.
Find the timing condition. A 365 day continuous run requirement, a snapshot date, or a measurement window all change which Azure workloads qualify. The wording here is decisive, because it converts a question about size into a question about timing.
Cloud counting often uses a virtual processor or vCPU based method rather than the physical core factor model used on premises. The mapping from Azure virtual machine sizes to countable processors needs to follow the contract and any Oracle cloud counting policy the agreement references. Getting the method right matters as much as establishing eligibility, and we cover the evidence side in evidence for cloud deployment counts.
Consider an indicative retailer with a substantial Oracle estate on Azure. Two workloads have run on Azure for eighteen months and clear a 365 day rule comfortably. A third, larger workload migrated only eight months before the term ends. Under a contract with a 365 day rule, the first two count and the third does not, unless its on premises predecessor can be counted instead. The result is not about how much Oracle runs on Azure, it is about when it got there. The figures are indicative and the answer turns on the exact clause.
If your contract excludes Azure, or a workload misses the 365 day threshold, the value is not necessarily lost. Where cloud does not count, workloads can sometimes be repatriated to on premises infrastructure or moved to OCI before the exit so that they count under the rules that do apply. That decision has cost and timing consequences and it has to start early, which is the subject of when the ULA is silent on GCP and the wider repatriation question. The point is that an unfavourable cloud clause is a problem to solve months in advance, not a verdict to accept at the exit.
Azure is one provider in a contract specific picture. For the full exit framework that cloud decisions sit inside, start with our ULA exit strategy guide. For the parallel provider question, read does AWS count toward your certification, and for the case the contract does not mention at all, read when the ULA is silent on GCP. Because the Azure answer lives entirely in your clause, the safest next step is to have that clause read while there is still time to act on it.
It depends on your contract. Many Oracle ULAs require a public cloud deployment such as Azure to run for 365 continuous days before the term ends to count toward certification. Some agreements exclude public cloud entirely. The clause governs, not Oracle's later guidance.
It is a common clause requiring cloud deployments to run continuously for the 365 days before certification to be eligible to count. A workload provisioned late in the term may not qualify, which is why the cloud clause should be read at least 18 months before exit.
Send us your expiry date and we will read your cloud clause while there is still time to act on it.