Oracle and Microsoft have expanded their partnership to deliver Oracle database services running on Oracle Cloud Infrastructure (OCI), collocated in Microsoft data centers. Azure customers can now procure, deploy, and use Oracle database services running on OCI within the native Azure portal and APIs, giving them an OCI-in-Azure-like experience. Here are some of the key benefits of Oracle Database@Azure.
Oracle Exadata Database Service will be the first available product in this offering. We expect this portfolio to grow rapidly with additional products.
|Exadata Cloud Infrastructure - Quarter Rack - X9M
|Exadata Cloud Infrastructure - Database Server - X9M Hosted Environment Per Hour
|Exadata Cloud Infrastructure - Storage Server - X9M Hosted Environment Per Hour
|Exadata Database OCPU - Dedicated Infrastructure OCPU Per Hour
|Exadata Database OCPU - Dedicated Infrastructure - BYOL OCPU Per Hour
|Oracle Cloud Infrastructure - Object Storage - Requests
|Oracle Cloud Infrastructure - Object Storage - Storage
All other Oracle Cloud part numbers require a valid Universal Credit commitment, available only with OCI.
Migrating to this offering is like migrating to OCI as the database service runs on OCI. Oracle provides proven database migration strategies, including automated migration solutions such as Oracle Zero Downtime Migration and powerful tools such as Oracle Data Guard and Oracle Cloud Infrastructure GoldenGate..
Oracle Database@Azure is now available in the Microsoft Azure East US region (two availability zones). The service will be available in additional regions in 2024, starting with Germany West Central, UK South, Australia East, Japan East, Canada Central, Brazil South, France Central, Central US, and South Central US. Oracle and Microsoft will continue to add availability in more regions to meet customer demand. We encourage customers to share any requirements for additional regions with their Oracle or Microsoft account team.
Yes. Please contact your partner service provider or Oracle Sales for more information.
If you’re interested in becoming a partner service provider or would like to learn more, you can find the latest and developing information on our website or contact your Oracle representative.
Exadata X9M will be supported at general availability (GA).
The provisioning of Oracle Database on Oracle Database@Azure is the same as on OCI, using the same UI flow, API calls, and so on; therefore, any database version currently supported and available on OCI is visible and available on Oracle Database@Azure infrastructure.
As the database is provisioned and managed in OCI, existing database tooling, such as backups and cloning, will be available.
Oracle Cloud Infrastructure Object Storage is the recommended backup service and is enabled to draw down on a customer’s MACC. Backing up to Oracle Database Autonomous Recovery Service or other storage (such as Azure native storage) requires a Universal Credit commitment with Oracle.
Oracle Database@Azure is a standard deployment, available within the Azure VNet. Oracle Database management tools, such as Data Pump, can be used to import data into the database from Azure database clients.
The dynamic routing gateway (DRG) used to provide the link between OCI and Azure network resources is housed within a tightly controlled service virtual cloud network (VCN) and can’t be updated. When provisioned, the Exadata VM cluster resources are attached to this DRG. If you have specific routing requirements, you can use local peering groups to connect to another VCN. This locally peered VCN can then be attached to a DRG you control. This DRG can be used for cross-region replication (see the question about data replication for disaster recovery (DR)).
Oracle Database@Azure is focused on high performance and low-latency workloads running in Azure. If the workload that requires low latency is in OCI, we recommend deploying Oracle Exadata Database Service on Dedicated Infrastructure in OCI. Where available, we recommend using Oracle Interconnect for Microsoft Azure to connect the OCI service and Oracle Database@Azure to meet low-latency needs.
As the database is created via OCI, Oracle Cloud Infrastructure Vault is used to house the system-generated or customer-generated key.
Yes, Oracle Database@Azure supports both single-tenant and multitenant environments. Oracle Exadata Database Service on Dedicated Infrastructure running inside Azure provides customers with dedicated Exadata compute and storage nodes, just as it does when running on OCI.
Yes. You can use existing Oracle Database licenses, including unlimited license agreements (ULAs) and Bring Your Own License (BYOL).
Yes, tenancies can either be new or existing. You’ll be given the choice during the onboarding process. As the Oracle Database@Azure service is physically present in Azure, existing Oracle Exadata Database Service on Dedicated Infrastructure environments will not be "moved," either physically or commercially. New Exadata infrastructures built within Azure will be seen in the existing OCI tenancy.
Yes. Using Oracle Database@Azure will accrue the same Oracle Support Rewards as using OCI directly.
Yes. You can use your Microsoft Azure Consumption Commitment (MACC) for Oracle Database@Azure. See Track your Microsoft Azure Consumption Commitment for more information.
For each Exadata cloud infrastructure instance you provision, you are billed for an initial 48 hours of consumption, then by the second after that. Each OCPU you add to the system is billed by the second, with a minimum usage period of one minute. If you terminate the cloud VM cluster and don’t terminate the cloud Exadata infrastructure resource, billing continues for the infrastructure resource.
Oracle consumption maps 1:1 to your Microsoft Azure Consumption Commitment (MACC).
The practical minimum for purchasing Exadata on Oracle Database@Azure is as follows:
As is standard with Oracle Exadata Database Service, each Oracle Database Exadata infrastructure shape/instance has a minimum service period of 48 hours.
At GA, there is no Free Tier option.
Any OCI cross-region traffic that normally incurs network bandwidth costs will be billed and metered in OCI (for example, a customer with cross-region disaster recovery using Oracle Database@Azure in region one and region two would incur network traffic costs).
Oracle and Microsoft have developed a joint support model to ensure rapid response and resolution for mission-critical workloads. Customers can reach out to either Microsoft or Oracle support teams.
Oracle and Microsoft have partnered to provide you with a well-integrated Azure experience for deploying, managing, and using Oracle Database instances in Azure. For most day-to-day operations, you’ll be able to use native Azure tooling.
Oracle Database@Azure will be made available in multiple public Azure regions within a geography (for example, the US or Europe). Azure customers can use Oracle Data Guard to ensure data protection and disaster recovery.
Customers will have access to Oracle Real Application Clusters. Oracle Database@Azure will also be deployed in multiple availability zones (AZ) within an Azure region to help meet high availability (HA) needs.
No. Oracle owns the link, the management, and the traffic flowing between the Azure data center and the OCI parent data center. Azure and OCI management networks don’t intersect. Azure has no visibility past the termination point in the partner transfer equipment within the data center where Oracle connects. And vice versa, Oracle can’t see past this same point. The network link is treated as internal to Oracle.
Operator Access Control is available for Oracle Compute Cloud@Customer, Exadata Cloud@Customer, and Autonomous Exadata VM clusters on client virtual machines deployed on Oracle Autonomous Database on Exadata Cloud@Customer.
Oracle Database@Azure management is the same as Oracle Exadata Database Service on OCI; therefore, Operator Access Control isn’t applicable.
Making Oracle Autonomous Database available via Oracle Database@Azure is on the roadmap. Today, Azure customers can use Oracle Interconnect for Microsoft Azure to access the full functionality of Oracle Autonomous Database on OCI.
Oracle Autonomous Database Select AI now supports Azure OpenAI to translate business- or domain-specific questions into SQL queries. Customers can simply ask questions in any language without knowing where and how their data is stored to gain insights. Oracle Autonomous Database now integrates with Azure Service Fabric, enabling more-seamless Power BI and Oracle Autonomous Database workflows.
Oracle Database@Azure resources that are provisioned and managed via the Oracle Database resource provider in Azure can be operated and managed from the Azure console, API, SDK, or CLI.
Expansion of the resources and features managed by the Oracle resource provider are on the roadmap.
The Oracle Database@Azure infrastructure is identical to that in OCI; therefore, standard Exadata and Oracle Database sizing tools, such as Oracle Cloud Capacity Analytics, can be used.
The Oracle Database@Azure hardware is deployed in the availability zone of the Azure region equivalent to the availability domain (AD) in OCI. For Azure and OCI regions that have multiple AZs and ADs, the Oracle Database@Azure hardware will be deployed in AZs with a 1:1 mapping to the OCI AD.
The network between the Oracle Database@Azure deployment in Azure and its parent OCI site is dedicated, redundant, Oracle internally managed dark fiber, similar to OCI AD-to-AD network infrastructure. The connection between the Oracle Database@Azure onsite hardware and Azure is achieved via local connectivity through redundant network hardware direct to Azure network infrastructure.
Each Oracle Database@Azure deployment is connected to an OCI parent site. This link is used for the following:
The network between the OCI parent and Oracle Database@Azure infrastructure is considered an internal regional network; therefore, no traffic costs or throttling limits are in place. Any capacity and other limits imposed on Azure virtual networking are still in effect (for example, bandwidth between the delegated subnet and Azure Private Link is limited to 50 Gb/sec, affecting services such as Azure Blob Storage access).
No, Oracle Interconnect for Azure is a standalone Oracle service available for customers to consume when deploying Oracle and Azure cloud services that require interconnectivity. Oracle Database@Azure doesn’t use this network link.
Both the OCI-Azure interconnect and Oracle Database@Azure take advantage of the proximity between clouds; therefore, there may be significant overlap in future region rollouts.
If you wish to use other OCI services with Azure services, Oracle Interconnect for Azure will need to be configured.
All traffic between sites, including Oracle Database@Azure infrastructure, is encrypted.
Oracle Data Guard redo logs are shipped from the primary database to the standby database via the client subnet across customer-managed networks on OCI infrastructure.
* Incurs outbound data transfer costs.
Existing Exadata deployments will still be operational; however, customers won't be able to create, update, or delete resources. Any process or procedure relying on OCI-based services (for example, OCI Vault key lookup, database backups, and so on) will fail.
Metrics and logging shipped from OCI to Azure Monitor will be delayed, even though the Exadata deployment is functional.
It is expected that all control plane functionality will become unavailable.