# Connector Installation - Azure
**Introduction**
This document will guide you to create an active-standby Cloudbrink Connector in Azure. Steps 7 through 10 must be completed twice in order to create two instances for the active-standby pair.
**Prerequisites**
● A hosting Linux VM with free space greater than 50 GB in Azure region where the Cloudbrink connector image needs to be downloaded is recommended to speed up transfer times, however it is not required
● A Storage Account service with container in the same region where the image needs to be created
**Connector VM Requirements**
● OS: Ubuntu 22.04
● Compute: 4 CPU and 8GB RAM and 50GB disk space
● Networking: ○ Inbound port 22 for SSH and active-standby keepalive ○ Outbound TCP port 443 and 9090, and UDP ports 9993 and 9994 to Cloudbrink SaaS and Edges
● Username: cbrink (required for hardening scripts)
***
## Create Connector VM from VHD file
1. Download the Cloudbrink Connector managed disk snapshot from the following URL (Azure Public Storage Account) using curl command.
Download Disk Image file from link below (15 days validity)
;
2. Upload the managed disk image VHD file to the container in the existing storage account using Azure UI console or CLI.
Command:
$ az storage blob upload --account-name \ --container-name \ --name \
Example:
$ az storage blob upload --account-name blobuploadtest --container-name testcontain- er --name connector-ubuntu-2204-amd64-v14.4.16.vhd --file connector-ubuntu-2204-amd64-v14.4.16.vhd
3. Create an image from the uploaded VHD file in the required region using Azure CLI.
Command:
$ az image create --resource-group \ --name \ --source \ --location \ --os-type Linux
Example:
$ az image create --resource-group ven-test-rg --name connector-ubuntu-2204-amd64-v14.4.16.vhd –source --location westus --os-type Linux
4. In Azure portal, navigate to All Services > Compute> Images.
5. On the Images page, select the newly created image and navigate to its overview page.
6. Click on the Create VM link located in the header to create a new connector VM.
7. Within the Instance Details section of the Basics tab, ensure the Availability Options has “No infrastructure redundancy required” selected.
8. Within the Administrator Account section of the Basics tab, ensure the Username is set to cbrink (this is required for our hardening script).
9. In the Networking section of VM creation, ensure that the Public IP type is set to “Basic” to ensure the Cloudbrink Connector retrieves its public IP details from Azure’s metadata.
10. In the Advanced tab, enable the “User-Data” and under the User-Data section with the below script, substituting in the provided OTP value.
\#cloud-config runcmd:
* \[bash, /opt/scripts/brink\_connector\_deploy\_cloud.sh, -o, "\", -a, "1", -v, "", -p, "", -f, ""]
NOTE: The OTP mentioned in the above step can be generated from the Cloudbrink management portal → Configure → Connectors → “Select the connector which is already configured for Azure env” → click “Generate OTP”
11. The last step is to click “Review and Create” the image and instantiate the Connector VM image
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cloudbrink.com/configuration/connector-deployment/connector-installation-azure.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.