The cloud clause is small, often buried, and decisive. Read it early and you control the outcome. Discover it at the window and you are negotiating with no runway left.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
Auditing your cloud clause means reading the certification provisions, the definitions of authorised cloud environments, and every amendment together to establish whether public cloud counts, which providers are named, whether a continuous running requirement applies, and what evidence is demanded. Do this twelve to eighteen months before exit. The clause decides whether substantial cloud estate becomes permanent entitlement or counts for nothing, and acting on it takes time you only have if you read it early.
Most ULA holders read their agreement for the headline terms: the products, the term, the fee, the certification mechanics. The cloud clause is easy to skim past because it is short and technical, yet it can determine the fate of a large slice of the certified count. If a meaningful share of your Oracle estate runs in AWS or Azure, the difference between a clause that lets it count and one that excludes it can be worth a great deal of permanent entitlement. That makes the cloud clause worth a dedicated, careful read of its own, separate from the general review.
The reason this read has to happen early is that almost every outcome it produces requires action, and action requires runway. If the clause imposes a continuous running requirement, qualifying estate has to be in place a year ahead. If it excludes public cloud, workloads may need to be repatriated or moved before the window. If it is silent, the position needs to be resolved while there is still time to clarify it. None of these moves is available if the clause is first read in the final weeks of the term.
It is rarely in a single, clearly labelled place. Cloud counting terms typically appear across three areas of the agreement, and a thorough audit reads all of them together.
Reading only one of these gives a partial and sometimes misleading picture. A permissive sentence in the body can be narrowed by a definition, and a silent body can be qualified by an amendment. The audit is the act of reading them as one instrument.
The cloud clause is read across the whole agreement, not in one paragraph, and it is read early enough to act on. A clause understood with runway is a clause you can plan around. A clause understood at the window is a constraint you simply absorb.
A useful cloud clause audit resolves five questions, each of which changes the move you should make before exit.
The table below shows how the answers to those questions translate into a move before exit for an anonymized example. The mapping is indicative and exists to show the logic, not to represent any real engagement, and your move depends entirely on your own wording.
| What the audit finds | The move before exit |
|---|---|
| Counts with 365 day threshold | Ensure estate is in place early and evidenced |
| Public cloud excluded | Repatriate on premises or move to OCI |
| Provider not named | Resolve scope or relocate to a counting environment |
| Silent clause | Analyse and clarify before the window |
Indicative only. The right move for your estate depends entirely on your cloud clause, your provider mix, and your timeline. The point is that every audit finding has a corresponding action, and every action needs time.
Auditing the cloud clause is the first move in any cloud aware exit, and it has to happen while there is runway to act on what it reveals. Pull the certification provisions, the definitions, and every amendment, answer the five questions, and decide your move. For the AWS specific reading, see does AWS count toward your certification, handle standby estate in cloud DR and the certification count, and ground the approach in our ULA exit strategy guide.
Book a ULA assessment and we will audit your cloud clause across the whole agreement, answer the five questions, and map the moves that keep your cloud estate in the certified count.