We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

How to Deploy an F-Series Firewall in Microsoft Azure using Azure Portal and ARM

  • Last updated on

If you are in a region, where the Azure Marketplace is not available, download VHD disk images from the Barracuda Download portal and deploy the firewall via user defined images.

For more information, see How to Upload Azure VHD Images for User Defined Images using ARM and How to Deploy an F-Series Firewall in Microsoft Azure using PowerShell and ARM.

The Barracuda NextGen Firewall F-Series for Microsoft Azure can be deployed as a virtual machine in the Microsoft Azure cloud. You can choose between the following images in the Azure Marketplace:

  • Barracuda NextGen Firewall F-Series (BYOL) – These images use licenses purchased directly from Barracuda Networks. Barracuda Networks offers a 30-day evaluation license.
  • Barracuda NextGen Firewall F-Series (PAYG) – These images do not need to be licensed separately. Licensing fees are included in the hourly price of the Instance. All charges are billed directly through your Microsoft Azure account.
  • Barracuda NextGen Control Center for Microsoft Azure (BYOL) – These images use licenses purchased directly from Barracuda Networks. Barracuda Networks offers a 30-day evaluation license.

Depending on your deployment, you may want to use more than one resource group to be able to maintain the deployed VMs more easily.

Video

Watch the following video of a NextGen Firewall PAYG deployment via the Azure portal. After the firewall is up and running the firewall is configured to act as the default gateway for the backend resources.

Before you begin

Step 1. Create a resource group

  1. Go to the Azure Portal: https://portal.azure.com
  2. In the upper left-hand corner, click NEW
  3. In the NEW column, click Management
  4. In the Management column, click Resource Group.
    azure_deploy_single_ui_01.png
  5. In the Resource Group column, enter:
    • Resource group name – Enter a unique name for your resource group.
    • Subscription – Select the Azure Subscription.
    • Resource group location – Select the Azure datacenter where you want to deploy your VM. All resources in the resource group must be in the same location. 
    azure_deploy_single_ui_02.png
  6. Click Create.

Step 2. Create a virtual network

  1. Go to the Azure Portal: https://portal.azure.com
  2. In the upper left-hand corner, click NEW
  3. In the NEW column, click Networking
  4. In the Networking column, click Virtual network
    azure_deploy_single_ui_03.png
  5.  In the Virtual network column, select Resource Manager from the deployment model drop-down list. 
    azure_deploy_single_ui_04.png
  6. Click Create
  7. In the Create virtual network column, enter:
    • Name – Enter a unique name for the virtual network.
    • Address space – Use a large network not overlapping with your on-premise networks.
    • Subnet name – Enter a name for the first subnet in the virtual network. E.g., Frontend
    • Subnet address range – Enter the network for the subnet. It must be a subnet of the network entered as the address space.
    • Subscription – Select the Azure subscription.
    • Resource Group – Click Select Existing and select the resource group created in step 1. 
    • Location – Select the location the resource group is in.
    azure_deploy_single_ui_05.png
  8. Click Create.

Step 3. Create a storage account

  1. Go to the Azure Portal: https://portal.azure.com
  2. In the upper left-hand corner, click NEW
  3. In the NEW column, click Data + Storage
  4. In the Data + Storage column, click Storage account
    azure_deploy_single_ui_06.png
  5.  In the Storage account column, select Resource Manager from the deployment model drop-down list.
    azure_deploy_single_ui_07.png
  6. Click Create.
  7. In the Create storage account column, enter:
    • Name – Enter a unique storage account name.
    • Type – Select the storage account type and how it is replicated.
    • Subscription – Select the Azure subscription.
    • Resource Group – Click Select Existing and select the resource group created in step 1.
    • Location – Select the location the resource group is in. 
    azure_deploy_single_ui_08.png
  8. Click Create.

Step 4. Deploy the Barracuda NextGen Firewall F-Series VM

  1. Go to the Azure Portal: https://portal.azure.com
  2. In the upper left-hand corner, click NEW
  3. In the NEW column, next to MARKETPLACE click See all link.
    azure_deploy_single_ui_10.png
     
  4. In the Everything column, search for Barracuda NextGen.
    azure_deploy_single_ui_11.png
  5. Select the image from the list:
    • Barracuda NextGen Firewall F-Series (BYOL)
    • Barracuda NextGen Firewall F-Series (Hourly)
    • Barracuda NextGen Control Center for Microsoft Azure (BYOL)
  6. In the Barracuda NextGen column for the selected image, select Resource Manager from the deployment model drop-down list.
    azure_deploy_single_ui_12.png
  7. Click Create.
  8. In the Basics column, configure:
    • Name – Enter the name of the Barracuda NextGen VM.
    • User name – Enter a placeholder username to satisfy the Azure input validation. This username is not used.
    • Authentication Type – Select Password.
    • Password – Enter the root password.
    • Subscription – Select the Azure subscription.
    • Resource Group – Click Select Existing and select the resource group created in step 1.
    • Location – Select the location the resource group is in.
    azure_deploy_single_ui_13.png
  9. Click OK.
  10. In the Choose a size column, select the instance size. Click View all to select from the full Instance list.
    azure_deploy_single_ui_14.png
  11. Click Select.
  12. In the Settings column, enter the storage, network, and monitoring settings:
    • Disk type – Select standard for magnetic disks or Premium (SSD) for faster SSD-based storage.
    • Storage account – Select the storage account created in step 3.
    • Virtual network – Select the virtual network created in step 2.
    • Subnet – Select the Subnet created in step 2. To use Azure user defined routing, verify that the firewall is not in the same subnet as the backend VMs.
    • Public IP address – Select a public IP address the VM is reachable through.
    • (optional) Network security group – Using a network security group is optional. Click and select none, or use the default included with the VM.
    • Monitoring – Click Disabled.
    azure_deploy_single_ui_15.png
  13. (HA Cluster only) In the Create virtual network column, add the VM to an Availability set:
    • Availability set –  Create a new availability set, or add to an existing availability set.
    azure_deploy_single_ui_05a.png
  14. Click OK.
    azure_deploy_single_ui_16.png
  15. In the Purchase column, click Purchase.

Wait for Microsoft Azure to finish the deployment of your Barracuda NextGen Firewall F-Series or Barracuda NextGen Control Center. Go to Virtual machines, click on the NextGen Firewall VM, and locate the Public IP address used to connect to your firewall.

azure_deploy_single_ui_17.png

Open the public IP address with your browser for further links on how to download NextGen Admin and how to receive an evaluation license.

cloud_landing_page.png

Next steps

Configure a user defined routing table for the backend VMs to send traffic through the firewall, and enable Azure Cloud Integration to allow the firewall VM to directly connect to the Azure service fabric.

For more information, see How to Configure Azure Route Tables (UDR) using Azure Portal and ARM and How to Configure Azure Cloud Integration using ARM.

Last updated on