create-multiple-sites-portal.md

title	description	services	author	ms.service	ms.topic	ms.date	ms.author
Tutorial - Create an application gateway that hosts multiple web sites using the Azure portal	In this tutorial, you learn how to create an application gateway that hosts multiple web sites using the Azure portal.	application-gateway	vhorne	application-gateway	tutorial	07/26/2019	victorh

Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal

You can use the Azure portal to configure the hosting of multiple web sites when you create an 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 assumes that you own multiple domains and uses examples of www.contoso.com and www.fabrikam.com.

In this tutorial, 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 backend listeners
• Create routing rules
• Create a CNAME record in your domain

If you don't have an Azure subscription, create a free account before you begin.

Sign in to Azure

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

Create an application gateway

1. Select Create a resource on the left menu of the Azure portal. The New window appears.

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:

   • Resource group: Select myResourceGroupAG for the resource group. If it doesn't exist, select Create new to create it.

   • Application gateway name: Enter myAppGateway for the name of the application gateway.

     

2. 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'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 Configure virtual network, select Create new to create a new virtual network . In the Create virtual network window that opens, enter the following values to create the virtual network and two subnets:

   • Name: Enter myVNet for the name of the virtual network.

   • Subnet name (Application Gateway subnet): The Subnets grid will show a subnet named Default. Change the name of this subnet to myAGSubnet.
     The application gateway subnet can contain only application gateways. No other resources are allowed.

   • Subnet name (backend server subnet): In the second row of the Subnets grid, enter myBackendSubnet in the Subnet name column.

   • Address range (backend server subnet): In the second row of the Subnets Grid, enter an address range that doesn't overlap with the address range of myAGSubnet. For example, if the address range of myAGSubnet is 10.0.0.0/24, enter 10.0.1.0/24 for the address range of myBackendSubnet.

   Select OK to close the Create virtual network window and save the virtual network settings.

   

3. On the Basics tab, accept the default values for the other settings and then select Next: Frontends.

Frontends tab

1. On the Frontends tab, verify Frontend IP address type is set to Public.
   You can configure the Frontend IP to be Public or Private as per your use case. In this example, you'll choose a Public Frontend IP.

   [!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. Choose Create 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 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'll create an empty backend pool with your application gateway and then add backend targets to the backend pool.

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 contosoPool for the name of the backend pool.
   • Add backend pool without targets: Select Yes to create a backend pool with no targets. You'll add backend targets after creating the application gateway.

3. In the Add a backend pool window, select Add to save the backend pool configuration and return to the Backends tab.

4. Now add another backend pool called fabrikamPool.

   

5. On the Backends tab, select Next: Configuration.

Configuration tab

On the Configuration tab, you'll connect the frontend and backend pools you created using a routing rule.

1. Select Add a rule in the Routing rules column.

2. In the Add a routing rule window that opens, enter contosoRule for the Rule name.

3. A routing rule requires a listener. On the Listener tab within the Add a routing rule window, enter the following values for the listener:

   • Listener name: Enter contosoListener for the name of the listener.
   • Frontend IP: Select Public to choose the public IP you created for the frontend.

   Under Additional settings:

   • Listener type: Multiple sites
   • Host name: www.contoso.com

   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 contosoPool for the Backend target.

5. For the HTTP setting, select Create new to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. In the Add an HTTP setting window that opens, enter contosoHTTPSetting for the HTTP setting name. Accept the default values for the other settings in the Add an HTTP setting window, then select Add to return to the Add a routing rule window.

6. On the Add a routing rule window, select Add to save the routing rule and return to the Configuration tab.

7. Select Add a rule and add a similar rule, listener, backend target, and HTTP setting for Fabrikam.

   

8. Select Next: Tags and then Next: Review + create.

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.

Add backend targets

In this example, you'll use virtual machines as the target backend. You can either use existing virtual machines or create new ones. You'll create two virtual machines that Azure uses as backend servers for the application gateway.

To add backend targets, you'll:

1. Create two new VMs, contosoVM and fabrikamVM, to be used as backend servers.
2. Install IIS on the virtual machines to verify that the application gateway was created successfully.
3. Add the backend servers to the backend pools.

Create a virtual machine

1. On the Azure portal, select Create a resource. The New window appears.

2. Select Compute and then select Windows Server 2016 Datacenter in the Popular list. The Create a virtual machine page appears.
   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.

3. Enter these values in the Basics tab for the following virtual machine settings:

   • Resource group: Select myResourceGroupAG for the resource group name.
   • Virtual machine name: Enter contosoVM for the name of the virtual machine.
   • Username: Enter azureuser for the administrator user name.
   • Password: Enter Azure123456! for the administrator password.

4. Accept the other defaults and then select Next: Disks.

5. Accept the Disks tab defaults and then select Next: Networking.

6. On the Networking tab, verify that myVNet is selected for the Virtual network and the Subnet is set to myBackendSubnet. Accept the other defaults and then select Next: Management.
   Application Gateway can communicate with instances outside of the virtual network that it is in, but you need to ensure there's IP connectivity.

7. On the Management tab, set Boot diagnostics to Off. Accept the other defaults and then select Review + create.

8. On the Review + create tab, review the settings, correct any validation errors, and then select Create.

9. Wait for the virtual machine creation to complete before continuing.

Install IIS for testing

In this example, you install IIS on the virtual machines only to verify Azure created the application gateway successfully.

1. Open Azure PowerShell. To do so, select Cloud Shell from the top navigation bar of the Azure portal and then select PowerShell from the drop-down list.

   

2. Run the following command to install IIS on the virtual machine:

   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
   

3. Create a second virtual machine and install IIS using the steps that you previously completed. Use fabrikamVM for the virtual machine name and for the VMName setting of the Set-AzVMExtension cmdlet.

Add backend servers to backend pools

1. Select All resources, and then select myAppGateway.

2. Select Backend pools from the left menu.

3. Select contosoPool.

4. Under Targets, select Virtual machine from the drop-down list.

5. Under VIRTUAL MACHINE and NETWORK INTERFACES, select the contosoVM virtual machine and it's associated network interface from the drop-down lists.

   

6. Select Save.

7. Repeat to add the fabrikamVM and interface to the fabrikamPool.

Wait for the deployment to complete before proceeding to the next step.

Create a www A record in your domains

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.

1. Click All resources, and then click myAGPublicIPAddress.

   

2. Copy the IP address and use it as the value for a new www A record in your domains.

Test the application gateway

1. Enter your domain name into the address bar of your browser. Such as, http://www.contoso.com.

   

2. Change the address to your other domain and you should see something like the following example:

   

Clean up resources

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.

To remove the resource group:

1. On the left menu of the Azure portal, select Resource groups.
2. On the Resource groups page, search for myResourceGroupAG in the list, then select it.
3. On the Resource group page, select Delete resource group.
4. Enter myResourceGroupAG for TYPE THE RESOURCE GROUP NAME and then select Delete

Next steps

[!div class="nextstepaction"] Learn more about what you can do with Azure Application Gateway