{"id":5291,"date":"2020-07-19T14:20:32","date_gmt":"2020-07-19T14:20:32","guid":{"rendered":"http:\/\/wiki-see.info\/wp\/?p=5291"},"modified":"2022-10-28T11:34:28","modified_gmt":"2022-10-28T11:34:28","slug":"azure-create-configure-application-gateway-to-host-multiple-web-sites-using-the-azure-portal","status":"publish","type":"post","link":"https:\/\/wiki-see.info\/wp\/2020\/07\/19\/azure-create-configure-application-gateway-to-host-multiple-web-sites-using-the-azure-portal\/","title":{"rendered":"Azure &#8211; Create, Configure Application Gateway to host multiple web sites using the Azure portal"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">You can use the Azure portal to&nbsp;<a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/multiple-site-overview\">configure the hosting of multiple web sites<\/a>&nbsp;when you create an&nbsp;<a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/overview\">application gateway<\/a>. In this tutorial, you define backend address pools using virtual machines. You then configure listeners and rules based on domains that you own to make sure web traffic arrives at the appropriate servers in the pools. This tutorial assumes that you own multiple domains and uses examples of&nbsp;<em><a href=\"http:\/\/www.contoso.com\/\">www.contoso.com<\/a><\/em>&nbsp;and&nbsp;<em><a href=\"http:\/\/www.fabrikam.com\/\">www.fabrikam.com<\/a><\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this tutorial, you learn how to:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Create an application gateway<\/li><li>Create virtual machines for backend servers<\/li><li>Create backend pools with the backend servers<\/li><li>Create backend listeners<\/li><li>Create routing rules<\/li><li>Create a CNAME record in your domain<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/scenario.png\" alt=\"Multi-site routing example\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If you don&#8217;t have an Azure subscription, create a&nbsp;<a href=\"https:\/\/azure.microsoft.com\/free\/?WT.mc_id=A261C142F\">free account<\/a>&nbsp;before you begin.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"sign-in-to-azure\">Sign in to Azure<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Sign in to the Azure portal at&nbsp;<a href=\"https:\/\/portal.azure.com\/\">https:\/\/portal.azure.com<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"create-an-application-gateway\">Create an application gateway<\/h2>\n\n\n\n<ol class=\"wp-block-list\"><li>Select&nbsp;<strong>Create a resource<\/strong>&nbsp;on the left menu of the Azure portal. The&nbsp;<strong>New<\/strong>&nbsp;window appears.<\/li><li>Select&nbsp;<strong>Networking<\/strong>&nbsp;and then select&nbsp;<strong>Application Gateway<\/strong>&nbsp;in the&nbsp;<strong>Featured<\/strong>&nbsp;list.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"basics-tab\">Basics tab<\/h3>\n\n\n\n<ol class=\"wp-block-list\"><li>On the&nbsp;<strong>Basics<\/strong>&nbsp;tab, enter these values for the following application gateway settings:<ul><li><strong>Resource group<\/strong>: Select&nbsp;<strong>myResourceGroupAG<\/strong>&nbsp;for the resource group. If it doesn&#8217;t exist, select&nbsp;<strong>Create new<\/strong>&nbsp;to create it.<\/li><li><strong>Application gateway name<\/strong>: Enter&nbsp;<em>myAppGateway<\/em>&nbsp;for the name of the application gateway.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/application-gateway-create-gateway-portal\/application-gateway-create-basics.png\" alt=\"Create new application gateway: Basics\"><\/li><\/ul><\/li><li>For Azure to communicate between the resources that you create, it needs a virtual network. You can either create a new virtual network or use an existing one. In this example, you&#8217;ll create a new virtual network at the same time that you create the application gateway. Application Gateway instances are created in separate subnets. You create two subnets in this example: one for the application gateway, and another for the backend servers.Under&nbsp;<strong>Configure virtual network<\/strong>, select&nbsp;<strong>Create new<\/strong>&nbsp;to create a new virtual network . In the&nbsp;<strong>Create virtual network<\/strong>&nbsp;window that opens, enter the following values to create the virtual network and two subnets:<ul><li><strong>Name<\/strong>: Enter&nbsp;<em>myVNet<\/em>&nbsp;for the name of the virtual network.<\/li><li><strong>Subnet name<\/strong>&nbsp;(Application Gateway subnet): The&nbsp;<strong>Subnets<\/strong>&nbsp;grid will show a subnet named&nbsp;<em>Default<\/em>. Change the name of this subnet to&nbsp;<em>myAGSubnet<\/em>.<br>The application gateway subnet can contain only application gateways. No other resources are allowed.<\/li><li><strong>Subnet name<\/strong>&nbsp;(backend server subnet): In the second row of the&nbsp;<strong>Subnets<\/strong>&nbsp;grid, enter&nbsp;<em>myBackendSubnet<\/em>&nbsp;in the&nbsp;<strong>Subnet name<\/strong>&nbsp;column.<\/li><li><strong>Address range<\/strong>&nbsp;(backend server subnet): In the second row of the&nbsp;<strong>Subnets<\/strong>&nbsp;Grid, enter an address range that doesn&#8217;t overlap with the address range of&nbsp;<em>myAGSubnet<\/em>. For example, if the address range of&nbsp;<em>myAGSubnet<\/em>&nbsp;is 10.0.0.0\/24, enter&nbsp;<em>10.0.1.0\/24<\/em>&nbsp;for the address range of&nbsp;<em>myBackendSubnet<\/em>.<\/li><\/ul>Select&nbsp;<strong>OK<\/strong>&nbsp;to close the&nbsp;<strong>Create virtual network<\/strong>&nbsp;window and save the virtual network settings.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/application-gateway-create-gateway-portal\/application-gateway-create-vnet.png\" alt=\"Create new application gateway: virtual network\"><\/li><li>On the&nbsp;<strong>Basics<\/strong>&nbsp;tab, accept the default values for the other settings and then select&nbsp;<strong>Next: Frontends<\/strong>.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"frontends-tab\">Frontends tab<\/h3>\n\n\n\n<ol class=\"wp-block-list\"><li>On the&nbsp;<strong>Frontends<\/strong>&nbsp;tab, verify&nbsp;<strong>Frontend IP address type<\/strong>&nbsp;is set to&nbsp;<strong>Public<\/strong>.<br>You can configure the Frontend IP to be Public or Private as per your use case. In this example, you&#8217;ll choose a Public Frontend IP.&nbsp;NoteFor the Application Gateway v2 SKU, you can only choose&nbsp;<strong>Public<\/strong>&nbsp;frontend IP configuration. Private frontend IP configuration is currently not enabled for this v2 SKU.<\/li><li>Choose&nbsp;<strong>Create new<\/strong>&nbsp;for the&nbsp;<strong>Public IP address<\/strong>&nbsp;and enter&nbsp;<em>myAGPublicIPAddress<\/em>&nbsp;for the public IP address name, and then select&nbsp;<strong>OK<\/strong>.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/application-gateway-create-gateway-portal\/application-gateway-create-frontends.png\" alt=\"Create new application gateway: frontends\"><\/li><li>Select&nbsp;<strong>Next: Backends<\/strong>.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"backends-tab\">Backends tab<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The backend pool is used to route requests to the backend servers that serve the request. Backend pools can be NICs, virtual machine scale sets, public IPs, internal IPs, fully qualified domain names (FQDN), and multi-tenant back-ends like Azure App Service. In this example, you&#8217;ll create an empty backend pool with your application gateway and then add backend targets to the backend pool.<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>On the&nbsp;<strong>Backends<\/strong>&nbsp;tab, select&nbsp;<strong>+Add a backend pool<\/strong>.<\/li><li>In the&nbsp;<strong>Add a backend pool<\/strong>&nbsp;window that opens, enter the following values to create an empty backend pool:<ul><li><strong>Name<\/strong>: Enter&nbsp;<em>contosoPool<\/em>&nbsp;for the name of the backend pool.<\/li><li><strong>Add backend pool without targets<\/strong>: Select&nbsp;<strong>Yes<\/strong>&nbsp;to create a backend pool with no targets. You&#8217;ll add backend targets after creating the application gateway.<\/li><\/ul><\/li><li>In the&nbsp;<strong>Add a backend pool<\/strong>&nbsp;window, select&nbsp;<strong>Add<\/strong>&nbsp;to save the backend pool configuration and return to the&nbsp;<strong>Backends<\/strong>&nbsp;tab.<\/li><li>Now add another backend pool called&nbsp;<em>fabrikamPool<\/em>.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/backend-pools.png\" alt=\"Create new application gateway: backends\"><\/li><li>On the&nbsp;<strong>Backends<\/strong>&nbsp;tab, select&nbsp;<strong>Next: Configuration<\/strong>.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"configuration-tab\">Configuration tab<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On the&nbsp;<strong>Configuration<\/strong>&nbsp;tab, you&#8217;ll connect the frontend and backend pools you created using a routing rule.<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Select&nbsp;<strong>Add a rule<\/strong>&nbsp;in the&nbsp;<strong>Routing rules<\/strong>&nbsp;column.<\/li><li>In the&nbsp;<strong>Add a routing rule<\/strong>&nbsp;window that opens, enter&nbsp;<em>contosoRule<\/em>&nbsp;for the&nbsp;<strong>Rule name<\/strong>.<\/li><li>A routing rule requires a listener. On the&nbsp;<strong>Listener<\/strong>&nbsp;tab within the&nbsp;<strong>Add a routing rule<\/strong>&nbsp;window, enter the following values for the listener:<ul><li><strong>Listener name<\/strong>: Enter&nbsp;<em>contosoListener<\/em>&nbsp;for the name of the listener.<\/li><li><strong>Frontend IP<\/strong>: Select&nbsp;<strong>Public<\/strong>&nbsp;to choose the public IP you created for the frontend.<\/li><\/ul>Under&nbsp;<strong>Additional settings<\/strong>:<ul><li><strong>Listener type<\/strong>: Multiple sites<\/li><li><strong>Host name<\/strong>:&nbsp;<strong><a href=\"http:\/\/www.contoso.com\/\">www.contoso.com<\/a><\/strong><\/li><\/ul>Accept the default values for the other settings on the&nbsp;<strong>Listener<\/strong>&nbsp;tab, then select the&nbsp;<strong>Backend targets<\/strong>&nbsp;tab to configure the rest of the routing rule.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/routing-rule.png\" alt=\"Create new application gateway: listener\"><\/li><li>On the&nbsp;<strong>Backend targets<\/strong>&nbsp;tab, select&nbsp;<strong>contosoPool<\/strong>&nbsp;for the&nbsp;<strong>Backend target<\/strong>.<\/li><li>For the&nbsp;<strong>HTTP setting<\/strong>, select&nbsp;<strong>Create new<\/strong>&nbsp;to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. In the&nbsp;<strong>Add an HTTP setting<\/strong>&nbsp;window that opens, enter&nbsp;<em>contosoHTTPSetting<\/em>&nbsp;for the&nbsp;<strong>HTTP setting name<\/strong>. Accept the default values for the other settings in the&nbsp;<strong>Add an HTTP setting<\/strong>&nbsp;window, then select&nbsp;<strong>Add<\/strong>&nbsp;to return to the&nbsp;<strong>Add a routing rule<\/strong>&nbsp;window.<\/li><li>On the&nbsp;<strong>Add a routing rule<\/strong>&nbsp;window, select&nbsp;<strong>Add<\/strong>&nbsp;to save the routing rule and return to the&nbsp;<strong>Configuration<\/strong>&nbsp;tab.<\/li><li>Select&nbsp;<strong>Add a rule<\/strong>&nbsp;and add a similar rule, listener, backend target, and HTTP setting for Fabrikam.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/fabrikamrule.png\" alt=\"Create new application gateway: routing rule\"><\/li><li>Select&nbsp;<strong>Next: Tags<\/strong>&nbsp;and then&nbsp;<strong>Next: Review + create<\/strong>.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"review--create-tab\">Review + create tab<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review the settings on the&nbsp;<strong>Review + create<\/strong>&nbsp;tab, and then select&nbsp;<strong>Create<\/strong>&nbsp;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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wait until the deployment finishes successfully before moving on to the next section.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"add-backend-targets\">Add backend targets<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In this example, you&#8217;ll use virtual machines as the target backend. You can either use existing virtual machines or create new ones. You&#8217;ll create two virtual machines that Azure uses as backend servers for the application gateway.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To add backend targets, you&#8217;ll:<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Create two new VMs,&nbsp;<em>contosoVM<\/em>&nbsp;and&nbsp;<em>fabrikamVM<\/em>, to be used as backend servers.<\/li><li>Install IIS on the virtual machines to verify that the application gateway was created successfully.<\/li><li>Add the backend servers to the backend pools.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"create-a-virtual-machine\">Create a virtual machine<\/h3>\n\n\n\n<ol class=\"wp-block-list\"><li>On the Azure portal, select&nbsp;<strong>Create a resource<\/strong>. The&nbsp;<strong>New<\/strong>&nbsp;window appears.<\/li><li>Select&nbsp;<strong>Compute<\/strong>&nbsp;and then select&nbsp;<strong>Windows Server 2016 Datacenter<\/strong>&nbsp;in the&nbsp;<strong>Popular<\/strong>&nbsp;list. The&nbsp;<strong>Create a virtual machine<\/strong>&nbsp;page appears.<br>Application Gateway can route traffic to any type of virtual machine used in its backend pool. In this example, you use a Windows Server 2016 Datacenter.<\/li><li>Enter these values in the&nbsp;<strong>Basics<\/strong>&nbsp;tab for the following virtual machine settings:<ul><li><strong>Resource group<\/strong>: Select&nbsp;<strong>myResourceGroupAG<\/strong>&nbsp;for the resource group name.<\/li><li><strong>Virtual machine name<\/strong>: Enter&nbsp;<em>contosoVM<\/em>&nbsp;for the name of the virtual machine.<\/li><li><strong>Username<\/strong>: Enter&nbsp;<em>azureuser<\/em>&nbsp;for the administrator user name.<\/li><li><strong>Password<\/strong>: Enter&nbsp;<em>Azure123456!<\/em>&nbsp;for the administrator password.<\/li><\/ul><\/li><li>Accept the other defaults and then select&nbsp;<strong>Next: Disks<\/strong>.<\/li><li>Accept the&nbsp;<strong>Disks<\/strong>&nbsp;tab defaults and then select&nbsp;<strong>Next: Networking<\/strong>.<\/li><li>On the&nbsp;<strong>Networking<\/strong>&nbsp;tab, verify that&nbsp;<strong>myVNet<\/strong>&nbsp;is selected for the&nbsp;<strong>Virtual network<\/strong>&nbsp;and the&nbsp;<strong>Subnet<\/strong>&nbsp;is set to&nbsp;<strong>myBackendSubnet<\/strong>. Accept the other defaults and then select&nbsp;<strong>Next: Management<\/strong>.<br>Application Gateway can communicate with instances outside of the virtual network that it is in, but you need to ensure there&#8217;s IP connectivity.<\/li><li>On the&nbsp;<strong>Management<\/strong>&nbsp;tab, set&nbsp;<strong>Boot diagnostics<\/strong>&nbsp;to&nbsp;<strong>Off<\/strong>. Accept the other defaults and then select&nbsp;<strong>Review + create<\/strong>.<\/li><li>On the&nbsp;<strong>Review + create<\/strong>&nbsp;tab, review the settings, correct any validation errors, and then select&nbsp;<strong>Create<\/strong>.<\/li><li>Wait for the virtual machine creation to complete before continuing.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"install-iis-for-testing\">Install IIS for testing<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In this example, you install IIS on the virtual machines only to verify Azure created the application gateway successfully.<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Open&nbsp;<a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/cloud-shell\/quickstart-powershell\">Azure PowerShell<\/a>. To do so, select&nbsp;<strong>Cloud Shell<\/strong>&nbsp;from the top navigation bar of the Azure portal and then select&nbsp;<strong>PowerShell<\/strong>&nbsp;from the drop-down list.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/application-gateway-create-gateway-portal\/application-gateway-extension.png\" alt=\"Install custom extension\"><\/li><li>Run the following command to install IIS on the virtual machine:Azure PowerShellCopyTry It<code>Set-AzVMExtension ` -ResourceGroupName myResourceGroupAG ` -ExtensionName IIS ` -VMName contosoVM ` -Publisher Microsoft.Compute ` -ExtensionType CustomScriptExtension ` -TypeHandlerVersion 1.4 ` -SettingString '{\"commandToExecute\":\"powershell Add-WindowsFeature Web-Server; powershell Add-Content -Path \\\"C:\\\\inetpub\\\\wwwroot\\\\Default.htm\\\" -Value $($env:computername)\"}' ` -Location EastUS<\/code><\/li><li>Create a second virtual machine and install IIS using the steps that you previously completed. Use&nbsp;<em>fabrikamVM<\/em>&nbsp;for the virtual machine name and for the&nbsp;<strong>VMName<\/strong>&nbsp;setting of the&nbsp;<strong>Set-AzVMExtension<\/strong>&nbsp;cmdlet.<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"add-backend-servers-to-backend-pools\">Add backend servers to backend pools<\/h3>\n\n\n\n<ol class=\"wp-block-list\"><li>Select&nbsp;<strong>All resources<\/strong>, and then select&nbsp;<strong>myAppGateway<\/strong>.<\/li><li>Select&nbsp;<strong>Backend pools<\/strong>&nbsp;from the left menu.<\/li><li>Select&nbsp;<strong>contosoPool<\/strong>.<\/li><li>Under&nbsp;<strong>Targets<\/strong>, select&nbsp;<strong>Virtual machine<\/strong>&nbsp;from the drop-down list.<\/li><li>Under&nbsp;<strong>VIRTUAL MACHINE<\/strong>&nbsp;and&nbsp;<strong>NETWORK INTERFACES<\/strong>, select the&nbsp;<strong>contosoVM<\/strong>&nbsp;virtual machine and it&#8217;s associated network interface from the drop-down lists.<\/li><li><img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/edit-backend-pool.png\" alt=\"Add backend servers\"><\/li><li>Select&nbsp;<strong>Save<\/strong>.<\/li><li>Repeat to add the&nbsp;<em>fabrikamVM<\/em>&nbsp;and interface to the&nbsp;<em>fabrikamPool<\/em>.<\/li><\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Wait for the deployment to complete before proceeding to the next step.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"create-a-www-a-record-in-your-domains\">Create a www A record in your domains<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After the application gateway is created with its public IP address, you can get the IP address and use it to create an A record in your domains.<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Click&nbsp;<strong>All resources<\/strong>, and then click&nbsp;<strong>myAGPublicIPAddress<\/strong>.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/public-ip.png\" alt=\"Record application gateway DNS address\"><\/li><li>Copy the IP address and use it as the value for a new&nbsp;<em>www<\/em>&nbsp;A record in your domains.<\/li><\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"test-the-application-gateway\">Test the application gateway<\/h2>\n\n\n\n<ol class=\"wp-block-list\"><li>Enter your domain name into the address bar of your browser. Such as,&nbsp;<code>http:\/\/www.contoso.com<\/code>.<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/application-gateway-iistest.png\" alt=\"Test contoso site in application gateway\"><\/li><li>Change the address to your other domain and you should see something like the following example:<img decoding=\"async\" src=\"https:\/\/docs.microsoft.com\/en-us\/azure\/application-gateway\/media\/create-multiple-sites-portal\/application-gateway-iistest2.png\" alt=\"Test fabrikam site in application gateway\"><\/li><\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"clean-up-resources\">Clean up resources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When you no longer need the resources that you created with the application gateway, remove the resource group. When you remove the resource group, you also remove the application gateway and all its related resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To remove the resource group:<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>On the left menu of the Azure portal, select&nbsp;<strong>Resource groups<\/strong>.<\/li><li>On the&nbsp;<strong>Resource groups<\/strong>&nbsp;page, search for&nbsp;<strong>myResourceGroupAG<\/strong>&nbsp;in the list, then select it.<\/li><li>On the&nbsp;<strong>Resource group page<\/strong>, select&nbsp;<strong>Delete resource group<\/strong>.<\/li><li>Enter&nbsp;<em>myResourceGroupAG<\/em>&nbsp;for&nbsp;<strong>TYPE THE RESOURCE GROUP NAME<\/strong>&nbsp;and then select&nbsp;<strong>Delete<\/strong>. <\/li><\/ol>\n","protected":false},"excerpt":{"rendered":"<p>You can use the Azure portal to&nbsp;configure the hosting of multiple web sites&nbsp;when you create an&nbsp;application gateway. In this tutorial, you define backend address pools using virtual machines. You then configure listeners and rules based on domains that you own to make sure web traffic arrives at the appropriate servers in the pools. This tutorial [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[811],"tags":[],"class_list":["post-5291","post","type-post","status-publish","format-standard","hentry","category-azure"],"_links":{"self":[{"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/posts\/5291","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/comments?post=5291"}],"version-history":[{"count":2,"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/posts\/5291\/revisions"}],"predecessor-version":[{"id":5328,"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/posts\/5291\/revisions\/5328"}],"wp:attachment":[{"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/media?parent=5291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/categories?post=5291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki-see.info\/wp\/wp-json\/wp\/v2\/tags?post=5291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}