How do I configure the Azure Web Application Gateway in the Azure Portal or Powershell?

You can configure Azure Web Application Gateway either through the Azure Portal or using Azure PowerShell. Here are the steps to configure it through both methods:

  1. Azure Portal:

Step 1: Sign in to the Azure Portal at https://portal.azure.com/.

Step 2: Click on “Create a resource” in the left-hand menu, then search for “Web Application Gateway” in the search box and select it from the results.

Step 3: Fill in the required information, such as the resource group, region, and deployment type.

Step 4: Configure the Gateway’s settings, such as the frontend IP address, listener, and backend pool.

Step 5: Configure the routing rules to determine how traffic should be forwarded to the backend pool.

Step 6: Save and deploy the configuration.

  1. Azure PowerShell:

Step 1: Open Azure PowerShell on your local machine.

Step 2: Connect to your Azure account using the following command:

powershell
Connect-AzAccount

Step 3: Select the subscription you want to work with using the following command:

powershell
Set-AzContext -SubscriptionId <SubscriptionID>

Step 4: Create a new resource group using the following command:

powershell
New-AzResourceGroup -Name <ResourceGroupName> -Location <Location>

Step 5: Create a new Web Application Gateway using the following command:

powershell
New-AzApplicationGateway -Name <GatewayName> -ResourceGroupName <ResourceGroupName> -Location <Location> -Sku Standard_v2 -GatewayIPConfigurations <IPConfigurations> -FrontendIPConfigurations <FrontendIPConfigurations> -FrontendPorts <FrontendPorts> -BackendAddressPools <BackendPools> -BackendHttpSettingsCollection <BackendHttpSettings> -HttpListeners <HttpListeners> -RequestRoutingRules <RoutingRules>

Step 6: Configure the Gateway’s settings, such as the frontend IP address, listener, and backend pool using the appropriate PowerShell cmdlets.

Step 7: Configure the routing rules to determine how traffic should be forwarded to the backend pool using the appropriate PowerShell cmdlets.

Step 8: Save and deploy the configuration.

Here are some examples of the PowerShell cmdlets you can use:

To create a new resource group:

powershell
New-AzResourceGroup -Name "MyResourceGroup" -Location "East US"

To create a new Web Application Gateway:

powershell
$ipConfigurations = @{"Name" = "GatewayIP"; "Subnet" = @{ "Id" = "/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Network/virtualNetworks/<VNetName>/subnets/<SubnetName>" }};
$frontendIPConfigurations = @{"Name" = "FrontendIP"; "PublicIPAddress" = @{ "Id" = "/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Network/publicIPAddresses/<PublicIPName>" }};
$frontendPorts = @{"Name" = "Port80"; "Port" = 80};
$backendAddressPools = @{"Name" = "BackendPool"; "BackendAddresses" = @{"IpAddress" = "10.0.0.4"}};
$backendHttpSettings = @{"Name" = "BackendSettings"; "Port" = 80; "Protocol" = "Http"; "CookieBasedAffinity" = "Enabled"};
$httpListeners = @{"Name" = "HttpListener"; "FrontendIPConfiguration" = $frontendIPConfigurations; "FrontendPort" = $frontendPorts; "Protocol" = "Http"; "
Author: tonyhughes