What it is
Oracle Database@Azure runs OCI database services (Exadata Database Service on dedicated infrastructure, Autonomous Database and others as they become available in your region) on OCI hardware inside Azure datacentres. You order it through Azure Marketplace, it appears as Azure resources, and the database plugs into a delegated subnet in your Azure VNet. The database itself is managed through OCI.
Similar offers exist for AWS and Google Cloud; the pattern below is the same.
When it fits
| Option | Good for | Watch out |
|---|---|---|
| Oracle Database@Azure | Exadata features (RAC, Smart Scan), low latency to Azure apps, Oracle-managed infrastructure | Region availability, Exadata minimum sizing |
| Oracle DB on Azure VMs | Small single-instance DBs, full OS control | No RAC; you manage HA, backups, patching |
| OCI + Azure interconnect | DBs in OCI, apps in Azure, in paired regions | Cross-cloud latency (low but not zero), two networks to run |
1. Onboarding
- Purchase from Azure Marketplace (private offer or pay-as-you-go).
- Link to a new or existing OCI tenancy — this is where database administration happens.
- Set up identity federation so Azure admins can use the OCI console (optional but recommended).
2. Networking
- Create a VNet and a delegated subnet for
Oracle.Database/networkAttachments. Size it for the client subnet IPs Exadata needs (check the documented sizing per VM cluster). - Apps in other VNets reach the database through VNet peering. Check the currently supported network topologies (for example, routing through NVAs or Virtual WAN) — they have changed over time.
- DNS: database hostnames are resolved from an OCI-managed private zone; integrate with your Azure Private DNS / resolver setup.
3. Provision
Create the Exadata infrastructure and then the VM cluster from the Azure portal (or Terraform azurerm resources), choosing ECPUs/OCPUs, storage and the Grid/DB version. Then create databases from the OCI console that the Azure resource links to.
4. Migrate
| Source | Method |
|---|---|
| On-prem Oracle, same platform | Data Guard physical standby, then switchover (ZDM physical online) |
| Different version or platform, or to Autonomous | Data Pump + GoldenGate (ZDM logical online) |
| Small DBs | Data Pump export/import |
Plan connectivity from on-prem to the delegated subnet (ExpressRoute) and enough bandwidth for the initial copy.
5. Operate
- Backups: Autonomous Recovery Service or Object Storage via the database service's automatic backups.
- Monitoring: Azure metrics for the resources plus OCI Database Management / Performance Hub for the database.
- Patching of the infrastructure is Oracle-managed in maintenance windows you schedule; database homes are patched by you through the OCI tooling.
- Billing is through Azure; Oracle licences can be BYOL or licence-included depending on the service.
Note
Responsibilities are split across two consoles. Write down who does what (network team in Azure, DBAs in OCI) before go-live.
Checklist
- Region and service availability confirmed
- Delegated subnet sized; topology supported
- DNS integration tested from app VNets
- Migration method chosen and rehearsed
- Backup, monitoring, patching ownership documented