Install Panorama on Azure

1. Log into to the Microsoft Azure portal.
2. Set up the virtual network for your network needs.

   Whether you launch the Panorama virtual appliance in an existing virtual network or you create a new virtual network, the Panorama virtual appliance must be able to receive traffic from other instances in the virtual network and perform inbound and outbound communication between the virtual network and the internet as needed.

   Refer to the Microsoft Azure Virtual Network documentation for more information.

   1. Create a Virtual Network or use an existing virtual network.
   2. Verify that the network and security components are appropriately defined.

      • Create a NAT gateway if you want to enable only outbound internet access for the subnet to which the Panorama virtual appliance belongs.
      • Create subnets. Subnets are segments of the IP address range assigned to the VNet in which you can launch Microsoft Azure instances. It is recommended that the Panorama virtual appliance belong to the management subnet so that you can configure it to access the internet if needed.
      • Add routes to the route table for a private subnet to ensure traffic can be routed across subnets in the VNet and from the internet if applicable.
        Ensure you create routes between subnets to allow communication between:
        • Panorama, managed firewalls, and Log Collectors.
        • (Optional) Panorama and the internet.
      • Ensure that the following ingress security rules are allowed for the VNet to manage VNet traffic. The ingress traffic source for each rule is unique to your deployment topology.
        See Ports Used for Panorama for more information.
        • Allow SSH (port 22) traffic to enable access to the Panorama CLI.
        • Allow HTTPS (port 443) traffic to enable access to the Panorama web interface.
        • Allow traffic on port 3978 to enable communication between Panorama, manage firewalls, and managed Log Collectors. This port is also used by Log Collectors to forward logs to Panorama.
        • Allow traffic on port 28443 to enable managed firewalls to get software and content updates from Panorama.
3. Deploy the Panorama virtual appliance.

   1. In the Azure Dashboard, select Virtual machines and Add a new virtual machine.
   2. Search for Palo Alto Networks and select the latest Panorama virtual appliance image.
   3. Create the Panorama virtual appliance.
4. Configure the Panorama virtual appliance.

   1. Select your Azure Subscription.
   2. Select the Azure Resource Group to contain all your Azure instance resources.
   3. Enter a Virtual machine name for the Panorama virtual appliance.
   4. Select the Region for the Panorama virtual appliance to be deployed in.
   5. (Optional) Select the Availability options. See How to use availability sets for more information.
   6. Select the Image used to deploy the Panorama management server. Browse all public and private images to deploy the Panorama management server from the Panorama image on the Azure marketplace.
   7. Configure the Panorama virtual appliance size. Review the Setup Prerequisites for the Panorama Virtual Appliance for sizing requirements.

      If you plan to use the Panorama virtual appliance as a Dedicated Log Collector, ensure that you configure the appliance with the required resources during initial deployment. The Panorama virtual appliance does not remain in Log Collector mode if you resize the virtual machine after you deploy it, and this results in a loss of log data.
   8. Configure the unique Panorama virtual appliance administrator credentials.

      You must configure a unique administrative password before you can access the web interface and CLI of the Panorama virtual appliance.

      1. Enter a Username for the Panorama virtual appliance administrator. To ensure that your username is secure, admin is not a valid entry.
      2. Enter a Password or copy and paste an SSH public key for securing administrative access to the Panorama virtual appliance.

      You must enable SSH key authentication if you plan to use this instance of the Panorama virtual appliance in FIPS-CC operational mode. Although you can deploy the Panorama virtual appliance 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 Panorama web interface. For details on creating the SSH key, refer to the Azure documentation.
   9. Configure the Panorama virtual appliance instance Networking

      1. Select an existing Virtual network or create a new virtual network.
      2. Configure the Subnet. The subnet is dependent on the virtual network you selected or created in the previous step. If you selected an existing virtual network, you can choose one of the subnets for the selected virtual network.
      3. Select an existing Public IP address or create a new one. This creates the management interface used to access your Panorama virtual appliance.
      4. Select an existing NIC network security group or create a new security group. Network security groups control traffic to the virtual machine. Make sure that HTTPS and SSH are allowed for the Inbound rules.
   10. Configure the instance Management settings.

       1. Select whether to enable Auto-shutdown. Auto-shutdown allows you to configure a daily time to automatically shut down the virtual machine that you disable auto-shutdown to avoid the possibility that a new public IP address gets assigned to the virtual machine, that logs are dropped, that logs are not or that you are unable to manage your firewalls while the Panorama virtual appliance is shut down.
       2. Select whether to enable boot Monitoring. Select the Diagnostic storage account if enabled. Monitoring automatically sends boot-up diagnostic logs to your Diagnostics storage account. For more information, see Overview of Monitoring in Microsoft Azure.
       3. Configure any other settings as needed.
   11. Review the summary, accept the terms of use and privacy policy, and Create the Panorama virtual appliance.
5. Verify that you the Panorama virtual appliance has been successfully deployed.

   1. Select DashboardResource Groups and select the resource group containing the Panorama virtual appliance.
   2. Under Settings, select Deployments for the virtual machine deployment status.

      It takes about 30 minutes to deploy the Panorama virtual appliance. Launching the Panorama virtual appliance may take longer depending on the resources configured for the virtual machine. Microsoft Azure does not permit the ICMP protocol to test whether it deployed successfully.

      If you plan to use the Panorama virtual appliance as a Dedicated Log Collector, ensure that you correctly configured the appliance the required resources. The Panorama virtual appliance does not remain in Log Collector mode if you resize the virtual machine after you deploy it and this results in a loss of log data.
6. Configure a static Public IP address.

   1. On the Azure portal, select Virtual machines and select the Panorama virtual machine.
   2. Select Overview and click the Public IP address.
   3. Under Assignment, select Static and Save the new IP address configuration.
7. Log in to the web interface of the Panorama virtual appliance.

   1. On the Azure portal, in All Resources, select the Panorama virtual appliance and view the public IP address located in the Overview section.
   2. Use a secure (https) connection from your web browser to log in to the Panorama virtual appliance using the public IP address.
   3. Enter the username and password of the Panorama virtual appliance. You are prompted with a certificate warning. Accept the certificate warning and continue to the web page.
8. Register the Panorama virtual appliance and activate the device management license and support licenses.

   1. (VM Flex Licensing Only) Provisioning the Panorama Virtual Appliance Serial Number.

      When leveraging VM Flex licensing, this step is required to generate the Panorama virtual appliance serial number needed to register the Panorama virtual appliance with the Palo Alto Networks Customer Support Portal (CSP).
   2. Register Panorama.

      You must register the Panorama virtual appliance using the serial number provided by Palo Alto Networks in the order fulfillment email.

      This step is not required when leveraging VM Flex licensing as the serial number is automatically registered with the CSP when generated.
   3. Activate the firewall management license.

      • Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected.
      • Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected.
   4. Activate a Panorama Support License.
9. Complete configuring the Panorama virtual appliance for your deployment needs.

   • For Panorama in Log Collector Mode.
     1. Add a Virtual Disk to Panorama on Azure as needed.
        Adding at least one virtual logging disk is required before you can change the Panorama virtual appliance to Log Collector mode.
     2. Begin at Step 6 to switch to Log Collector mode.
        Enter the Public IP address of the Dedicated Log Collector when you add the Log Collector as a managed collector to the Panorama management server. You cannot specify the IP Address, Netmask, or Gateway.
   • For Panorama in Panorama mode.
     1. Add a Virtual Disk to Panorama on Azure.
        Adding at least one virtual logging disk is required before you can change the Panorama virtual appliance to Panorama mode.
     2. Set up a Panorama Virtual Appliance in Panorama Mode.
     3. Configure a Managed Collector.
   • For Panorama in Management Only mode.
     1. Set up a Panorama Virtual Appliance in Management Only Mode.
     2. Configure a Managed Collector to add a Dedicated Log Collector to the Panorama virtual appliance.
        Management Only mode does not support local log collection, and requires a Dedicated Log Collector to store managed device logs.