CloudConnexa: Connect Google Cloud and Azure Networks Using Site-to-Site Networking

Configure routing in both cloud environments so resources in each network can communicate through CloudConnexa.

You'll add routes that direct traffic for the remote network to your local Network Connector.

For this example, we'll use the following subnet ranges:

Note: The Google Cloud and Azure VNet subnet ranges are reserved for documentation and aren't intended for actual deployments. Use your VPCs' actual private CIDR ranges and the subnet ranges assigned to your CloudConnexa WPC.

Configure routing for the Google Cloud VPC

First, configure routing in Google Cloud so resources in your Google Cloud VPC can reach the AWS VPC.

1. Sign in to the Google Cloud console.
2. Navigate to VPC network → Routes.
3. Select the Route management tab.
4. Select Create route.
5. Configure the route with the following settings:
   • Name: Enter a descriptive name, such as 'to-azure-vnet'.
   • Network: Select the VPC containing your Google Cloud Network Connector.
   • Destination IP range: Enter 198.51.100.0/24 (the subnet for the Azure VNet).
   • Priority: Use the appropriate route priority for your environment.
   • Next hop: Select the next-hop IP address option and enter the internal IP address of your Google Cloud Network Connector.
6. Select Create to save the route.
7. Add routes for your CloudConnexa WPC and Domain Routing subnets if your configuration requires them. Use the same Network Connector as the next hop.

Your Google Cloud VPC now has a route directing traffic for the Azure VNet to the local Network Connector.

Configure Routing for the Azure VNet

Next, configure routing in Azure so resources in your Azure VNet can reach the Google Cloud VPC.

1. Sign in to the Azure portal.
2. Navigate to Route tables.
3. Select the route table associated with the subnet containing the resources you want to connect to the Google Cloud VPC.
4. Under Settings, select Routes.
5. Select Add to create a route.
6. Configure the route with the following settings:
   • Route name: Enter a descriptive name, such as 'to-google-cloud-vpc'.
   • Destination type: Select IP Addresses, if prompted.
   • Destination IP addresses/CIDR ranges: 192.0.2.0/24 (the subnet for the Google Cloud VPC).
   • Next hop type: Select Virtual appliance.
   • Next hop address: Enter the private IP address of your Azure Network Connector.
7. Select Add to save the route.
8. Add routes for your CloudConnexa WPC and Domain Routing subnets if your configuration requires them. Use the same Azure Network Connector as the next hop.

Your Azure route table now directs traffic for the Google Cloud VPC to the local Network Connector.

Note: Ensure that the Azure route table is associated with each subnet containing resources that need connectivity to Google Cloud. If a route table isn't associated with the required subnet, its routes won't apply to that subnet.

Step 4: Verify network access settings

Before testing connectivity, check that both cloud environments and CloudConnexa allow traffic between the VPCs.

1. In Google Cloud, verify that IP forwarding is enabled for the VM instance running your Network Connector.
2. In Azure, verify that IP forwarding is enabled on the Network Connector's network interface and configured within the VM operating system.
3. Review your Google Cloud firewall rules and Azure network security groups (NSGs). Ensure they allow the traffic you want to exchange between the VPCs.
4. In the CloudConnexa Administration Portal, verify that your Access Groups allow the intended communication between the two Networks.
5. Confirm that both Network Connectors are connected to CloudConnexa.

Verify connectivity

Test the connection in both directions to confirm that resources in Google Cloud and Azure can communicate.

1. Connect to a VM instance in your Google Cloud VPC.
2. Test connectivity to the private IP address of a resource in your Azure VNet.
3. Connect to a VM instance in your Azure VNet.
4. Test connectivity to the private IP address of a resource in your Google Cloud VPC.
5. Verify that the applications or services you want to access are reachable across the connection.

If connectivity fails, check the Google Cloud and Azure routes, Google Cloud firewall rules, Azure NSGs, CloudConnexa Access Groups, and Network Connector status.

Note: If you're testing with ping, ensure that your firewall rules, NSGs, and host firewalls allow ICMP traffic. Otherwise, test using a protocol and port permitted by your configuration.