Edit

Network topology and connectivity for Oracle Database@Azure - Migration connectivity design

Important

Deprecation notice: This article is deprecated and is no longer being updated. This article will be removed on October 30, 2026, to ensure the Cloud Adoption Framework remains focused on helping decision makers make better and faster cloud adoption decisions for their organization.

This does not affect the Oracle on Azure application landing zone accelerator on GitHub.

For alternative guidance, see Oracle on Azure architectures and product documentation.

If you would like to save this guidance, you can select Download a PDF at the bottom left of this page or download the files from GitHub.

A successful Oracle Exadata Database@Azure migration depends on secure, high-bandwidth connectivity between your source environment and Azure. This article outlines foundational networking strategies to support your migration. For comprehensive migration steps and methodologies, see Migrate Oracle workloads to Azure.

The following diagram illustrates how Oracle Exadata Database@Azure can connect to on-premises networks and other source environments.

Diagram that shows connectivity to Oracle Exadata Database@Azure from on-premises environments or other sources.

Note

The virtual network in the diagram includes both an Azure Storage account and Azure NetApp Files for illustration. Deployments usually use only one storage solution depending on workload and migration requirements.

Design considerations

  • High throughput requirements: Migrations often require large data transfers. Ensure that the selected network path can support sustained high throughput to minimize migration time.

  • Connectivity options: Both Azure ExpressRoute and VPN tunnels can be used to connect on-premises environments to Oracle Exadata Database@Azure. ExpressRoute provides more predictable performance and lower latency.

  • Shared connectivity effects: If the same ExpressRoute or VPN connection is used by multiple services, ensure adequate bandwidth to prevent contention or performance degradation.

Design recommendations

  • Prefer ExpressRoute over VPN: For on-premises to Oracle Exadata Database@Azure connectivity, we recommend ExpressRoute because of its dedicated bandwidth, predictable performance, lower latency, and increased security.

  • Capacity planning: Ensure that your chosen ExpressRoute or VPN connection has adequate bandwidth to support migration workloads and avoid service impact. If necessary, use bandwidth limiting.

Next step

After you plan and establish your network connectivity, proceed to Migrate Oracle workloads to Azure to begin or refine your migration strategy.