Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: 'Tutorial: Create an application gateway with URL path-based routing rules using Azure portal' description: In this tutorial, you learn how to create URL path-based routing rules for an application gateway and virtual machine scale set using the Azure portal. services: application-gateway author: mbender-ms ms.service: azure-application-gateway ms.topic: tutorial ms.date: 10/06/2025 ms.author: mbender ms.custom: sfi-image-nochange #Customer intent: As an IT administrator, I want to use the Azure portal to set up an application gateway so I can route my app traffic based on path-based routing rules. # Customer intent: As an IT administrator, I want to create an application gateway with URL path-based routing rules using the Azure portal, so that I can efficiently manage and direct web traffic to the appropriate backend servers based on specific URL patterns. --- # Tutorial: Create an application gateway with path-based routing rules using the Azure portal You can use the Azure portal to configure [URL path-based routing rules](./url-route-overview.md) when you create an [application gateway](./overview.md). In this tutorial, you create backend pools using virtual machines. You then create routing rules that make sure web traffic arrives at the appropriate servers in the pools. In this article, you learn how to: > [!div class="checklist"] > * Create an application gateway > * Create virtual machines for backend servers > * Create backend pools with the backend servers > * Create a backend listener > * Create a path-based routing rule :::image type="content" source="./media/application-gateway-create-url-route-portal/scenario.png" alt-text="Diagram of application gateway URL routing example." lightbox="./media/application-gateway-create-url-route-portal/scenario.png"::: If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) before you begin. ## Prerequisites - An Azure subscription ## Create virtual machines In this example, you create three virtual machines to be used as backend servers for the application gateway. You also install IIS on the virtual machines to verify that the application gateway works as expected. 1. Sign in to the [Azure portal](https://portal.azure.com). 1. On the Azure portal, select **Create a resource**. 2. Select **Windows Server 2016 Datacenter** in the Popular list. 3. Enter these values for the virtual machine: - **Subscription** - Select your subscription. - **Resource group**, select **Create new**, and then type *myResourceGroupAG*. - **Virtual machine name**: *myVM1* - **Region**: *(US) East US* - **Username**: Type a user name - **Password**: Type a password 4. Select **Next:Disks**. 5. Select **Next:Networking** 6. For **Virtual network**, select **Create new** and then type these values for the virtual network: - *myVNet* - for the name of the virtual network. - *10.0.0.0/16* - for the virtual network address space. - *myBackendSubnet* for the first subnet name - *10.0.1.0/24* - for the subnet address space. - *myAGSubnet* - for the second subnet name. - *10.0.0.0/24* - for the subnet address space. 7. Select **OK**. 8. Ensure that under **Subnet**, **myBackendSubnet** is selected for the subnet, and then select **Next: Management**. 9. Select **Disable** to disable boot diagnostics. 10. Select **Review + Create**, review the settings on the summary page, and then select **Create**. 11. Create two more virtual machines, *myVM2* and *myVM3* and place them in the *MyVNet* virtual network and the *myBackendSubnet* subnet. ### Install IIS 1. Open the interactive shell and make sure that it's set to **PowerShell**. 2. Run the following command to install IIS on the virtual machine: ```azurepowershell $publicSettings = @{ "fileUris" = (,"https://raw.githubusercontent.com/Azure/azure-docs-powershell-samples/master/application-gateway/iis/appgatewayurl.ps1"); "commandToExecute" = "powershell -ExecutionPolicy Unrestricted -File appgatewayurl.ps1" } Set-AzVMExtension ` -ResourceGroupName myResourceGroupAG ` -Location eastus ` -ExtensionName IIS ` -VMName myVM1 ` -Publisher Microsoft.Compute ` -ExtensionType CustomScriptExtension ` -TypeHandlerVersion 1.4 ` -Settings $publicSettings ``` 3. Install IIS on the other virtual machines using the steps that you just finished. Use *myVM2* and *myVM3* for VMName values in Set-AzVMExtension. ## Create an application gateway 1. Select **Create a resource** on the left menu of the Azure portal. 2. Select **Networking** and then select **Application Gateway** in the **Featured** list. ### Basics tab 1. On the **Basics** tab, enter these values for the following application gateway settings: - **Subscription**: Select your subscription. - **Resource group**: Select **myResourceGroupAG** for the resource group. - **Application gateway name**: Type *myAppGateway* for the name of the application gateway. - **Region** - Select **East US**. 2. Under **Configure virtual network**, select **myVNet** for the name of the virtual network. 3. Select **myAGSubnet** for the subnet. 3. Accept the default values for the other settings and then select **Next: Frontends**. :::image type="content" source="./media/create-url-route-portal/application-gateway-create-basics.png" alt-text="Screenshot of Basics tab of Create application gateway page."::: ### Frontends tab 1. On the **Frontends** tab, verify **Frontend IP address type** is set to **Public**. > [!NOTE] > For the Application Gateway v2 SKU, you can only choose **Public** frontend IP configuration. Private frontend IP configuration is currently not enabled for this v2 SKU. 2. Select **Add new** for the **Public IP address** and enter *myAGPublicIPAddress* for the public IP address name, and then select **OK**. 3. Select **Next: Backends**. ### Backends tab The backend pool is used to route requests to the backend servers that serve the request. Backend pools can be composed of NICs, virtual machine scale sets, public IPs, internal IPs, fully qualified domain names (FQDN), and multitenant backends like Azure App Service. 1. On the **Backends** tab, select **Add a backend pool**. 2. In the **Add a backend pool** window that opens, enter the following values to create an empty backend pool: - **Name**: Enter *myBackendPool* for the name of the backend pool. 3. Under **Target type**, select **Virtual machine** from the drop-down list. 5. Under **Target** select the network interface for **myVM1**. 6. Select **Add**. 7. Repeat to add an *Images* backend pool with *myVM2* as the target, and a *Video* backend pool with *myVM3* as the target. 8. Select **Add** to save the backend pool configuration and return to the **Backends** tab. 4. On the **Backends** tab, select **Next: Configuration**. ### Configuration tab On the **Configuration** tab, you'll connect the frontend and backend pool you created using a routing rule. 1. Select **Add a routing rule** in the **Routing rules** column. 2. In the **Add a routing rule** window that opens, enter *myRoutingRule* for the **Rule name**. 3. A routing rule requires a listener. On the **Listener** tab within the **Add a routing rule** window, type the following values for the listener: - **Listener name**: Enter *myListener* for the name of the listener. - **Frontend IP**: Select **Public** to choose the public IP you created for the frontend. - **Port**: Type *8080* Accept the default values for the other settings on the **Listener** tab, then select the **Backend targets** tab to configure the rest of the routing rule. 4. On the **Backend targets** tab, select **myBackendPool** for the **Backend target**. 5. For the **Backend settings**, select **Add new** to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. 6. In the **Add Backend setting** window that opens, enter *myHTTPSetting* for the **Backend settings name**. Accept the default values for the other settings in the **Add Backend setting** window, then select **Add** to return to the **Add a routing rule** window. 7. Under **Path-based routing**, select **Add multiple targets to create a path-based rule**. 1. Under **Path based rules**, select **Add multiple targets to create a path-based rule**. 1. For **Path**, type */images/*\*. 1. For **Target name**, type *Images*. 1. For **Backend settings**, select **myHTTPSetting** 1. For **Backend target**, select **myBackendPool**. 1. Select **Add** to save the path rule and return to the **Add a routing rule** tab. 1. Repeat to add another rule for Video. 1. Select **Add** to add the routing rule and return to the **Configuration** tab. 1. Select **Next: Tags** and then **Next: Review + create**. > [!NOTE] > You don't need to add a custom */** path rule to handle default cases. This is automatically handled by the default backend pool. > [!NOTE] > Wildcard delimiter **\*** is only honored at the end of the rule. For more information and supported path based rules examples, see [URL Path Based Routing overview](url-route-overview.md#pathpattern). ### Review + create tab Review the settings on the **Review + create** tab, and then select **Create** to create the virtual network, the public IP address, and the application gateway. It may take several minutes for Azure to create the application gateway. Wait until the deployment finishes successfully before moving on to the next section. ## Test the application gateway 1. Select **All resources**, and then select **myAppGateway**. :::image type="content" source="./media/application-gateway-create-url-route-portal/application-gateway-record-ag-address.png" alt-text="Screenshot of record application gateway public IP address."::: 2. Copy the public IP address, and then paste it into the address bar of your browser. Such as, http:\//203.0.113.10:8080.  The listener on port 8080 routes this request to the default backend pool. 3. Change the URL to *http://<ip-address>:8080/images/test.htm*, replacing <ip-address> with the public IP address of **myAppGateway**, and you should see something like the following example:  The listener on port 8080 routes this request to the *Images* backend pool. 4. Change the URL to *http://<ip-address>:8080/video/test.htm*, replacing <ip-address> with the public IP address of **myAppGateway**, and you should see something like the following example:  The listener on port 8080 routes this request to the *Video* backend pool. ## Clean up resources When no longer needed, delete the resource group and all related resources. To do so, select the resource group and select **Delete resource group**. ## Next steps In this tutorial, you created an application gateway with a path-based routing rule. To learn more about path-based routing in Application Gateways, see [URL path-based routing overview](url-route-overview.md) To learn how to create and configure an Application Gateway to redirect web traffic using the Azure CLI, advance to the next tutorial. > [!div class="nextstepaction"] > [Redirect web traffic](tutorial-url-redirect-cli.md)