General product information

What is Oracle Database@Azure?

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.

  • Run your workloads where you choose with fully managed Oracle database services running on OCI but inside Azure. Experience the highest level of Oracle Database performance, scale, and availability, as well as feature and pricing parity, with Oracle Exadata Database Service.
  • Migrate, modernize, and innovate with Oracle and Azure services using Oracle database services and Azure resources such as Azure Compute and Azure Kubernetes, with familiar application development tools and frameworks supported by Azure.
  • Simplify purchasing and operations. Purchase through the Azure Marketplace and use your Microsoft Azure Consumption Commitment (MACC). Monitor and troubleshoot with Oracle Database service logs, metrics, and events available directly in Azure.

Which Oracle products are available?

Oracle Exadata Database Service and Oracle Autonomous Database Serverless are available. We expect this portfolio to grow rapidly with additional products.

What part numbers are available from Oracle with Oracle Database@Azure

Part number Description
B93380 Exadata Cloud Infrastructure - Quarter Rack - X9M
B93381 Exadata Cloud Infrastructure - Database Server - X9M Hosted Environment Per Hour
B93382 Exadata Cloud Infrastructure - Storage Server - X9M Hosted Environment Per Hour
B88592 Exadata Database OCPU - Dedicated Infrastructure OCPU Per Hour
B88847 Exadata Database OCPU - Dedicated Infrastructure - BYOL OCPU Per Hour
B91627 Oracle Cloud Infrastructure - Object Storage - Requests
B91628 Oracle Cloud Infrastructure - Object Storage – Storage
B95701 Oracle Autonomous Data Warehouse - ECPU
B95703 Oracle Autonomous Data Warehouse - ECPU - BYOL
B95754 Oracle Autonomous Database Storage
B95702 Oracle Autonomous Transaction Processing - ECPU
B95704 Oracle Autonomous Transaction Processing - ECPU - BYOL
B95706 Oracle Autonomous Database Storage for Transaction Processing (Gigabyte Storage Capacity Per Month)
B88327 Outbound Data Transfer - Originating in North America, Europe, and UK
B93455 Outbound Data Transfer - Originating in APAC, Japan, and South America
B93456 Outbound Data Transfer - Originating in Middle East and Africa

All other Oracle Cloud part numbers are available only in OCI.

What are the commercial benefits for customers when they use Oracle Database@Azure?

  • Microsoft Azure Consumption Commitment (MACC): The purchase of Oracle Database@Azure will contribute toward a customer’s MACC.
  • Oracle Support Rewards: Existing Oracle customers with on-premises licenses will be eligible for Oracle Support Rewards.
  • Custom contract terms: Azure and Oracle customers can work with Oracle Sales to negotiate commercial terms.
  • Leverage existing Oracle licenses: Existing Oracle customers can use unlimited license agreements (ULAs) or Oracle Bring Your Own License (BYOL) to purchase Oracle Database@Azure, just like they can with Oracle Cloud Infrastructure.

How do I migrate to Oracle Database@Azure?

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..

Where can I use the service?

Please refer to the section covering Oracle Database@Azure regions for regional availability and the roadmap. We encourage customers to share any requirements for additional regions with their Oracle or Microsoft account team.

Can I work with my trusted partner service provider for Oracle Database@Azure?

Yes, for consulting services. Please note that Oracle Database@Azure is sold to customers directly via the Azure Marketplace and isn’t available for purchase through any other company or channel.

As an Oracle services partner, where can I learn more about Oracle Database@Azure?

If you're interested in becoming an Oracle consulting services partner as well as qualifying for a Service Expertise designation, you can find the latest information on the Oracle PartnerNetwork website. Service providers can purchase the offering directly, but not on behalf of customers.

What generation of Oracle Exadata Database Service on Dedicated Infrastructure is supported?

At present, Exadata X9M is supported.

What versions of Oracle Database will be available?

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.

What cloning functions will be available on day zero of the service?

As the database is provisioned and managed in OCI, existing database tooling, such as backups and cloning, will be available.

What backup options are available for Oracle Database@Azure?

Oracle Cloud Infrastructure Object Storage is the recommended backup service for automated database backup and will draw down on a customer’s MACC when OCI Object Storage is enabled. All other OCI backup SKUs, such as Oracle Database Autonomous Recovery Service, are only available on OCI.

Can I import data from Azure Blob Storage to the database?

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.

Can I update or request an update to the DRG?

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)).

What is the latency between Oracle Database@Azure and other OCI services?

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.

Can databases created on Oracle Database@Azure VM clusters connect to the vault in OCI, or can I manage keys in Azure Key Vault?

As the database is created via OCI, Oracle Cloud Infrastructure Vault is used to house the system-generated or customer-generated key.

Does the service support both single-tenant and multitenant environments?

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.

What compliance certifications are applicable to Oracle DatabaseDB@Azure?

Compliance is a shared responsibility between Oracle and Microsoft. Oracle Databse@Azure has been certified for industry standard compliance certifications. For detailed information on the compliance certifications, please visit Oracle Database@Azure Compliance Information

Billing and economics

How do I purchase Oracle Database@Azure services?

First, you work with Oracle Sales to negotiate the commercial terms, which are formalized in an ordering document that’s shared with you for you to review and accept. Next, Oracle creates a private offer and uploads it to the Azure Marketplace. You must purchase the private offer in the Azure Marketplace to provision the services.

You can purchase Oracle Database@Azure with an Oracle Database license included or use your existing Oracle Database licenses, including unlimited license agreements (ULAs) and Oracle Bring Your Own License (BYOL).

Can I use my existing Oracle Database license(s) with Oracle Database@Azure?

Yes. You can use existing Oracle Database licenses, including unlimited license agreements (ULAs) and Oracle Bring Your Own License (BYOL).

Does Oracle Database@Azure support new and existing OCI tenancies?

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.

Can Oracle Database@Azure customers make use of Oracle Support Rewards?

Yes. Using Oracle Database@Azure will accrue the same Oracle Support Rewards as using OCI directly.

Will the purchase of Oracle Database@Azure contribute toward my MACC?

Yes. You can use your Microsoft Azure Consumption Commitment (MACC) for Oracle Database@Azure. See Track your Microsoft Azure Consumption Commitment for more information.

How is consumption metered in OCI?

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.

Autonomous Database Serverless usage is billed according to the values of two parameters: compute and storage. You select values for these parameters when you provision or scale an Autonomous Database instance. See Autonomous Database Billing Summary for more details.

Oracle consumption maps 1:1 to your Microsoft Azure Consumption Commitment (MACC).

What is the minimum unit of purchase for a customer in Azure?

The practical minimum for purchasing Exadata on Oracle Database@Azure is as follows:

  • Exadata Cloud Infrastructure - Quarter Rack
    • Includes two database servers and three storage servers
  • Exadata Database OCPU (license included or BYOL, depending on circumstances)
    • Four OCPU minimum
  • Can scale by single database and storage server increments

What is the minimum service period for the Oracle Database@Azure service?

As is standard with Oracle Exadata Database Service, each Oracle Database Exadata infrastructure shape/instance has a minimum service period of 48 hours.

Is there a Free Tier for Oracle Database@Azure?

At present, there is no Free Tier option.

What is the standard practice for DR network traffic costs?

Any OCI cross-region traffic that normally incurs network bandwidth costs will draw down on a customer’s MACC (for example, a customer with cross-region disaster recovery using Oracle Database@Azure in region one and region two would incur network traffic costs).

Operations, support, and security

What is the support model for Oracle Database@Azure?

Oracle and Microsoft have developed a joint support model to ensure rapid response and resolution for mission-critical workloads. Customers will create all technical support requests directly with Oracle. Oracle will engage Microsoft support if needed.

How do I manage my Oracle Database(s) on Oracle Database@Azure?

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.

How can I achieve disaster recovery (DR) for Oracle Database@Azure?

Oracle Database@Azure will be made available in multiple availability zones within an Azure region and multiple Azure regions within a geography. Customers can use Oracle Data Guard to deploy DR solutions. Refer to the reference architecture to deploy a DR solution using Data Guard across availability zones within a region that meets the Oracle Maximum Availability Architecture (MAA) Gold standard. To learn more, refer to Oracle Maximum Availability Architecture for Oracle Database@Azure.

Can I use Azure availability zones with Oracle Database@Azure?

Oracle Database@Azure will be made available in multiple availability zones within an Azure region to meet high availability (HA) and disaster recovery requirements.

Could the link from Azure to OCI be seen as backdoor (to OCI or Azure)?

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.

Do we support Oracle Operator Access Control for Oracle Exadata Cloud@Customer? How is this done and described?

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.

Can the service be fully operated and managed from the Azure console or API?

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.

  • Exadata infrastructure is fully managed.
  • Exadata VM clusters are partially managed.
  • Oracle container databases and pluggable databases aren’t managed by the Oracle resource provider.

Expansion of the resources and features managed by the Oracle resource provider are on the roadmap.

What is the recommended DR size compared to the primary region?

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.

What is the relationship between the Azure region and the Oracle Database@Azure deployment?

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.

What is the network between Azure and OCI?

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.

What connectivity exists between the Azure data center and Oracle Cloud Infrastructure data center?

Each Oracle Database@Azure deployment is connected to an OCI parent site. This link is used for the following:

  • Control plane operations
    • Management of the infrastructure, including patching, monitoring, maintenance, and so on, by Oracle Cloud Operations
    • Oracle resource provider provisioning and control workflows
  • Data plane operations
    • Oracle Database backups to OCI Object Storage (as part of the optional automated backups from Oracle Database)
    • Transmission of the Oracle Data Guard redo log from primary to standby databases deployed in other locations

Are there throttling/capacity limits for the network (for example, if a customer replicates OCI Oracle Exadata Database Service on Dedicated Infrastructure with terabytes of data to Oracle Database@Azure)?

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).

Does the connection from Oracle Database@Azure to OCI traverse over Oracle Interconnect for Microsoft Azure? Does the service rely on the OCI-Azure interconnect?

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.

Is the traffic between Azure and OCI data centers encrypted?

All traffic between sites, including Oracle Database@Azure infrastructure, is encrypted.

What is the path for data replication for disaster recovery between the primary and DR database?

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.

  • If the standby database is hosted in the same Oracle Database@Azure AZ:
    • Redo log shipment is local to the Oracle Database@Azure network infrastructure hosted at Azure.
    • Routing uses local peering groups to the hub VCN (if using different OCI VCNs).
  • If the standby database is hosted in the same Azure region but different AZs:
    • Redo log shipment is via the parent OCI site (no cross-AZ traffic).
    • Routing uses local peering groups to the hub VCN (if using different OCI VCNs)
  • If the standby database is hosted in a different Oracle Database@Azure region:*
    • Redo log shipment is via the parent OCI site to the standby parent site to the standby Oracle Database@Azure infrastructure.
    • Routing uses local peering groups to the hub VCNs.

* Incurs outbound data transfer costs.

What happens if/when the connection to OCI fails? Will the data plane still be running and will data be accessible?

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.