It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

How to Deploy a Firewall Control Center from the Microsoft Azure Marketplace

  • Last updated on

You can install the Firewall Control Center as a virtual machine in the Microsoft Azure public cloud. The Firewall Control Center is licensed using the Bring-Your-Own-License (BYOL) model. For more information, see Firewall Control Center.

Before You Begin

Step 1. Basics

  1. Go to the Azure portal:
  2. In the upper-left corner, click + Create a resource
  3. Search the Marketplace for Barracuda Firewall Control Center for Azure and click Barracuda Firewall Control Center for Azure.

  4. In the next window, click Create.
  5. In the Basics blade, configure the following settings:
    • Subscription – Select your subscription.
    • Resource Group – Select an existing resource group to deploy to, or click Create new for a new resource group.
    • Region – Select the desired location the Control Center will be deployed to. 
    • Control Center Name – Enter the hostname for the Firewall Control Center.
    • Firmware version – Select one of the available firmware versions. Barracuda Networks recommends deploying the highest available version.
  6. Click Next : Networking >.

Step 2. Networking

  1. In the Size and Networking blade, configure the following settings:
    • Virtual network Select an existing Virtual network, or create a new one. 
    • Control Center Subnet – Select an existing subnet, or create a new one. This subnet will host your Control Center.
    • Public IP address name – Select an existing Public IP address, or create a new one. 

      Note that regardless of the option selected, the Barracuda CloudGen Firewall is always deployed with a standard SKU public IP address for enhanced performance. For example, if you select a basic SKU IP address, the CloudGen Firewall will still be deployed with a standard SKU IP address.

    • Domain name label – Enter a domain name for your Control Center.
  2. Click Next : Management >.

Step 3. Management

  1. In the Management blade, configure the following settings:
    • Management ACL – Introduces a Network Security Group that restricts access to management ports of the Control Center. Enter to allow access from any network and to skip creating a Network Security Group.

    • Root password – Enter the password for the root user of the Control Center.

    • Confirm password – Retype the password for the root user of the Control Center.
  1. Click Next : Advanced >.  

Step 4. Advanced

  1. In the Advanced blade, configure the following settings:
    • Private IP addressEnter a static private IP address from the subnet the Control Center is deployed to. The first four and the last IP addresses in the subnet are reserved by Azure.
    • VM size – If not already configured, change the virtual machine size.
    • Accelerated networking – Enable or disable Azure Accelerated Networking if the size of your virtual machine meets the requirements of Microsoft.

      Azure Accelerated Networking creates, for each existing interface, a second interface for Accelerated Networking (one for the hv_netvsc driver, and one for Mellanox). Use only every second interface in boxnet (e.g., eth0, eth2, eth4). On devices with DHCP enabled, eth0 is replaced with the DHCP interface. On DHCP-enabled devices, as well, use only every second interface (e.g., eth0, eth2, eth4).


  2. Click Next : Review + create >.

Step 5. Summary

  1. The basic configuration of the Control Center is validated, and if no errors are found, the virtual machine is ready for provisioning. For automated deployments, you can download the configuration template.
  2. Click Create
  3. Wait for Microsoft Azure to finish the deployment of your Control Center. 
  4. Go to Virtual machines, click on the Control Center VM, and locate the Public IP address  used to connect to your Control Center. Use this IP address to connect to your Control Center via Barracuda Firewall Admin. The username is root and the password is the password you configured in Step 3.