Tutorial: Connect Your Azure VNet to CloudConnexa by Deploying a Connector
Deploy an OpenVPN Network Connector on an Azure VM to connect your Azure VNet to CloudConnexa. Provide secure network access to your Azure VNet resources.
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.
Important
The downloaded ARM template contains deployment information specific to the Connector, including credentials used to retrieve its connector profile. Store the template securely, do not share it, and delete it when you no longer need it.
Step 1: Create a Network
To create a Network, follow the steps below:
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.
To authorize CloudConnexa:
On the Native tab, select Sign in to Azure.
In the Microsoft authentication dialog, sign in using your Azure account.
Review and grant the requested permissions.
After authentication, CloudConnexa displays the Azure deployment settings.
To configure the Connector VM:
Select the Azure Subscription.
Select the Resource Group where CloudConnexa will deploy the Connector VM.
Enter a VM Name.
Select the Region.
Select an SSH public key.
Enter a DNS Label Prefix.
Select the Virtual Network Name.
Select the Subnet.
Select Deploy.
CloudConnexa deploys the VM, installs the Connector software, and retrieves the connector profile.
Important
Select the VNet subnet that corresponds to the subnet configured for the Network in CloudConnexa. Using a different subnet may prevent traffic from routing correctly.
Note
The Connector VM uses the assigned Network Security Group (NSG) to control network traffic. Ensure the NSG allows the required outbound connectivity so the Connector can establish and maintain its outbound tunnel to CloudConnexa.
Continue to Verify the Connector.
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.
To download the template:
On the Deploy Network Connector page, select the Manual tab.
Select the option to download the ARM template.
Save the JSON template to your local computer.
Important
Download a new template for each Connector deployment. The template contains information specific to that Connector and shouldn't be reused for another Network or Connector.
To load the downloaded template:
Sign in to the Azure portal.
Select Create a resource.
Search for Template deployment (deploy using custom templates).
Select Create.
Select Build your own template in the editor.
Select Load file.
Select the JSON ARM template you downloaded from CloudConnexa.
Select Save.
Azure displays the deployment settings defined by the template.
Complete the template deployment settings:
Select the Azure Subscription.
Select an existing Resource Group, or create one.
The Connector resources are deployed to the Region associated with the resource group.
Complete the following Instance details:
Parameter
Description
Region
The region value propagates from the resource group.
VM Name
Enter a name for the Connector VM.
Disk Type
Select the storage type for the VM operating system disk.
Admin Username
Enter the administrator username for the VM. The default is
ubuntu.Authentication Type
Select SSH public key or password authentication. SSH public key authentication is strongly recommended.
Admin Password Or Key
Enter the SSH public key or password for the VM, based on the selected authentication type.
Dns Label Prefix
Enter a unique DNS label prefix for the VM's public IP address.
Vm Size
Select the Azure VM size. The template provides a default size.
Virtual Network Name
Enter the exact name of the existing Azure VNet. You can find the VNet name on the Virtual Networks page.
Subnet Name
Enter the exact name of the existing subnet where you want to deploy the Connector. You can find the subnet name on the Subnets page of the VNet.
Important
The Subnet Name must identify the VNet subnet that corresponds to the subnet configured for the Network in CloudConnexa. Using a different subnet may prevent traffic from routing correctly.
Network Security Group Name
Enter a name for the Network Security Group, or use the generated default.
To deploy the Connector:
Select Review + create.
Review the deployment settings.
Wait for Azure to validate the template.
After validation succeeds, select Create.
Azure creates the Connector VM and its supporting networking resources. During initialization, the VM installs the Connector software, enables IP forwarding, configures NAT, and retrieves its connector profile from CloudConnexa.
Note
The generated Network Security Group permits inbound SSH access to the VM. Review the rule and restrict its source range to align with your organization's security requirements.
Continue to Verify the Connector.
Verify the Connector
Note
Deployment typically takes several minutes.
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.