Configure FortiGate initial parameters


This recipe is part of the process of deploying FortiGate HA load-balancing for Microsoft Azure using Azure load balancer. See below for the rest of the recipes in this process:

  1. Basic concepts
    • Traffic flow
    • Azure load balancer
      • Inbound NAT rules
      • Load balancing rules
  2. Locate FortiGate HA for Azure in the Azure portal or Azure marketplace
  3. Determine your licensing model
  4. Configure FortiGate initial parameters
  5. Create VNet and subnets in network settings
  6. Select Azure instance type
  7. Assign Azure IP address
  8. Validate deployment resources
  9. Create FortiGate instances
  10. Connect to the FortiGate
  11. [Use case] Set up a Windows Server in the protected network
  12. Configure FortiGate firewall policies and virtual IPs
  13. [Failover test] Create load balancing rules and access the Windows Server via remote desktop
  1. Set the initial parameters as follows:
    • FortiGate set name prefix: FortiGate name, set to distinguish from other resources.
    • FortiGate administrative username: specify FortiGate main administrator username. “admin” is not allowed as a username due to Azure restrictions.
    • FortiGate password: specify the administrator password.
    • Subscription: choose your subscription. This should differ from the screenshot below.
    • Resource group: specify the resource group name where FortiGate and associated resources will be accommodated.
    • Location: select the region where resources are hosted.

  2. Click OK.