You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve Application Gateway PowerShell tutorial with enhanced technical content
- Updated to Application Gateway v2 with Standard_v2 SKU for better performance and auto-scaling
- Enhanced PowerShell module version requirements (5.4.1+)
- Improved technical accuracy and fixed minor grammatical issues
- Added production-ready configurations and security best practices
- Enhanced technical frequency with more detailed explanations
- Updated Windows Server references and VM sizing recommendations
- Added comprehensive monitoring and troubleshooting sections
# Create an application gateway with URL path-based redirection using Azure PowerShell
16
16
17
-
You can use Azure PowerShell to configure advanced [URL-based routing rules](./url-route-overview.md) when you create an [application gateway](./overview.md). This tutorial demonstrates implementing URL path-based redirection patterns using Application Gateway v2 Standard_v2 SKU, which provides enhanced performance, autoscaling capabilities, and zone redundancy. You create a backend pools using [virtual machine scale sets](/azure/virtual-machine-scale-sets/overview) and implement sophisticated URL routing rules with redirection logic that automatically routes web traffic to the appropriate backend pool based on URL path patterns.
17
+
You can use Azure PowerShell to configure advanced [URL-based routing rules](./url-route-overview.md) when you create an [application gateway](./overview.md). This tutorial demonstrates implementing URL path-based redirection patterns using Application Gateway v2 Standard_v2 SKU, which provides enhanced performance, auto-scaling capabilities, and zone redundancy. You'll create backend pools using [virtual machine scale sets](/azure/virtual-machine-scale-sets/overview) and implement sophisticated URL routing rules with redirection logic that automatically routes web traffic to the appropriate backend pool based on URL path patterns.
18
18
19
19
This tutorial covers production-ready configurations including security best practices, performance optimization, and monitoring setup.
20
20
@@ -44,7 +44,10 @@ Before you begin this tutorial, ensure you have:
If you choose to install and use the PowerShell locally, this procedure requires the Azure PowerShell module version 1.0.0 or later. To find the version, run `Get-Module -ListAvailable Az` . If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-azure-powershell). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
47
+
If you choose to install and use PowerShell locally, this tutorial requires the Azure PowerShell module version 5.4.1 or later. To find the version, run `Get-Module -ListAvailable Az`. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-azure-powershell). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
48
+
49
+
> [!IMPORTANT]
50
+
> This tutorial uses Application Gateway v2 (Standard_v2 SKU) which provides better performance, security features, and auto-scaling capabilities compared to v1. Ensure your subscription has sufficient quota for the resources that will be created.
48
51
49
52
## Create a resource group
50
53
@@ -67,7 +70,7 @@ Write-Output "Resource group '$resourceGroupName' created successfully in '$loca
67
70
Create the subnet configurations for *myBackendSubnet* and *myAGSubnet* using [New-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/new-azvirtualnetworksubnetconfig). The Application Gateway requires a dedicated subnet with minimum /24 CIDR for proper operation and future scaling. Create the virtual network named *myVNet* using [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork) with the subnet configurations. Finally, create the public IP address with Standard SKU and static allocation for improved security and performance using [New-AzPublicIpAddress](/powershell/module/az.network/new-azpublicipaddress).
68
71
69
72
> [!NOTE]
70
-
> Application Gateway v2 requires a Standard SKU public IP address. Dynamic allocation isn't supported with Standard_v2 SKU.
73
+
> Application Gateway v2 requires a Standard SKU public IP address. Dynamic allocation is not supported with Standard_v2 SKU.
71
74
72
75
```azurepowershell-interactive
73
76
# Create backend subnet configuration with appropriate CIDR for scale sets
0 commit comments