Skip to content

Commit c8c74ab

Browse files
mbender-msmbender-ms
committed
updates to doc
1 parent c11f38a commit c8c74ab

File tree

1 file changed

+103
-111
lines changed

1 file changed

+103
-111
lines changed

‎articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md

Lines changed: 103 additions & 111 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,9 @@ Get started with Azure Load Balancer by using the Azure portal to create an inte
1818

1919
:::image type="content" source="media/quickstart-load-balancer-standard-internal-portal/internal-load-balancer-resources.png" alt-text="Diagram of resources deployed for internal load balancer.":::
2020

21+
> [!NOTE]
22+
> In this example you'll create a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed and isn't needed with the NAT gateway. For more information on Azure NAT gateway, see [What is Azure Virtual Network NAT?](../virtual-network/nat-gateway/nat-overview.md)
23+
> For more information about outbound connections in Azure, see [Source Network Address Translation (SNAT) for outbound connections](../load-balancer/load-balancer-outbound-connections.md)
2124
## Prerequisites
2225

2326
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -26,6 +29,41 @@ Get started with Azure Load Balancer by using the Azure portal to create an inte
2629

2730
Sign in to the [Azure portal](https://portal.azure.com).
2831

32+
## Create NAT gateway
33+
34+
All outbound internet traffic traverses the NAT gateway to the internet. Use the following example to create a NAT gateway for the hub and spoke network.
35+
36+
1. Sign in to the [Azure portal](https://portal.azure.com).
37+
38+
1. In the search box at the top of the portal, enter **NAT gateway**. Select **NAT gateways** in the search results.
39+
40+
1. Select **+ Create**.
41+
42+
1. In the **Basics** tab of **Create network address translation (NAT) gateway** enter or select the following information:
43+
44+
| Setting | Value |
45+
| ------- | ----- |
46+
| **Project details** | |
47+
| Subscription | Select your subscription. |
48+
| Resource group | Select **Create new**. </br> Enter **CreateIntLBQS-rg** in Name. </br> Select **OK**. |
49+
| **Instance details** | |
50+
| NAT gateway name | Enter **myNATgateway**. |
51+
| Region | Select **East US**. |
52+
| Availability zone | Select **None**. |
53+
| Idle timeout (minutes) | Enter **15**. |
54+
55+
1. Select the **Outbound IP** tab or select the **Next: Outbound IP** button at the bottom of the page.
56+
57+
1. Select **Create a new public IP address** under **Public IP addresses**.
58+
59+
1. Enter **myNATgatewayIP** in **Name** in **Add a public IP address**.
60+
61+
1. Select **OK**.
62+
63+
1. Select the blue **Review + create** button at the bottom of the page, or select the **Review + create** tab.
64+
65+
1. Select **Create**.
66+
2967
## Create the virtual network
3068

3169
When you create an internal load balancer, a virtual network is configured as the network for the load balancer.
@@ -38,57 +76,59 @@ In this section, you'll create a virtual network, subnet, and Azure Bastion host
3876

3977
1. In the search box at the top of the portal, enter **Virtual network**. Select **Virtual Networks** in the search results.
4078

41-
2. In **Virtual networks**, select **+ Create**.
79+
1. In **Virtual networks**, select **+ Create**.
4280

43-
3. In **Create virtual network**, enter or select this information in the **Basics** tab:
81+
1. In **Create virtual network**, enter or select this information in the **Basics** tab:
4482

4583
| **Setting** | **Value** |
4684
|------------------|-----------------------------------------------------------------|
4785
| **Project Details** | |
4886
| Subscription | Select your Azure subscription |
49-
| Resource Group | Select **Create new**. </br> In **Name** enter **CreateIntLBQS-rg**. </br> Select **OK**. |
87+
| Resource Group | Select **CreateIntLBQS-rg**. |
5088
| **Instance details** | |
5189
| Name | Enter **myVNet** |
52-
| Region | Select **West US 3** |
90+
| Region | Select **East US** |
5391

54-
4. Select the **IP Addresses** tab or select the **Next: IP Addresses** button at the bottom of the page.
92+
1. Select the **IP Addresses** tab or select the **Next** button at the bottom of the page.
5593

56-
5. In the **IP Addresses** tab, enter this information:
94+
1. In the **IP Addresses** tab, enter this information:
5795

5896
| Setting | Value |
5997
|--------------------|----------------------------|
6098
| IPv4 address space | Enter **10.1.0.0/16** |
6199

62-
6. Under **Subnet name**, select the word **default**.
100+
1. Under **Subnets**, select the word **default**.
63101

64-
7. In **Edit subnet**, enter this information:
102+
1. In **Edit subnet**, enter this information:
65103

66104
| Setting | Value |
67105
|--------------------|----------------------------|
68106
| Subnet name | Enter **myBackendSubnet** |
69107
| Subnet address range | Enter **10.1.0.0/24** |
108+
| **Security** | |
109+
| NAT Gateway | Select **myNATgateway**. |
70110

71-
8. Select **Save**.
111+
1. Select **Add**.
72112

73-
9. Select the **Security** tab.
113+
1. Select the **Security** tab.
74114

75-
10. Under **BastionHost**, select **Enable**. Enter this information:
115+
1. Under **BastionHost**, select **Enable**. Enter this information:
76116

77117
| Setting | Value |
78118
|--------------------|----------------------------|
79119
| Bastion name | Enter **myBastionHost** |
80-
| AzureBastionSubnet address space | Enter **10.1.1.0/27** |
81-
| Public IP Address | Select **Create new**. </br> For **Name**, enter **myBastionIP**. </br> Select **OK**. |
120+
| AzureBastionSubnet address space | Enter **10.1.1.0/26** |
121+
| Public IP Address | Select **Create new**. </br> Enter **myBastionIP** in Name. </br> Select **OK**. |
82122

83123
> [!IMPORTANT]
84124
85125
> [!INCLUDE [Pricing](../../includes/bastion-pricing.md)]
86126
87127
>
88128
89-
11. Select the **Review + create** tab or select the **Review + create** button.
129+
1. Select the **Review + create** tab or select the **Review + create** button.
90130

91-
12. Select **Create**.
131+
1. Select **Create**.
92132

93133

94134
> [!NOTE]
@@ -100,65 +140,59 @@ In this section, you create a load balancer that load balances virtual machines.
100140

101141
During the creation of the load balancer, you'll configure:
102142

103-
* Frontend IP address
104-
* Backend pool
105-
* Inbound load-balancing rules
143+
- Frontend IP address
144+
- Backend pool
145+
- Inbound load-balancing rules
106146

107147
1. In the search box at the top of the portal, enter **Load balancer**. Select **Load balancers** in the search results.
108148

109-
2. In the **Load balancer** page, select **Create**.
149+
1. In the **Load balancer** page, select **Create**.
110150

111-
3. In the **Basics** tab of the **Create load balancer** page, enter, or select the following information:
151+
1. In the **Basics** tab of the **Create load balancer** page, enter, or select the following information:
112152

113-
| Setting | Value |
114-
| --- | --- |
153+
| Setting | Value |
154+
| --- | --- |
115155
| **Project details** | |
116156
| Subscription | Select your subscription. |
117157
| Resource group | Select **CreateIntLBQS-rg**. |
118158
| **Instance details** | |
119-
| Name | Enter **myLoadBalancer** |
120-
| Region | Select **West US 3**. |
159+
| Name | Enter **myLoadBalancer** |
160+
| Region | Select **East US**. |
121161
| SKU | Leave the default **Standard**. |
122-
| Type | Select **Internal**. |
162+
| Type | Select **Internal**. |
123163
| Tier | Leave the default of **Regional**. |
124164

125-
126165
:::image type="content" source="./media/quickstart-load-balancer-standard-internal-portal/create-standard-internal-load-balancer.png" alt-text="Screenshot of create standard load balancer basics tab." border="true":::
127166

128-
4. Select **Next: Frontend IP configuration** at the bottom of the page.
129-
130-
5. In **Frontend IP configuration**, select **+ Add a frontend IP configuration**.
131-
132-
6. Enter **myFrontend** in **Name**.
133-
134-
7. Select **myBackendSubnet** in **Subnet**.
135-
136-
8. Select **Dynamic** for **Assignment**.
137-
138-
9. Select **Zone-redundant** in **Availability zone**.
139-
140-
10. Select **Add**.
141-
142-
11. Select **Next: Backend pools** at the bottom of the page.
143-
144-
12. In the **Backend pools** tab, select **+ Add a backend pool**.
145-
146-
13. Enter **myBackendPool** for **Name** in **Add backend pool**.
147-
148-
14. Select **NIC** or **IP Address** for **Backend Pool Configuration**.
167+
1. Select **Next: Frontend IP configuration** at the bottom of the page.
149168

150-
15. Select **IPv4** or **IPv6** for **IP version**.
169+
1. In **Frontend IP configuration**, select **+ Add a frontend IP configuration**, then enter or select the following information:
151170

152-
16. Select **Add**.
153-
154-
17. Select the **Next: Inbound rules** button at the bottom of the page.
155-
156-
18. In **Load balancing rule** in the **Inbound rules** tab, select **+ Add a load balancing rule**.
157-
158-
19. In **Add load balancing rule**, enter or select the following information:
171+
| Setting | Value |
172+
| ------- | ----- |
173+
| Name | Enter **myFrontend** |
174+
| Private IP address version | Select **IPv4** or **IPv6** depending on your requirements. |
159175

160176
| Setting | Value |
161177
| ------- | ----- |
178+
| Name | Enter **myFrontend** |
179+
| Virtual network | Select **myVNet** |
180+
| Subnet | Select **myBackendSubnet** |
181+
| Assignment | Select **Dynamic** |
182+
| Availability zone | Select **Zone-redundant** |
183+
184+
1. Select **Add**.
185+
1. Select **Next: Backend pools** at the bottom of the page.
186+
1. In the **Backend pools** tab, select **+ Add a backend pool**.
187+
1. Enter **myBackendPool** for **Name** in **Add backend pool**.
188+
1. Select **IP Address** for **Backend Pool Configuration**.
189+
1. Select **Save**.
190+
1. Select the **Next: Inbound rules** button at the bottom of the page.
191+
1. In **Load balancing rule** in the **Inbound rules** tab, select **+ Add a load balancing rule**.
192+
1. In **Add load balancing rule**, enter or select the following information:
193+
194+
| **Setting** | **Value** |
195+
| ----------- | --------- |
162196
| Name | Enter **myHTTPRule** |
163197
| IP Version | Select **IPv4** or **IPv6** depending on your requirements. |
164198
| Frontend IP address | Select **myFrontend**. |
@@ -169,57 +203,14 @@ During the creation of the load balancer, you'll configure:
169203
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
170204
| Session persistence | Select **None**. |
171205
| Idle timeout (minutes) | Enter or select **15**. |
172-
| TCP reset | Select **Enabled**. |
173-
| Floating IP | Select **Disabled**. |
206+
| Enable TCP reset | Select **checkbox** . |
207+
| Enable Floating IP | Leave the default of unselected. |
174208

175-
20. Select **Add**.
209+
1. Select **Save**.
176210

177-
21. Select the blue **Review + create** button at the bottom of the page.
211+
1. Select the blue **Review + create** button at the bottom of the page.
178212

179-
22. Select **Create**.
180-
181-
> [!NOTE]
182-
> In this example you'll create a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed and isn't needed with the NAT gateway. For more information on Azure NAT gateway, see [What is Azure Virtual Network NAT?](../virtual-network/nat-gateway/nat-overview.md)
183-
> For more information about outbound connections in Azure, see [Source Network Address Translation (SNAT) for outbound connections](../load-balancer/load-balancer-outbound-connections.md)
184-
185-
## Create NAT gateway
186-
187-
In this section, you'll create a NAT gateway for outbound internet access for resources in the virtual network.
188-
189-
1. In the search box at the top of the portal, enter **NAT gateway**. Select **NAT gateways** in the search results.
190-
191-
2. In **NAT gateways**, select **+ Create**.
192-
193-
3. In **Create network address translation (NAT) gateway**, enter or select the following information:
194-
195-
| Setting | Value |
196-
| ------- | ----- |
197-
| **Project details** | |
198-
| Subscription | Select your subscription. |
199-
| Resource group | Select **CreateIntLBQS-rg**. |
200-
| **Instance details** | |
201-
| NAT gateway name | Enter **myNATgateway**. |
202-
| Region | Select **West US 3**. |
203-
| Availability zone | Select **None**. |
204-
| Idle timeout (minutes) | Enter **15**. |
205-
206-
4. Select the **Outbound IP** tab or select the **Next: Outbound IP** button at the bottom of the page.
207-
208-
5. In **Outbound IP**, select **Create a new public IP address** next to **Public IP addresses**.
209-
210-
6. Enter **myNATgatewayIP** in **Name** in **Add a public IP address**.
211-
212-
7. Select **OK**.
213-
214-
8. Select the **Subnet** tab or select the **Next: Subnet** button at the bottom of the page.
215-
216-
9. In **Virtual network**, select **myVNet**.
217-
218-
10. Select **myBackendSubnet** under **Subnet name**.
219-
220-
11. Select the blue **Review + create** button at the bottom of the page, or select the **Review + create** tab.
221-
222-
12. Select **Create**.
213+
1. Select **Create**.
223214

224215
## Create virtual machines
225216

@@ -240,7 +231,7 @@ These VMs are added to the backend pool of the load balancer that was created ea
240231
| Resource Group | Select **CreateIntLBQS-rg** |
241232
| **Instance details** | |
242233
| Virtual machine name | Enter **myVM1** |
243-
| Region | Select **(US) West US 3** |
234+
| Region | Select **(US) East US** |
244235
| Availability Options | Select **Availability zones** |
245236
| Availability zone | Select **1** |
246237
| Security type | Select **Standard**. |
@@ -304,10 +295,10 @@ In this section, you'll create a VM named **myTestVM**. This VM will be used to
304295
| Resource Group | Select **CreateIntLBQS-rg** |
305296
| **Instance details** | |
306297
| Virtual machine name | Enter **myTestVM** |
307-
| Region | Select **(US) West US 3** |
298+
| Region | Select **(US) East US** |
308299
| Availability Options | Select **No infrastructure redundancy required** |
309300
| Security type | Select **Standard**. |
310-
| Image | Select **Windows Server 2019 Datacenter - Gen2** |
301+
| Image | Select **Windows Server 2022 Datacenter - x64 Gen2** |
311302
| Azure Spot instance | Leave the default of unselected. |
312303
| Size | Choose VM size or take default setting |
313304
| **Administrator account** | |
@@ -388,13 +379,14 @@ In this section, you'll test the load balancer by connecting to the **myTestVM**
388379

389380
7. Enter the username and password entered during VM creation.
390381

391-
8. Open **Internet Explorer** on **myTestVM**.
382+
8. Open **Microsoft Edge** on **myTestVM**.
392383

393384
9. Enter the IP address from the previous step into the address bar of the browser. The custom page displaying one of the backend server names is displayed on the browser. In this example, it's **10.1.0.4**.
394385

395386
:::image type="content" source="./media/quickstart-load-balancer-standard-internal-portal/load-balancer-test.png" alt-text="Screenshot shows a browser window displaying the customized page, as expected." border="true":::
396387

397-
To see the load balancer distribute traffic across both VMs, you can force-refresh your web browser from the client machine.
388+
1. To see the load balancer distribute traffic across both VMs, navigate to the VM shown in the browser message, and stop the VM.
389+
1. Refresh the browser window. The page should still display the customized page. The load balancer is now only sending traffic to the remaining VM.
398390

399391
## Clean up resources
400392

@@ -404,11 +396,11 @@ When no longer needed, delete the resource group, load balancer, and all related
404396

405397
In this quickstart, you:
406398

407-
* Created an internal Azure Load Balancer
399+
- Created an internal Azure Load Balancer
408400

409-
* Attached 2 VMs to the load balancer
401+
- Attached 2 VMs to the load balancer
410402

411-
* Configured the load balancer traffic rule, health probe, and then tested the load balancer
403+
- Configured the load balancer traffic rule, health probe, and then tested the load balancer
412404

413405
To learn more about Azure Load Balancer, continue to:
414406
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)