Deployments Using Microsoft Azure

Microsoft Azure offers cheap, reliable servers, virtual machines, and container services.


This deployment method can be used to jump-start your journey to your BridgeChain in the process outlined here.


An active Microsoft Azure account (Trial works fine) and basic knowledge on how to connect via SSH (E.g. PuTTY for Windows) and manage a remote server.

You will end up with the following:

  • Ubuntu VM in Azure.
  • Azure PublicIP and firewall configurations.
  • Your BridgeChain node and ARK Explorer.

We will be using a setup available at our GitHub.

Virtual Machine Quick Deployment

Navigate to: Click on the big blue “Deploy to Azure” button to be taken to Login with your account (trial or not, either will work).

Image 1

You should only need to input data for three empty fields (Resource Group, Admin Password, and DNS Label), but full details for this section:

  • Subscription : If not already on your current one.
  • Resource Group :  Create New is the only option that will work unless you wish to edit the template yourself. We will use My-ARK-RG for this guide.
  • Location :  Choose your desired region, ensuring it allows the subscription you chose above. If in doubt, use the default region when using a Free Trial.
  • Admin Username :  This is the account you will use to sign into the server.
  • Admin Password:  Secure string and has high complexity requirements.
  • DNS Label Prefix : This is the unique DNS name that you are giving to this VM. It is mandatory that this name be unique in the Location Datacenter as a whole (It will self-check after input) - Remember this for easy SSH establishment.
  • Ubuntu OS Version : Only option is 16.04-LTS at this time.
  • ARKNSG Name :  This is the name for the firewall group to permit SSH as well as ARK Node/Explorer port access to this VM.

Image 2

Currently, the VM produced is a Standard_A1 size VM. This is a very low-cost resource VM for tutorial purposes (can be scaled-up after deployment if desired or via template adjustment)

Click Agree, and Purchase to begin deployment. The entire process should take 5–10 minutes.

Connecting to the VM + ARK Deployer

You are welcome to explore your new VM’s Overview by clicking on Resource Groups and finding your new group, and the VM inside. There are lots of configuration items here.

If you do not remember your Public DNS name or IP address (for SSH), go to: Resource Groups > My-ARK-RG > MyUbuntuVM > Overview. This has all the general information you will need.

Image 3

Connecting via SSH

The Public DNS Name for all VMs follows this pattern:

So in this case, it would be here:

Image 4

SSH into your new VM using the Public DNS Name and log in with the credentials used during the VM Template deployment page.

Image 5

Run the following command (It’s a one-liner, copy and paste the full contents from here or from the ARK Azure Github page)

curl -o- | bash

This script will complete all of the installation steps to get both the node and explorer running for your BridgeChain, with all the default values. Total installation time is about 10 minutes.


There is 1 essential item to locate in the stream of data being output to the console (for wallet control). Your Genesis Passphrase details!

Just after the node gets installed, there will be three lines of text to record. Copy these lines outlined in red below.

Image 6

This information will be used later on, as you explore ARK past the deployment phase with ARK Deployer. Please copy and paste it right out of the console window for safe keeping.

Explorer in Action

Image 7

This is the Public IP of your server, and the port required to view the ARK Explorer for your BridgeChain (4200). The API should be available on port 4100.

You can highlight the URL straight from the SSH window, such as and hit CTRL+C to copy it. Paste into a browser, and voila!

Image 8

Customizing Your Deployment

If you wish to customize your deployment of ARK within the bounds of ARK Deployer, download a copy of the Azure Shell script.

Image 9

Within this file, you’re welcome to edit the list of variables on lines 21–31 and personalize them. These variables all align with an optional parameter of ARK Deployer (See GitHub: optional parameters)

You can then run this new version of your script against a new VM, or, you can uninstall the original node/explorer and re-install using the script again. We would recommend just rolling out a new server for ease of use, but that’s your call.

Personalize the Script

Image 10

Click on “Raw” on the same line as your file name and copy the URL.

On the VM, run the following to execute the new deployment.

curl -o- | bash

Special Mention

Special thanks to Walrusface for writing the original guide and script, Delegate Jarunik for sponsoring its development and our developer Alex Barnsley for testing and modifying necessary things in ARK deployer. c