Set up a direct interconnection between Azure and Oracle Cloud Infrastructure
Applies to: ✔️ Linux VMs
To create an integrated multicloud experience, Microsoft and Oracle offer direct interconnection between Azure and Oracle Cloud Infrastructure (OCI) through ExpressRoute and FastConnect. Through the ExpressRoute and FastConnect interconnection, you can experience low latency, high throughput, private direct connectivity between the two clouds.
Oracle has certified these applications to run in Azure when using the Azure / Oracle Cloud interconnect solution:
- E-Business Suite
- JD Edwards EnterpriseOne
- Oracle Retail applications
- Oracle Hyperion Financial Management
The following image shows a high-level overview of the interconnection:
The ExpressRoute connection seen in the diagram is a regular ExpressRoute circuit and supports all fuctionality, such as Global Reach.
To establish connectivity between Azure and OCI, you must have an active Azure subscription and an active OCI tenancy.
Connectivity is only possible where an Azure ExpressRoute peering location is in proximity to or in the same peering location as the OCI FastConnect. See Region Availability.
Configure direct connectivity between ExpressRoute and FastConnect
Create a standard ExpressRoute circuit on your Azure subscription under a resource group. For more information, see Create and modify an ExpressRoute circuit.
In the Azure portal, enter ExpressRoute in the search bar, and then select ExpressRoute circuits.
Under Express Route circuits, select Create.
Select your subscription, enter or create a resource group, and enter a name for your ExpressRoute. Select Next: Configuration to continue.
Select Oracle Cloud FastConnect as the service provider and select your peering location.
An Azure ExpressRoute circuit provides granular bandwidth options. FastConnect supports 1, 2, 5, or 10 Gbps. For Bandwidth, choose one of these matching bandwidth options.
Select Review + create to create your ExpressRoute.
After you create your ExpressRoute, configure direct connectivity between ExpressRoute and FastConnect.
Go to your new ExpressRoute and find the Service key. You need to provide the key while configuring your FastConnect circuit.
You are billed for ExpressRoute charges as soon as the ExpressRoute circuit is provisioned, even if Provider Status is Not Provisioned.
Carve out two private IP address spaces of
/30each. Be sure that the spaces don't overlap with your Azure virtual network or OCI virtual cloud network IP Address space. The first IP address space is the primary address space and the second IP address space is the secondary address space. You need these addresses when you configure your FastConnect circuit.
Create a Dynamic Routing Gateway (DRG). You need this gateway when you create your FastConnect circuit. For more information, see Dynamic Routing Gateway.
Create a FastConnect circuit under your Oracle tenant. For more information, see Access to Microsoft Azure.
- Under FastConnect configuration, select Microsoft Azure: ExpressRoute as the provider.
- Select the Dynamic Routing Gateway that you provisioned in the previous step.
- Select the bandwidth to be provisioned. For optimal performance, the bandwidth must match the bandwidth selected when creating the ExpressRoute circuit.
- In Provider Service Key, paste the ExpressRoute service key.
- Use the first
/30private IP address space carved out in a previous step for the Primary BGP IP Address and the second
/30private IP address space for the Secondary BGP IP Address.
- Assign the first useable address of the two ranges for the Oracle BGP IP Address (primary and secondary) and the second address to the customer BGP IP Address from a FastConnect perspective. The first useable IP address is the second IP address in the
/30address space. Microsoft reserves the first IP address.
- Select Create.
Complete linking the FastConnect to virtual cloud network under your Oracle tenant with Dynamic Routing Gateway, using Route Table.
Navigate to Azure and ensure that the Provider Status for your ExpressRoute circuit has changed to Provisioned and that a peering of type Azure private has been provisioned. This status is a prerequisite for the following step.
Select the Azure private peering. You see the peering details have automatically been configured based on the information you entered when setting up your FastConnect circuit.
Connect virtual network to ExpressRoute
Create a virtual network and virtual network gateway, if you haven't already. For more information, see Configure a virtual network gateway for ExpressRoute using the Azure portal.
Once you have completed the network configuration, you can verify your configuration by selecting Get ARP Records and Get route table under the ExpressRoute Private peering page in the Azure portal.
Microsoft has created Terraform scripts to enable automated deployment of the network interconnect. The Terraform scripts need to authenticate with Azure before they run, because they require adequate permissions on the Azure subscription. Authentication can be performed using an Microsoft Entra service principal or using the Azure CLI. For more information, see CLI Authentication.
For the Terraform scripts and related documentation to deploy the inter-connect, see Azure-OCI Cloud Inter-Connect.
Installing agents on both the clouds, you can use Azure Network Performance Monitor to monitor the performance of the end-to-end network. Network Performance Monitor helps you to readily identify network issues, and helps eliminate them.
Delete the interconnect link
To delete the interconnect, perform these steps in the order given. Failure to do so results in a failed state ExpressRoute circuit.
- Delete the ExpressRoute connection. Delete the connection by selecting the Delete icon on the page for your connection. For more information, see Clean up resources.
- Delete the Oracle FastConnect from the Oracle Cloud Console.
- Once the Oracle FastConnect circuit has been deleted, you can delete the Azure ExpressRoute circuit.
The delete and deprovisioning process is complete.