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 Web Application Firewall
Barracuda Web Application Firewall

Microsoft Azure

  • Last updated on

If you need to add additional storage, you must create a new attached drive; this applies to Barracuda virtual machines purchased through the Microsoft Azure Marketplace February 2015 or later. You cannot attach new storage in earlier deployments

The Barracuda Web Application Firewall provides proven application security and data loss prevention for your applications on Microsoft Azure, including:

  • Detecting and blocking attacks including SQL injections, Cross-Site Scripting, malware uploads, and volumetric or application DDoS.
  • Authentication and access control allowing organizations to exercise strong user control.
  • Scanning of outbound traffic for sensitive data, with admin control of masking or blocking information to prevent data leakage.
  • Built-in load balancing and session management, allowing organizations to manage multiple applications behind a single instance of the Barracuda Web Application Firewall.

Cloud hosted deployment of the Barracuda Web Application Firewall on Microsoft Azure currently supports One-Arm Proxy Mode. For more information, see Configuring One-Arm Proxy Mode.


To meet a variety of performance requirements, the A1, A2, A3 and A4 instance types are supported. Depending on the instance type, you can have:

  • Up to 8 vCPU.
  • Up to 14 GB of memory.

Licensing Options

 The Barracuda Web Application Firewall is available on Microsoft Azure with the Bring Your Own License (BYOL) and Hourly / Metered option.

Bring Your Own License (BYOL)

With the Bring Your Own License (BYOL) option, you are required to get the Barracuda Web Application Firewall license token, either by:

BYOL Models and Instance Types

For BYOL, Barracuda offers four models. The table below lists each model, the corresponding Instance Type to be used in Microsoft Azure, the default CPU and Memory for the instance.

If you want to increase the performance of a license that you have already purchased, you can buy additional cores from Barracuda and reconfigure for a larger instance type. 

Barracuda Web Application Firewall Model Supported Instance Type in Microsoft Azure Default vCPU Default Memory
Level 1 D1 1 3.5 GB
Level 5 D2 2 7 GB
Level 10 D3 4 14 GB
Level 15 D4 8 28 GB

You can add multiple Barracuda Web Application Firewall instances under one cloud service and load balance the traffic between the deployed instances to increase the throughput. For more information on load balancing, see the Load Balancing For Clustered Barracuda Web Application Firewall Instances in the Old Microsoft Azure Management Portal article.

Hourly / Metered

With the Hourly/Metered licensing option, you complete the purchase or evaluation of the Barracuda Web Application Firewall entirely within the Microsoft Azure gallery. After the instance is launched, it is provisioned automatically. You are charged hourly for both the Barracuda Web Application Firewall Software and Microsoft Azure usage on Microsoft. 

Hourly / Metered Model and Instance Types

For more information on supported instance types, Default vCPU, Default Memory and Hourly pricing, refer to Barracuda Web Application Firewall Pricing Details[3]

If you want to increase the performance of an existing VM, configure it with a larger instance type on Microsoft Azure and you will be charged accordingly by Microsoft. The VM will automatically be reconfigured by Microsoft with the resources and capabilities of the larger instance type.

Before You Begin

Create an Azure Virtual Network

  1. Log into your Microsoft Azure Management Portal[4].
  2. In the left pane, click NETWORKS, and then click NEW at the bottom of the screen.




  4. On the Virtual Network Details page:
    1. Enter a unique name in the Name field. For example, AzureVirtualNet
    2. Select a location from the LOCATION drop-down list. The virtual network can only be used for Azure instances in this geographic region. E.g., South Central US
    3. Click Next arrow.png.


  5. (Optional) On the DNS Servers and VPN Connectivity page, select or enter your DNS SERVERS.
  6. Click Next arrow.png.
  7. On the Virtual Network Address Spaces page, configure the ADDRESS SPACE:
    1. STARTING IP: Enter the first IP address of the address space you want to use.
    2. CIDR: Select the subnet mask for the virtual network. The maximum number of instances for a virtual network are listed in parentheses.
  8. Add a SUBNET:
    1. STARTING IP: Enter the first IP address of the subnet. 
    2. CIDR: Select the subnet mask for the subnet.


  9. Click Finish check_mark.png.

The created virtual network gets displayed in the VIRTUAL NETWORKS lists.

Next Step

Continue with Deploying and Provisioning the Barracuda Web Application Firewall in the Old Microsoft Azure Management Portal for instructions on installation and configuration.

Last updated on