Deploy the VM-Series Firewall from the Azure Marketplace (Solution Template)

The following instructions describe how to deploy the solution template for the VM-Series firewall that is available in the Azure® Marketplace and the Azure Government Marketplace. To use the customizable Azure Resource Manager (ARM) templates available in the GitHub repository, see Use the ARM Template to Deploy the VM-Series Firewall.

All VM-Series firewall interfaces must be assigned an IPv4 address when deployed in a public cloud environment. IPv6 addresses are not supported.

1. Set up an Azure account.
   1. If you don’t have one already, create a Microsoft® account.
   2. Log in to the Azure portal (https://portal.azure.com or https://portal.azure.us) using your Microsoft account credentials.
      If you are using a trial subscription, you may need to open a support request (Help + SupportNew Support Request) to increase the quota of allocated VM cores.
2. Find the VM-Series solution template in the Azure Marketplace.
   1. Select MarketplaceVirtual Machines.
   2. Search for Palo Alto Networks® and a list of offerings for the VM-Series firewall will display. For the differences in the BYOL (bring your own license) and PAYG (pay as you go) models, see VM-Series Firewall Licenses for Public Clouds.

   3. Select an offering to Create a new VM-Series firewall.
3. Deploy the firewall.
   1. Configure basic settings for the firewall.
      1. Select your Azure Subscription.
      2. Create a new resource group or select an existing resource group that is empty. The resource group will hold all the resources associated with the VM-Series firewall for this deployment.
         Azure has removed the option to select an existing resource group for Marketplace solutions that enable multiple network interface controllers (NICs). To deploy the firewall into an existing resource group, use the ARM template in the GitHub Repository or use your own custom ARM template.
      3. Select the Azure Region in which you are deploying the firewall.
      4. Enter a Username for the firewall administrator.
      5. Select the Authentication type—Password or SSH Public Key.
         You must enable SSH key authentication if you plan to use the firewall in FIPS-CC operational mode. Although you can deploy the VM-Series firewall using a username and password, you will be unable to authenticate using the username and password after changing the operational mode to FIPS-CC. After resetting to FIPS-CC mode, you must use the SSH key to log in and can then configure a username and password that you can use for subsequently logging in to the firewall web interface. For details on creating the SSH key, refer to the Azure documentation.
      6. Enter a Password (up to 31 characters) or copy and paste an SSH public key for securing administrative access to the firewall.
   2. Configure networking.
      1. Select an existing Azure Virtual Network (VNet) or create a new one and enter the IP address space for the VNet. By default, the Classless Inter-Domain Routing (CIDR) IP address is 10.8.0.0/16.
      2. Configure the subnets for the network interfaces.
         If you use the default subnets, you must review the configuration. If you use an existing VNet, you must have set up three subnets: one each for the management,trust, and untrust interfaces. If you create a new VNet, verify or change the prefixes for each subnet. The default subnets are 10.8.0.0/24 for the management subnet, 10.8.1.0/24 for the untrust subnet, and 10.8.2.0/24 for the trust subnet.
      3. Enter the source IP address or IP range (include the CIDR block) that can access the VNet. Network Security Group: inbound source IP allows you to restrict inbound access to the Azure VNet.
         Restrict access to the firewall. Make sure to supply a CIDR block that corresponds to your dedicated management IP addresses or network. Do not make the allowed source network range larger than necessary and never configure the allowed source as 0.0.0.0/0. Verify your IP address before you configure it on the template to make sure that you do not lock yourself out.

   3. Define management access to the firewall.
      1. Use the default variable ((new) fwMgmtPublicIP)) to assign a Public IP address to the management interface (eth0) of the firewall.
         Azure accelerated networking is not supported on the management interface.
      2. Enter a prefix to access the firewall using a DNS name. You must combine the prefix you enter with the suffix displayed on screen to access the web interface of the firewall. For example: <yourname><your-region>.cloudapp.azure.com
      3. Select latest VM-Series Version.
      4. Enter a display name to identify the VM-Series firewall within the resource group.

   4. Add the information to configure the firewall at launch. See Bootstrap the VM-Series Firewall on Azure.
      1. Select yes to Enable Bootstrap.
      2. Enter the Storage Account Name that holds the Bootstrap Package.
      3. Enter the Storage Account Access Key. This firewall needs this access key to authenticate to the storage account and access the files stored within.
      4. Add the File share name to which you have uploaded the files required for bootstrapping the firewall. The storage account must be in the same region in which you are deploying the firewall and it must have the correct folder structure for bootstrapping.
      5. Select the Azure virtual machine tier and size to meet your needs. Use the Change size link to view supported instance types, and to review the Minimum System Requirements for the VM-Series on Azure.
   5. Review the summary, and OK. Then accept the terms of use and privacy policy, and Create to launch the firewall.

   6. Verify that you have successfully deployed the VM-Series firewall.
      1. Select DashboardResource Groups and select the resource group.
      2. Select your resource group and see the Overview for detailed status on which resources are deployed successfully.

4. Attach a public IP address for the untrust interface of the VM-Series firewall. When you create a new public IP address, you get one from the block of IP addresses that Microsoft owns, so you can’t choose a specific one. The maximum number of public IP addresses you can assign to an interface is based on your Azure subscription.
   1. On the Azure portal, select the network interface for which you want to add a public IP address (such as the eth1 interface).
   2. Select IP ConfigurationsAdd and, for Public IP address, select Enabled. Create a new public IP address or select one that you have available.
   3. Verify that you can view the secondary IP address associated with the interface.

   When you attach a secondary IP address to a network interface, the VM-Series firewall does not automatically acquire the private IP address assigned to the interface. You will need to manually configure the private IP address using the VM-Series firewall web interface. See Configure the dataplane network interfaces as Layer 3 interfaces on the firewall.
5. Log in to the web interface of the firewall.
   1. On the Azure portal, in All Resources, select the VM-Series firewall and view the full DNS name for the firewall.
   1. Using a secure (https) connection from your web browser, log in to the DNS name for the firewall.
   2. Enter the usernamepassword that you defined in the parameters file. You will see a certificate warning but that is OK—continue to the web page.
6. Activate the licenses on the VM-Series firewall.
   For the BYOL version
   1. Create a Support Account.
   2. Register the VM-Series Firewall (with auth code).
   3. On the firewall web interface, select DeviceLicenses and select Activate feature using authentication code.
   4. Enter the capacity authentication code (auth-code) that you registered on the support portal. The firewall will connect to the update server (updates.paloaltonetworks.com), and download the license and reboot automatically.
   5. Log back in to the web interface and confirm the following on the Dashboard:
      • A valid serial number displays in Serial#.
        If the term Unknown displays, it means the firewall is not licensed. To view traffic logs on the firewall, you must install a valid capacity license.
      • The VM Mode displays as Microsoft Azure.
   For the PAYG version
   1. Create a Support Account.
   2. Register the Usage-Based Model of the VM-Series Firewall for Public Clouds (no auth code).
7. Configure the dataplane network interfaces as Layer 3 interfaces on the firewall.
   If you are hosting multiple websites or services with different IP addresses and SSL certificates on a single server, you might need to configure more than one IP address on the VM-Series firewall interfaces.
   1. Select NetworkInterfacesEthernet.
   2. Click ethernet 1/1 and configure as follows:
      • Set Interface Type to Layer3 (default).
      • On the Config tab, assign the interface to the default router.
      • Also on the Config tab, expand the Security Zone drop-down and select New Zone. Define a new zone called UnTrust, and then click OK.
      • On the IPv4 tab, select DHCP Client if you plan to assign only one IP address on the interface—the firewall will automatically acquire the private IP address assigned in the ARM template. If you plan to assign more than one IP address, select Static and manually enter the primary and secondary IP addresses assigned to the interface on the Azure portal.
      • Disable (clear) the Automatically create default route to default gateway provided by server to ensure that traffic handled by this interface does not flow directly to the default gateway in the VNet.
   3. Click ethernet 1/2 and configure as follows:
      • Set Interface Type to Layer3 (default).
      • Set Security Zone to Trust.
      • Set IP address DHCP Client or Static.
      • Disable (clear) the Automatically create default route to default gateway provided by serverto ensure that traffic handled by this interface does not flow directly to the default gateway in the VNet.
   4. Commit your changes and verify that the link state for the interfaces is up.
   5. Add a static route on the virtual router of the VM-Series firewall for any networks that the firewall needs to route.
      For example, to add a default route to the destination subnets for the servers that the firewall secures:
      • Select NetworkVirtual Routerdefault
      • Select Static RoutesIPv4, and add the next hop IP address for the destination servers. You can set x.x.x.1 as the next hop IP address for all traffic (destined to 0.0.0.0/0 from interface ethernet1/1).
8. Configure the firewall for your specific deployment.
   • Gateway—Deploy a third-party load balancer in front of the UnTrust zone.
   • Hybrid and Inter-VNet—Deploy an Azure VPN Gateway or a NAT virtual machine in front the UnTrust zone.
   • Inter-Subnet—On the VM-Series firewall, add an intrazone Security policy rule to allow traffic based on the subnets attached to the Trust interface.
   • GlobalProtect™—Deploy a NAT virtual machine in front of the UnTrust zone.
9. Direct traffic to the VM-Series firewall.
   1. To ensure that the VM-Series firewall secures all traffic within the Azure resource group, configure static routes on the firewall.
   2. Configure user defined routes to direct all traffic through the interfaces on the VM-Series firewall. Refer to the Azure documentation on UDRs for details.
      The user defined routes on the internal subnets must send all traffic through the Trust interface. The user defined routes on the UnTrust side direct all traffic from the Internet through the UnTrust interface on the VM-Series firewall. The traffic from the Internet may be coming from an Azure Application Gateway or Azure Load Balancer, or through the Azure VPN Gateway in the case of a hybrid deployment that connects your on-premise network with the Azure cloud.
10. To publish PAN-OS® metrics to Azure Application Insights, see Enable Azure Application Insights on the VM-Series Firewall.