Many Oracle ULAs name AWS and Azure in their cloud counting language and say nothing about Google Cloud. Silence is not inclusion. Treating an unaddressed platform as if it counts is one of the simplest ways to strand real capacity at exit, and it is avoidable with time to plan.
Not automatically. Silence is not inclusion. If the cloud counting language names AWS and Azure but says nothing about Google Cloud, you cannot assume a GCP deployment will certify. The safe reading is that an unaddressed platform is unaddressed, and the position has to be tested against the exact wording of your agreement before exit, not after. A contract that is silent leaves a gap, not a permission.
In ULA work, what the contract does not say is as important as what it does. An assumption that silence means yes is the assumption that turns real capacity into a zero at certification.
Oracle's authorized cloud environment policy has historically named AWS and Azure, and a great many ULA cloud clauses were drafted around that framing. Google Cloud arrived in the enterprise picture later and is frequently not addressed at all in older agreements. So a clause that carefully sets out how AWS and Azure deployments count can be completely silent on GCP. That silence is not a quiet yes. It means the platform was never agreed as a counting environment, and a deployment there sits outside the language that gives other cloud deployments their certainty.
A deployment on a platform your contract does not address carries counting risk. You may believe it should count, and you may even be able to argue it, but you are arguing rather than relying on agreed language. At certification that is a weak place to be, because the burden is on you to support the number and Oracle reads its own contracts narrowly. The practical effect is that GCP capacity in a silent contract should not be treated as certain entitlement until the clause has been read and the position assessed. Planning around a number you cannot defend is how organizations get surprised at exit.
A logistics group ran a meaningful Oracle estate on Google Cloud and assumed it would count, because its ULA clearly allowed cloud deployments. On reading, the clause named only AWS and Azure. With a year of runway the group moved the workloads, part on premises and part to OCI, both completed and evidenced inside the term, so the capacity counted with certainty rather than on an argument. Had the silence been spotted in the final weeks, the deployment would have certified as nothing. Figures are indicative and depend on the specific contract language.
Establish exactly which platforms the contract names and on what conditions. If GCP is absent, you know the gap you are working with and can plan rather than assume.
Sometimes broader language elsewhere in the agreement supports a position. More often it does not. The point is to make a clear decision about whether the GCP deployment can be relied on to count, rather than drift into certification hoping it will.
Where the deployment cannot be relied on, repatriating the workload on premises or to OCI before exit converts it into capacity that counts, provided there is time for any continuous run clock to complete. That decision needs months, not weeks.
Which platforms your cloud clause names, what conditions it sets, and whether any broader language reaches Google Cloud all come from the specific agreement. Two firms with GCP deployments can reach opposite conclusions because their contracts read differently. In ULA work the answer almost always depends on the specific wording, so a silent contract is assessed against its own terms, never against a general assumption.
If any of your Oracle estate runs on Google Cloud, read your clause now while there is still runway to act. Start with the ULA exit strategy pillar guide, then read the cloud exposure after certification and evidence for cloud deployment counts.
Not automatically. Silence is not inclusion. If the cloud counting language names AWS and Azure but says nothing about Google Cloud, you cannot assume GCP deployments certify. The safe reading is that an unaddressed platform is unaddressed, and the position has to be tested against the exact wording before exit.
Oracle's authorized cloud environment policy has historically named AWS and Azure, and many ULA cloud clauses were drafted around it. Google Cloud is often simply not addressed. That leaves a gap rather than a permission, which is why GCP deployments in a silent contract carry counting risk.
Read the clause, decide whether the GCP deployment can be relied on to count, and if it cannot, consider repatriating the workload on premises or to OCI with enough runway for any continuous run clock. Treating a silent contract as if it includes GCP is the mistake that strands capacity at exit.
Book a confidential assessment and we will read your cloud clause, test where GCP stands, and plan the move if your capacity needs firmer ground.