--- title: "Oracle Database@AWS, Azure & Google Cloud: The licensing traps to know before you move" description: Moving to Oracle Database@AWS, Azure or Google Cloud? Just because it's an Oracle service doesn't mean there are no licensing traps. Here's what to check before you move. image: https://cloud.invictuspartners.io/hubfs/Blog%20cover%207_1100x600.jpg --- [![](https://cloud.invictuspartners.io/hs-fs/hubfs/Invictus%20Partners%20Theme/Images/IP_Logo_Primary-Logo_Golden-Brown.png?width=1459&height=375&name=IP_Logo_Primary-Logo_Golden-Brown.png)](https://invictuspartners.io/) - About - [Our Story](https://invictuspartners.io/#our-story) - [Meet the Leadership Team](https://invictuspartners.io/leadership/) - [Careers](https://cloud.invictuspartners.com/careers) - [Services](https://invictuspartners.io/enterprise-software-licensing/) - [All Services](https://invictuspartners.io/enterprise-software-licensing/) - [ERP & Enterprise Software Consulting](https://invictuspartners.io/erp-consulting-services/) - [ERP Selection Consulting](https://invictuspartners.io/erp-consulting-services/) - [SI Partner Selection Consulting](https://invictuspartners.io/erp-implementation-partner-selection/) - [Independent Quality Assurance](https://invictuspartners.io/independent-quality-assurance/) - [SAP Cloud ERP Advisory](https://invictuspartners.io/sap-cloud-erp-advisory/) - [Oracle Fusion Cloud ERP Advisory](https://invictuspartners.io/oracle-cloud-erp-advisory/) - [Software Licence Management](https://invictuspartners.io/software-licence-management-services/) - [Vendor-specific Licence Management](https://invictuspartners.io/software-licensing-advisory/) - [Oracle Licence Management](https://invictuspartners.io/oracle-licence-management/) - [SAP Licence Management](https://invictuspartners.io/sap-licence-management/) - [Microsoft Licence Management](https://invictuspartners.io/microsoft-licence-management/) - [IBM Licence Management](https://invictuspartners.io/ibm-licence-management/) - [VMware Licence Management](https://invictuspartners.io/vmware-licence-management/) - [ServiceNow Licence Management](https://cloud.invictuspartners.io/industry-insights/invictuspartners.io/servicenow-consulting-services) - [Software Licence Audit Defence](https://invictuspartners.io/software-licence-audit-services/) - [Software Licence Optimisation](https://invictuspartners.io/software-licence-optimisation-services/) - [Software Asset Management](https://invictuspartners.io/software-asset-management-services/) - [SAM Tools Advisory](https://invictuspartners.io/sam-tool-services/) - [ServiceNow ITAM Optimisation](https://invictuspartners.io/servicenow-itam-optimisation/) - [Software Contract Negotiation](https://invictuspartners.io/software-contract-negotiation-consulting/) - [SaaS Licence Management](https://invictuspartners.io/saas-licence-management/) - [Cloud Licence Advisory](https://invictuspartners.io/cloud-licensing-services/) - [AWS Licence Advisory](https://invictuspartners.io/aws-licence-advisory/) - [Microsoft Azure Licence Advisory](https://invictuspartners.io/azure-licence-advisory/) - [Google Cloud Platform Licence Advisory](https://invictuspartners.io/gcp-licence-advisory/) - [Oracle Cloud Infrastructure Licence Advisory](https://invictuspartners.io/oracle-cloud-licence-advisory/) - [Third-Party Support Advisory](https://invictuspartners.io/third-party-support-advisory/) - [IT Supplier Management](https://invictuspartners.io/it-supplier-management/) - [IT Supplier Spend Analysis](https://invictuspartners.io/it-supplier-spend-analysis/) - [IT Vendor Management-as-a-Service](https://invictuspartners.io/it-vendor-management-services/) - [Services by Vendor](https://invictuspartners.io/software-licensing-advisory/) - [Oracle](https://invictuspartners.io/oracle-licence-management/) - [Oracle Licence Audit Simulation](https://invictuspartners.io/oracle-licence-audit-simulation/) - [Oracle Licence Management](https://invictuspartners.io/oracle-licence-management/) - [Oracle Cloud Infrastructure Consulting](https://invictuspartners.io/oracle-cloud-licence-advisory/) - [Oracle Fusion Cloud ERP](https://invictuspartners.io/oracle-cloud-erp-advisory/) - [SAP](https://invictuspartners.io/sap-licence-management/) - [SAP Licence Management](https://invictuspartners.io/sap-licence-management/) - [SAP Cloud ERP Advisory](https://invictuspartners.io/sap-cloud-erp-advisory/) - [Microsoft](https://invictuspartners.io/microsoft-licence-management/) - [Microsoft Licence Management](https://invictuspartners.io/microsoft-licence-management/) - [Microsoft Azure Consulting](https://invictuspartners.io/azure-licence-advisory/) - [IBM](https://invictuspartners.io/ibm-licence-management/) - [IBM Licence Management](https://invictuspartners.io/ibm-licence-management/) - [Broadcom](https://invictuspartners.io/vmware-licence-management/) - [Broadcom Licence Management](https://invictuspartners.io/vmware-licence-management/) - [AWS](https://invictuspartners.io/aws-licence-advisory/) - [AWS Cloud Consulting](https://invictuspartners.io/aws-licence-advisory/) - [AWS OLA](https://cloud.invictuspartners.io/awsola) - [Google](https://invictuspartners.io/gcp-licence-advisory/) - [Google Cloud Consulting](https://invictuspartners.io/gcp-licence-advisory/) - [ServiceNow](https://invictuspartners.io/servicenow-itam-optimisation/) - [ServiceNow Licence Management](https://cloud.invictuspartners.io/industry-insights/invictuspartners.io/servicenow-consulting-services) - [ServiceNow ITAM Consulting](https://invictuspartners.io/servicenow-itam-optimisation/) - [Advisory by Client Need](https://invictuspartners.io/vmware-licence-management/#) - [Help with software vendor audit](https://invictuspartners.io/software-licence-audit-services/) - [Cut software licence costs](https://invictuspartners.io/software-licence-optimisation-services/) - [Manage vendor relationships](https://invictuspartners.io/it-vendor-management-services/) - [Renegotiate software contracts](https://invictuspartners.io/software-contract-negotiation-consulting/) - [Optimise SAM capabilities and tools](https://invictuspartners.io/software-asset-management-services/) - [Migrate software to the cloud](https://invictuspartners.io/cloud-licensing-services/) - [Migrate to Third-Party Support](https://invictuspartners.io/third-party-support-advisory/) - [Evaluate next-generation ERP options](https://invictuspartners.io/erp-consulting-services/) - [Blog](https://cloud.invictuspartners.io/industry-insights) - [Collateral](https://invictuspartners.io/collateral/) - [All Collateral](https://invictuspartners.io/collateral/) - [Case Studies](https://cloud.invictuspartners.io/case-study) - [Datasheets](https://cloud.invictuspartners.io/datasheets) - [White Papers](https://cloud.invictuspartners.io/whitepapers) - [Contact](https://invictuspartners.io/contact/) # Oracle Database@AWS, Azure & Google Cloud: The licensing traps to know before you move ### Table of contents Your Oracle rep has probably already mentioned it. Oracle Database@ – recently rebranded as Oracle AI Database@ – puts Oracle's database, running on Oracle's own infrastructure, inside AWS, Microsoft Azure or Google Cloud. It's one of **Oracle's biggest priorities right now**, and its sales teams are actively encouraging customers to make the move. The appeal is simple. For years, organisations that had standardised on AWS, Azure or Google Cloud faced the challenge: keep Oracle databases on-premises, move them to Oracle's own cloud, or run them on general-purpose cloud infrastructure that wasn't built for them. Database@ removes that trade-off. **You get the full Oracle database, running where the rest of your cloud estate already lives.** However, moving from on-premise deployment to an Oracle@ service doesn’t remove the licensing risks. Your workload moves to the hyperscaler, but **Oracle's terms and conditions still apply**. And if you bring your own licences (BYOL), your support obligations and audit exposures follow, alongside service-specific licensing rules. Moving to Database@ is no guarantee of compliance or predictable costs. As many Oracle customers are now prioritising their move to these hyperscalers, it is important to understand the licensing ramifications that come with it. This blog will cover: 1. The **benefits of each Database@ option** – Azure, AWS and Google Cloud. 2. The **licensing considerations and traps** to watch out for. 3. What to do **before you sign**, so you stay in control. ## **What is Oracle AI Database@?** Oracle Database@ is essentially [Oracle Cloud Infrastructure (OCI)](https://invictuspartners.io/oracle-cloud-licence-advisory/) delivered inside someone else's cloud. Oracle's own infrastructure – Exadata, for most services – sits physically in the hyperscaler’s data centre and is managed by Oracle. You buy it through the hyperscaler's marketplace, it appears on your hyperscaler bill, and your applications connect to it over the hyperscaler's own network – which keeps latency low and avoids moving data between clouds. There are three versions: **Oracle AI Database@Azure**, **Oracle AI Database@AWS** and **Oracle AI Database@Google Cloud**, which we'll now outline in more detail. ## **Oracle Database@Azure** Microsoft Azure was the first hyperscaler to launch Oracle Database@, and it remains the most mature of the three, with the widest regional footprint and the full range of Oracle database services. ### Benefits of Oracle AI Database@Azure - **Move with minimal change:** The same Oracle database you run on-premises, including Real Application Clusters (RAC), so most applications move without being rearchitected. - **Fits Microsoft-first organisations:** Oracle databases plug into the identity, security and governance tools you already run – Microsoft Entra ID, Azure Key Vault, Microsoft Sentinel and Azure Policy. - **Data and AI integration:** Supports integration with Microsoft analytics and AI services, using connectors, mirroring or other configured integration path. - **One bill, one portal, joint support:** Billing and monitoring run through the Azure Portal, backed by a joint Oracle-Microsoft support model. - **Counts toward your Azure commitment:** Spend draws down your Microsoft Azure Consumption Commitment (MACC), which can help organisations at risk of under-consuming. ### **Licensing considerations before you migrate Oracle database to Azure** Oracle Database@Azure is licensed as an Oracle cloud service, not as Oracle software running on an Azure virtual machine. The rules that apply to Database@Azure are different from those that apply to Oracle on standard Azure infrastructure, so **organisations already running Oracle in Azure shouldn't assume their current approach carries over**. It also means you are **managing two commercial relationships at once**. It's no longer one vendor – you're dealing with two. Microsoft handles Azure billing and Azure infrastructure; **Oracle operates and maintains the underlying Oracle infrastructure**. Exadata also uses a shared responsibility model, with customers retaining database and VM management responsibilities. And while drawing down your Microsoft Azure Consumption Commitment is a genuine benefit, it shouldn't be the deciding factor. Burning through a cloud commitment faster is only a win if the underlying Oracle costs stack up. ## Oracle Database@AWS Oracle Database@AWS reached general availability in 2025 and has been expanding quickly. It offers Oracle Exadata Database Service and Autonomous AI Database, running inside AWS data centres. ### Benefits of Oracle AI Database@AWS - **Move Exadata workloads with minimal change:** Oracle positions Database@AWS as a like-for-like home for existing Exadata workloads, including RAC, with the same Exadata platform capabilities. - **Built for AWS-first organisations:** Oracle databases sit right next to the applications you run on Amazon EC2 and AWS container services, with very low latency between them. - **AI and analytics integration:** Connects to Amazon Bedrock and AWS analytics services, and can work with open data in Amazon S3 without building extract-and-load pipelines. - **Familiar tools and controls:** Manage it through the AWS Console, APIs and Terraform; control access with AWS IAM and encryption keys with AWS Key Management Service. - **One bill, collaborative support:** Oracle consumption flows through your AWS relationship and counts toward your AWS spending commitments, with support coordinated between Oracle and AWS. ### Licensing considerations before you migrate Oracle database to AWS Oracle Database@AWS spend counts toward your AWS commitments, but [Oracle's own FAQs](https://www.oracle.com/cloud/aws/faq/) confirms it does not count toward any existing Oracle or OCI commitments. If your organisation already holds Oracle cloud credits, Database@AWS won't help you use them. For organisations running Oracle on Amazon RDS, **moving to Database@AWS is not a like-for-like switch**. Licence requirements depend on the target service: Exadata Database Service requires Enterprise Edition licences for BYOL, while certain Autonomous Database services accept supported Standard Edition licences within defined limits. If you use RDS licence-included pricing, those licences do not transfer, you will need eligible licences for BYOL or Database@AWS licence-included pricing. Check the target service’s licensing requirements and total costs before committing. Database@AWS can work well for the right organisation, particularly one that is licence-constrained running Oracle on standard AWS infrastructure. But the running costs and minimum configurations are very different from RDS or EC2. Weigh any licensing upside against the full cost of running the service, and **don't rely on Oracle to point out the downsides**. ## Oracle Database@Google Cloud Oracle Database@Google Cloud launched in 2024 and offers a broad set of services: Exadata Database Service, Autonomous AI Database, Base Database Service and GoldenGate. Oracle positions it for organisations that want their Oracle transactional data working closely with Google's analytics and AI platforms. ### Benefits of Oracle AI Database@Google Cloud - **Move with minimal change:** Migrate on-premises Oracle databases with minimal rearchitecting, using Oracle's Zero Downtime Migration tooling. - **AI integration:** Gemini-powered applications can draw on live Oracle data. - **Key control:** Google Cloud supports Cloud KMS customer-managed keys. AWS also supports native KMS integration. - **One bill, coordinated support:** Billing runs through Google Cloud and counts toward your Google Cloud commitments, with support coordinated between Oracle and Google. - **Migration incentives:** Google Cloud's Rapid Migration Program (RaMP) and Oracle's Migration Accelerator can help offset migration costs for eligible workloads. ### Licensing considerations before you migrate Oracle database to Google Cloud With more service options comes more choice – and more to get right. **Exadata, Autonomous and Base Database Service are licensed and priced differently**, so the service you choose for each workload shapes your licence requirements as much as your performance. Oracle Database@Google Cloud currently has the smallest regional footprint of the three. Check that the services you need are available in the regions you need them, including for disaster recovery, before you commit – **a change of architecture later can mean a change in licensing too**. ## Oracle Database@ licensing traps to watch out for **Whichever hyperscaler you choose, the same Oracle licensing rules sit underneath.** Moving to Database@ doesn’t remove your Oracle licensing obligations, it just changes where they sit. These are the traps most likely to catch organisations out. ### 1. Licence-included vs. BYOL You can pay for Oracle Database@ in one of two ways: licence-included pricing or bring your own licence (BYOL). With **licence-included** pricing, the Oracle licences and support are built into the hourly rate, along with many database options – on Exadata, that includes Real Application Clusters (RAC) and In-Memory. You pay for what you use, which makes it a good fit for new workloads, short-term needs, and gaps in your licence estate. With **BYOL**, you apply licences you already own and pay a lower rate. For anyone with a large Oracle estate, that looks like the obvious option. It often isn’t that simple: those licences must stay on Oracle support for as long as you run them, every option and pack you use needs its own supported licence, and once applied, the licences are locked to that service. BYOL works best for organisations with surplus, supported Enterprise Edition licences. **Many organisations will end up with a mix** – BYOL where they hold the right licences, licence-included where they don't. The key is working out which is which before you migrate, not after. ### 2. Licensing every option BYOL means bringing a licence for everything you use – not just the database itself, but every database option and management pack switched on in your environment. Licence-included pricing bundles some of these in; BYOL does not. **Options and packs enabled out of habit are a familiar source of audit findings** on-premises, and the same risk follows you to the cloud. ### 3. Paying double Most migrations involve a period where the old and new databases run at the same time. Oracle gives BYOL customers up to 100 days from the BYOL Service activation to complete that transition. Dual use ends when the transition finishes or 100 days elapse, whichever happens first. After that, you **need enough licences to cover both environments**, so a migration that slips can quickly become a compliance problem. ### 4. Early decision lock-in Once you've applied licences to a BYOL service, Oracle's terms don't let you move them to a different BYOL service. **The allocation decisions you make at the start shape your flexibility for the life of the deployment**. Confirming reassignment rights in the applicable contract is a must! ### 5. Audit risk Oracle’s terms are clear that your licence usage on Database@ can be verified in an audit, and that you remain responsible for complying with your licence restrictions. Database@ doesn’t take you outside Oracle’s audit reach. In fact, **a major migration can raise your audit risk: it draws attention to your licence position**, and any gaps that existed on-premises come with you. ## What to do before you commit to Oracle AI Database ### Know your Oracle licensing position Understand what you actually own: which licences are on Oracle support, which are on [third-party support](https://invictuspartners.io/third-party-support-advisory/), which options and packs you hold, and what each licence is currently covering. Every Oracle Database@ decision depends on this baseline. ### Compare the commercial options Model licence-included against BYOL for your real workloads, including the ongoing support costs BYOL locks in. It's also worth comparing Oracle Database@ with running Oracle on your hyperscaler's standard infrastructure. ### Get the answers in writing Get written confirmation from Oracle on licence counting, workload changes and the treatment of existing commitments. Treat vague answers as a warning sign. ### Get an independent review Oracle and the hyperscalers offer funded migration assessments to build your business case. They can be useful, but it’s worth thinking about who benefits from the migration going ahead. The vendor that gains from your move shouldn't be the one modelling what it will cost you. It is best to engage independent licensing specialists, like Invictus Partners, who can offer you honest and unbiased advice. ## The bottom line Oracle Database@Azure, Oracle Database@AWS, and Oracle Database@Google Cloud solve a real problem. They let organisations run Oracle where the rest of their cloud estate already operates, without giving up the database features they depend on. **For many Oracle customers, that will be the right move.** But Database@ is still an Oracle service, governed by Oracle's licensing terms. The organisations that get the most from Database@ will be the ones that **get cloud-ready from a licensing perspective before they migrate**. ![ODCS thumbnail](https://cloud.invictuspartners.io/hs-fs/hubfs/ODCS%20thumbnail.jpg?height=2000&name=ODCS%20thumbnail.jpg) ### Download the Oracle Database@ Licensing Cheat Sheet We've put the most critical Oracle Database@ licensing info from the blog into a handy 2-page cheat sheet that you can download and take with you. Just pop your email in below and it's yours. ![Chat calendar and letter](https://cloud.invictuspartners.io/hs-fs/hubfs/Invictus%20Partners%20Theme/Images/Chat%20calendar%20and%20letter.png?width=2539&height=1573&name=Chat%20calendar%20and%20letter.png) #### Find out about Invictus Partners services - [Software Licence Management](https://invictuspartners.io/software-licence-management-services/) - [Software Asset Management](https://invictuspartners.io/software-asset-management-services/) - [Cloud Licence Advisory](https://invictuspartners.io/cloud-licensing-services/) - [Next-Gen ERP Advisory](https://invictuspartners.io/erp-consulting-services/) - [Third Party Support Licence Advisory](https://invictuspartners.io/third-party-support-advisory/) [All services](https://invictuspartners.io/enterprise-software-licensing) ## Got questions about Invictus Partners Enterprise Software Licensing Advisory? ![IP\_Logo\_Secondary-Logo\_Golden-Brown](https://cloud.invictuspartners.io/hs-fs/hubfs/Invictus%20Partners%20Theme/Images/IP_Logo_Secondary-Logo_Golden-Brown.png?width=400&height=30&name=IP_Logo_Secondary-Logo_Golden-Brown.png) ##### Melbourne L5, 111 Cecil St South Melbourne Victoria 3205 ##### Sydney L7, 3 Spring St Sydney New South Wales 2000 ##### Singapore 1 Fullerton Road #02-01 One Fullerton Singapore 049213 ##### New York 1740 Broadway 15th Floor, New York New York 10019 ##### London 1st Floor 124 Cleveland Street London W1T 6PH ##### Cape Town 50 Long Street Cape Town South Africa 8000 Copyright © 2023. Invictus Partners Pty. Ltd. All Rights Reserved. | [Privacy Policy](https://invictuspartners.io/privacy/) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Invictus Partners", "url" : "https://cloud.invictuspartners.io/industry-insights/author/invictus-partners" }, "dateModified" : "2026-10-28T07:41:08.329Z", "datePublished" : "2026-10-28T07:11:32.000Z", "headline" : "Oracle Database@AWS, Azure & Google Cloud: The licensing traps to know before you move", "image" : [ "https://cloud.invictuspartners.io/hubfs/Blog%20cover%207_1100x600.jpg" ], "mainEntityOfPage" : { "@id" : "https://cloud.invictuspartners.io/industry-insights/oracle-database-licensing", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://cloud.invictuspartners.io/hubfs/IP_Logo_Primary_Logo_Golden_Brown-removebg-preview%20(1).png" }, "name" : "Invictus Partners" } } ```