Tutorial: Connect Your Azure VNet to CloudConnexa by Deploying a Connector
Overview
This tutorial walks you through deploying a Network Connector to an Azure virtual network (VNet) from the CloudConnexa Administration portal.
During deployment, you can select one of the following methods:
Native deployment: Sign in to your Microsoft Azure account from the Network Configuration Wizard and let CloudConnexa deploy the Connector directly.
Manual deployment: Download an Azure Resource Manager (ARM) template from CloudConnexa and deploy it from the Azure portal.
Both methods create an Azure virtual machine (VM) and install the Connector software to provide secure, private network access.
Before you begin
Before starting this tutorial, ensure you have:
A CloudConnexa account and Cloud ID.
An Azure subscription.
Permissions to create virtual machines and networking resources in Azure.
An existing Azure VNet and VNet subnet where you want to deploy the Connector.
An SSH public key in the resource group where CloudConnexa will deploy the Connector VM.
Step 1: Create a Network
To create a Network, follow the steps below:
Sign in to your WPC's Administration portal by entering your Cloud ID in a web browser (for example,
company_name.openvpn.com).Navigate to Networks.
Select Add Network and select your desired network scenario.
Complete the Define Network page.
Select Next.
The Deploy Network Connector page displays.
Step 2: Select a deployment method
On the Deploy Network Connector page, select one of the following methods:
On the Deploy Network Connector page, select Azure from the drop-down.
The Native tab for Azure deployment is displayed by default.
Select one of the following deployment methods:
To authorize CloudConnexa to deploy the Connector directly to Azure, remain on the Native tab and continue to Option A: Deploy the Connector using the Native tab.
To download and deploy an ARM template yourself, select the Manual tab and continue to Option B: Deploy the Connector using the Manual tab.
Option A: Deploy the Connector using the Native tab
With native deployment, you sign in to Azure from CloudConnexa and configure the Azure resources from the Network Configuration Wizard.
After authentication, your Azure account is available for deployment.
Option B: Deploy the Connector using the Manual tab
With manual deployment, you download an ARM template from CloudConnexa and deploy it from the Azure portal.
The template creates and configures the resources required for the Connector, including:
An Ubuntu VM.
A network interface with IP forwarding enabled.
A static public IP address.
A Network Security Group.
The Connector software and configuration.
Network Address Translation (NAT) rules for routed traffic.
Verify the Connector
After deployment completes:
If deployment succeeds, the Connector status displays as Connected.
If deployment fails, CloudConnexa displays an error message so you can review and correct the deployment configuration.
Select Finish to complete the deployment.
What happens next
The Connector maintains an outbound connection from your Azure VNet to CloudConnexa.
You can now configure applications, IP services, and Access Groups to control which users and connected networks can access resources in the Azure VNet.