Oracle Database@Azure: course overview
This section is a study companion for the Oracle Database@Azure deep-dive course. Each topic condenses one course video into original architecture notes, a responsibility view, and a short self-check, so the material stays reviewable for the DP-300 journey and for customer modernization conversations.
The course teaches an Oracle Cloud service that runs inside Azure datacenters. These notes are written in our own words for revision — they are not a transcript of the course. Always confirm region, networking, and commercial details against the linked Microsoft Learn pages before using them with a customer.
What Oracle Database@Azure is
Oracle Database@Azure lets customers run Oracle Cloud database services on Oracle Cloud Infrastructure (OCI) hardware that is physically deployed inside Microsoft Azure datacenters. The database service sits next to Azure resources and uses Azure networking, so applications, identity, and monitoring stay close to the data without a customer-built cross-cloud interconnect.
Key points to remember:
- The Oracle database service runs on OCI-managed infrastructure that is colocated in Azure datacenters.
- Customers provision and operate the service primarily through Azure, with some database tasks still using OCI tooling.
- Oracle and OCI operations teams manage the underlying infrastructure and service software.
Why it exists: the partnership timeline
The service is the current step in the Oracle and Microsoft multicloud partnership:
- Private interconnect. A low-latency network link first connected separate Azure and OCI environments.
- Oracle Database Service for Azure. A simpler experience reduced the manual cross-cloud network design work.
- Oracle Database@Azure. The Oracle database service is placed inside Azure datacenters, removing most of the customer-managed interconnect pattern.
The intent is to keep Oracle database performance, availability, scalability, and security while improving integration with Azure applications and operations.
Architecture at a glance
- The database service runs in Azure datacenters and connects through a delegated subnet in the customer's Azure virtual network.
- Azure-native tools such as Azure Monitor and Log Analytics collect supported metrics, events, and logs.
- Because the database service is colocated with Azure resources, network latency between Azure application endpoints and the database is very low.
- Support follows the boundary: Oracle and OCI handle the database service and infrastructure, while Azure handles Azure platform and networking components.
Responsibility split
| Owner | Responsibilities |
|---|---|
| Oracle / OCI | Operate the Exadata infrastructure, VM clusters, service software, and infrastructure updates; resolve Oracle and OCI database-service issues. |
| Customer | Purchase and provision the service, size the infrastructure, provision databases, load data, establish connectivity, support development, and monitor metrics and logs. |
| Microsoft / Azure support | Resolve Azure-side issues such as virtual network, bastion, virtual machines, and Azure Monitor. |
When to choose it
Oracle Database@Azure fits best when a customer wants to keep Oracle database technology and Exadata-class performance, but wants the database closer to Azure applications, networking, monitoring, and commercial operations. Validate availability, region fit, network requirements, commercial access, and operational ownership before recommending it. It is not a click-to-create lab resource — it requires subscription, billing, and Oracle service onboarding.
Migration method selector
| Method | Best fit | Downtime | Complexity | Rollback strength | Notes |
|---|---|---|---|---|---|
| Data Pump | Smaller or logical export and import migrations | Medium to high | Low to medium | Good if the source is unchanged | Familiar, but downtime grows with size. |
| RMAN | Large physical backup and restore migrations | Medium | Medium | Strong | Suits Oracle-native physical movement. |
| Data Guard | Low-downtime Oracle-to-Oracle switchover | Low | High | Strong | Strong for mission-critical cutovers when source and target are compatible. |
| Zero Downtime Migration | Oracle-guided automation of migration paths | Low to medium | Medium | Depends on the chosen method | Helps standardize migration execution. |
| GoldenGate | High-change workloads and phased cutovers | Very low | High | Strong but operationally complex | Best for change-data-capture and staged cutovers. |
Course topics
| # | Topic | Status |
|---|---|---|
| 1 | Introduction to Oracle Database@Azure | Available |
| 2 | Use case scenarios for Oracle Database@Azure | Available |
| 3 | Oracle Database@Azure architecture | Available |
| 4 | Subscribe and onboard Oracle Database@Azure | Available |
| 5+ | Added as each course video is summarized | Planned |