This lab requires an Azure subscription. Your subscription type may affect the availability of features in this lab. You may change the region, but the steps are written using East US.
Your organization recently finished testing managing network traffic for Azure virtual machines in a hub and spoke network topology. Now, you want to test traffic distribution across virtual machines by using layer 4 and layer 7 load balancers. For this purpose, you intend to use Azure Load Balancer (layer 4) and Azure Application Gateway (layer 7).
There are interactive lab simulations that you might find useful for this topic. The simulation lets you to click through a similar scenario at your own pace. There are differences between the interactive simulation and this lab, but many of the core concepts are the same. An Azure subscription is not required.
+ [Create and configure and Azure load balancer](https://mslabs.cloudguides.com/guides/AZ-700%20Lab%20Simulation%20-%20Create%20and%20configure%20an%20Azure%20load%20balancer). Create a virtual network, backend servers, load balancer, and then test the load balancer.
+ [Deploy Azure Application Gateway](https://mslabs.cloudguides.com/guides/AZ-700%20Lab%20Simulation%20-%20Deploy%20Azure%20Application%20Gateway). Create an application gateway, create virtual machines, create the backend pool, and test the gateway.
+ [Implement traffic management](https://mslabs.cloudguides.com/guides/AZ-104%20Exam%20Guide%20-%20Microsoft%20Azure%20Administrator%20Exercise%2010). Implement complete hub and spoke network including virtual machines, virtual networks, peering, load balancer, and application gateway.
In this task, you will use a template to deploy one virtual network, one network security group, and two virtual machines along with associated virtual network interface cards. The VMs will reside in a hub virtual network named **az104-vnet1**.
1. If necessary, download the **\\Allfiles\\Labs\\06\\az104-06-vms-loop-template.json** and **\\Allfiles\\Labs\\06\\az104-06-vms-loop-parameters.json** lab files to your computer.
>**Note**: If you receive an error that the VM size is unavailable, select a SKU that is available in your subscription and has at least 2 cores.
1. Select **Review + Create** and then select **Create**.
>**Note**: Wait for the deployment to finish before moving to the next task. The deployment should complete in approximately 5 minutes.
## Task 2: Implement Azure Load Balancer
In this task, you will implement an Azure Load Balancer in front of the two Azure virtual machines in the hub virtual network. Load Balancers in Azure provide layer 4 connectivity across resources, such as virtual machines. Load Balancer configuration includes a front-end IP address to accept connections, a backend pool, and rules that define how connections should traverse the load balancer.
1. On the **Frontend IP configuration** tab, click **Add a frontend IP configuration** and use the following settings:
| Setting | Value |
| --- | --- |
| Name | `az104-fe` |
| IP type | IP address |
| Public IP address | Select **Create new**|
| Gateway Load Balancer | None |
1. On the **Add a public IP address** popup, use the following settings before clicking **OK** and then **Add**. When completed click **Next: Backend pools**.
| Setting | Value |
| --- | --- |
| Name | `az104-pip` |
| SKU | Standard |
| Tier | Regional |
| Assignment | Static |
| Routing Preference | **Microsoft network** |
1. On the **Backend pools** tab, click **Add a backend pool** with the following settings (leave others with their default values). Click **+ Add** (twice) and then click **Next:Inbound rules**.
1. On the **Inbound rules** tab, click **Add a load balancing rule**. Add a load balancing rule with the following settings (leave others with their default values). When completed click **Add**.
1. As you have time, review the other tabs, then click **Review and create**. Ensure there are no validation errors, then click **Create**.
1. Wait for the load balancer to deploy then click **Go to resource**.
1. Select **Frontend IP configuration** from the Load Balancer resource page. Copy the public IP address.
1. Open another browser tab and navigate to the IP address. Verify that the browser window displays the message **Hello World from az104-06-vm0** or **Hello World from az104-06-vm1**.
1. Refresh the window to verify the message changes to the other virtual machine. This demonstrates the load balancer rotating through the virtual machines.
> **Note**: You may need to refresh more than once or open a new browser window in InPrivate mode.
## Task 3: Implement Azure Application Gateway
In this task, you will implement an Azure Application Gateway in front of the two Azure virtual machines in the spoke virtual networks. An Application Gateway provides layer 7 load balancing, Web Application Firewall (WAF), SSL termination, and end-to-end encryption to the resources defined in the backend pool.
1. In the Azure portal, search and select `Virtual networks`.
1. Add a subnet with the following settings (leave others with their default values):
| Setting | Value |
| --- | --- |
| Name | `subnet-appgw` |
| Subnet address range | `10.60.3.224/27` |
1. Click **Save**
> **Note**: This subnet will be used by the Azure Application Gateway instances, which you will deploy later in this task. The Application Gateway requires a dedicated subnet of /27 or larger size.
1. In the Azure portal, search and select `Application Gateways` and, on the **Application Gateways** blade, click **+ Create**.
1. On the **Basics** tab, specify the following settings (leave others with their default values):
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | `az104-rg1` |
| Application gateway name | `az104-appgw` |
| Region | The **same** Azure region that you used in Task 1 |
1. Click **Next: Frontends >** and specify the following settings (leave others with their default values). When complete, click **OK**.
| Setting | Value |
| --- | --- |
| Frontend IP address type | **Public** |
| Public IP address| **Add new** |
| Name | `az104-gwpip` |
| Availability zone | **None** |
1. Click **Next: Backends >** and then **Add a backend pool**. Specify the following settings (leave others with their default values). When completed click **Add**.
| Setting | Value |
| --- | --- |
| Name | `az104-appgwbe` |
| Add backend pool without targets | **No** |
| IP address or FQDN | **10.60.0.4** |
| IP address or FQDN | **10.60.1.4** |
> **Note**: The targets represent the private IP addresses of virtual machines **az104-vm0** and **az104-vm1**.
1. Click **Next: Configuration >** and then **+ Add a routing rule**. Specify the following settings:
1. Switch to the **Backend targets** tab and specify the following settings (leave others with their default values). When completed click **Add** (twice).
| Setting | Value |
| --- | --- |
| Target type | **Backend pool** |
| Backend target | **az104-appgwbe** |
| Backend settings | **Add new** |
| Backend settings name | `az104-http` |
| Backend protocol | **HTTP** |
| Backend port | `80` |
| Additional settings | **take the defaults** |
| Host name | **take the defaults** |
1. Click **Next: Tags >**, followed by **Next: Review + create >** and then click **Create**.
> **Note**: Wait for the Application Gateway instance to be created. This will take appoximately 10 minutes.
1. In the Azure portal, search and select **Application Gateways** and, on the **Application Gateways** blade, click **az104-appgw**.
1. On the **az104-appgw** Application Gateway blade, copy the value of the **Frontend public IP address**.
1. Start another browser window and navigate to the IP address you identified in the previous step.
1. Verify that the browser window displays the message **Hello World from az104-vm0** or **Hello World from az104-vm1**.
1. Refresh the window to verify the message changes to the other virtual machine.
> **Note**: You may need to refresh more than once or open a new browser window in InPrivate mode.
Congratulations on completing the lab. Here are the main takeaways for this lab.
+ Azure Load Balancer is an excellent choice for distributing network traffic across multiple virtual machines at the transport layer (OSI layer 4 - TCP and UDP).
+ Public Load Balancers are used to load balance internet traffic to your VMs. An internal (or private) load balancer is used where private IPs are needed at the frontend only.
+ The Basic load balancer is for small-scale applications that don't need high availability or redundancy. The Standard load balancer is for high performance and ultra-low latency.
+ Azure Application Gateway is a web traffic (OSI layer 7) load balancer that enables you to manage traffic to your web applications.
+ An Application Gateway can make routing decisions based on additional attributes of an HTTP request, for example URI path or host headers.
If you are working with your own subscription take a minute to delete the lab resources. This will ensure resources are freed up and cost is minimized. The easiest way to delete the lab resources is to delete the lab resource group.
+ In the Azure portal, select the resource group, select **Delete the resource group**, **Enter resource group name**, and then click **Delete**.
+ Using Azure PowerShell, `Remove-AzResourceGroup -Name resourceGroupName`.
