Deploy the Azure Solution Template for Single VM-Series Firewall

Set up an Azure account.
If you don’t have one already, create a Microsoft® account.
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 + Support
New Support Request
) to increase the quota of allocated VM cores.
Find the VM-Series solution template in the Azure Marketplace, click
Create a resource
and Select
VM-Series Next Generation Firewall from Palo Alto
.
Select
Marketplace
Virtual Machines
.
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.
Select the VM-Series Next-Gen Single Firewall to
Create
a new VM-Series firewall.
Deploy the firewall.
Configure basic settings for the firewall.

Select your Azure
Subscription
.
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.
Select the Azure
Region
in which you are deploying the firewall.
Enter a
Username
for the firewall administrator.
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.
Enter a
Password
(up to 31 characters) or copy and paste an
SSH public key
for securing administrative access to the firewall.
Confirm the password.
Select the
License Type
.
Enter the Deployment
Tag
that you specified while creating the resource group.
Click
Next
.

Configure networking.

Select an existing Azure Virtual Network (VNet) or create a new one and enter the IP address space for the VNet.
Configure the subnets for the network interfaces--You may choose either a single arm configuration with management and trust subnets, or two arm configuration with management, trust and untrust subnets.
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.
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.
Click
Next
.

Define management access to the firewall.

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.
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
Select latest
VM-Series Version
.
Enter a display name to identify the VM-Series firewall within the resource group.

Add the information to configure the firewall at launch. Select the

VM-Series Version

,

Virtual machine size

, and

Availability Option

.

Select
yes
if you wish to
Enable Bootstrap
. See Bootstrap the VM-Series Firewall on Azure. Select one of the following two options under
Use Bootstrap File:
Provide Bootstrap File
Provide Bootstrap Parameters - Add additional information related to primary Panorama, secondary Panorama, DG, template stack, and so on.
Enter the
Storage Account Name
that holds the Bootstrap Package.
Enter the
Storage Account Access Key
. This firewall needs this access key to authenticate to the storage account and access the files stored within.
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.
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.

Review the summary, and

OK

. Then accept the terms of use and privacy policy, and

Create

to launch the firewall.

Verify that you have successfully deployed the VM-Series firewall.

Select

Dashboard

Resource Groups

and select the resource group.

Select your resource group and see the

Overview

for detailed status on which resources are deployed successfully.
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.
On the Azure portal, select the network interface for which you want to add a public IP address (such as the
eth1
interface).
Select
IP Configurations
Add
and, for Public IP address, select
Enabled
. Create a new public IP address or select one that you have available.
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.
Log in to the web interface of the firewall.
On the Azure portal, in
All Resources
, select the VM-Series firewall and view the full DNS name for the firewall.
Using a secure (https) connection from your web browser, log in to the DNS name for the firewall.
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.
Activate the licenses on the VM-Series firewall.
For the BYOL version
Create a Support Account.
Register the VM-Series Firewall (with auth code).
On the firewall web interface, select
Device
Licenses
and select
Activate feature using authentication code
.
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.
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
Create a Support Account.
Register the Usage-Based Model of the VM-Series Firewall for Public Clouds (no auth code).
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.
Select
Network
Interfaces
Ethernet
.
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.
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 server
to ensure that traffic handled by this interface does not flow directly to the default gateway in the VNet.
Commit
your changes and verify that the link state for the interfaces is up.
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
Network
Virtual Router
default
Select
Static Routes
IPv4
, 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).
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.
Direct traffic to the VM-Series firewall.
To ensure that the VM-Series firewall secures all traffic within the Azure resource group, configure static routes on the firewall.
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.
To publish PAN-OS® metrics to Azure Application Insights, see Enable Azure Application Insights on the VM-Series Firewall.