Skip to content

Commit cba7c3c

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #282312 from asudbring/nat-patch
Updated screenshots and verbiage in NAT gateway hub/spoke tutorial
2 parents 420a0db + 5cd2897 commit cba7c3c

File tree

1 file changed

+73
-57
lines changed

1 file changed

+73
-57
lines changed

‎articles/nat-gateway/tutorial-hub-spoke-route-nat.md

Lines changed: 73 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: asudbring
66
ms.author: allensu
77
ms.service: nat-gateway
88
ms.topic: tutorial
9-
ms.date: 07/13/2023
9+
ms.date: 07/30/2024
1010
ms.custom: template-tutorial
1111
---
1212

@@ -89,7 +89,7 @@ The hub virtual network is the central network of the solution. The hub network
8989

9090
1. Select **Next** to proceed to the **Security** tab.
9191

92-
1. Select **Enable Bastion** in the **Azure Bastion** section of the **Security** tab.
92+
1. Select **Enable Azure Bastion** in the **Azure Bastion** section of the **Security** tab.
9393

9494
Azure Bastion uses your browser to connect to VMs in your virtual network over secure shell (SSH) or remote desktop protocol (RDP) by using their private IP addresses. The VMs don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see [Azure Bastion](/azure/bastion/bastion-overview)
9595

@@ -101,7 +101,7 @@ The hub virtual network is the central network of the solution. The hub network
101101
| Setting | Value |
102102
|---|---|
103103
| Azure Bastion host name | Enter **bastion**. |
104-
| Azure Bastion public IP address | Select **Create a public IP address**. </br> Enter **public-ip** in Name. </br> Select **OK**. |
104+
| Azure Bastion public IP address | Select **Create a public IP address**. </br> Enter **public-ip-bastion** in Name. </br> Select **OK**. |
105105

106106
1. Select **Next** to proceed to the **IP Addresses** tab.
107107

@@ -111,25 +111,27 @@ The hub virtual network is the central network of the solution. The hub network
111111

112112
| Setting | Value |
113113
|---|---|
114-
| **Subnet details** | |
115-
| Subnet template | Leave the default **Default**. |
114+
| Subnet purpose | Leave the default **Default**. |
116115
| Name | Enter **subnet-private**. |
116+
| **IPv4** | |
117+
| IPv4 address range | Leave the default of **10.0.0.0/16**. |
117118
| Starting address | Leave the default of **10.0.0.0**. |
118-
| Subnet size | Leave the default of **/24(256 addresses)**. |
119+
| Size | Leave the default of **/24(256 addresses)**. |
119120

120121
1. Select **Save**.
121122

122-
1. Select **+ Add subnet**.
123+
1. Select **+ Add a subnet**.
123124

124125
1. In **Add subnet**, enter or select the following information:
125126

126127
| Setting | Value |
127128
|---|---|
128-
| **Subnet details** | |
129-
| Subnet template | Leave the default **Default**. |
129+
| Subnet purpose | Leave the default **Default**. |
130130
| Name | Enter **subnet-public**. |
131+
| **IPv4** | |
132+
| IPv4 address range | Leave the default of **10.0.0.0/16**. |
131133
| Starting address | Enter **10.0.253.0**. |
132-
| Subnet size | Select **/28(16 addresses)**. |
134+
| Size | Select **/28(16 addresses)**. |
133135
| **Security** | |
134136
| NAT gateway | Select **nat-gateway**. |
135137

@@ -161,7 +163,7 @@ The simulated NVA acts as a virtual appliance to route all traffic between the s
161163
| Region | Select **(US) East US 2**. |
162164
| Availability options | Select **No infrastructure redundancy required**. |
163165
| Security type | Select **Standard**. |
164-
| Image | Select **Ubuntu Server 22.04 LTS - x64 Gen2**. |
166+
| Image | Select **Ubuntu Server 24.04 LTS - x64 Gen2**. |
165167
| VM architecture | Leave the default of **x64**. |
166168
| Size | Select a size. |
167169
| **Administrator account** | |
@@ -199,9 +201,9 @@ The IP configuration of the primary network interface of the virtual machine is
199201

200202
1. In the **Overview** select **Stop** if the virtual machine is running.
201203

202-
1. Select **Networking** in **Settings**.
204+
1. Expand **Networking** then select **Network settings**.
203205

204-
1. In **Networking** select the network interface name next to **Network Interface:**. The interface name is the virtual machine name and random numbers and letters. In this example, the interface name is **vm-nva271**.
206+
1. In **Network settings** select the network interface name next to **Network Interface:**. The interface name is the virtual machine name and random numbers and letters. In this example, the interface name is **vm-nva271**.
205207

206208
1. In the network interface properties, select **IP configurations** in **Settings**.
207209

@@ -211,15 +213,15 @@ The IP configuration of the primary network interface of the virtual machine is
211213

212214
1. When the apply action completes, select **ipconfig1**.
213215

214-
1. In **Assignment** in **ipconfig1** select **Static**.
216+
1. In **Private IP address settings** in **ipconfig1** select **Static**.
215217

216218
1. In **Private IP address** enter **10.0.253.10**.
217219

218220
1. Select **Save**.
219221

220222
1. When the save action completes, return to the networking configuration for **vm-nva**.
221223

222-
1. In **Networking** of **vm-nva** select **Attach network interface**.
224+
1. In **Network settings** of **vm-nva** select **Attach network interface**.
223225

224226
1. Select **Create and attach network interface**.
225227

@@ -251,7 +253,7 @@ The routing for the simulated NVA uses IP tables and internal NAT in the Ubuntu
251253

252254
1. When the virtual machine is completed booting, continue with the next steps.
253255

254-
1. In **Operations**, select **Bastion**.
256+
1. In the **Overview** section, select **Connect**, then select **Connect via Bastion**.
255257

256258
1. Enter the username and password you entered when the virtual machine was created.
257259

@@ -344,7 +346,7 @@ Route tables are used to overwrite Azure's default routing. Create a route table
344346
345347
1. Select **route-table-nat-hub**.
346348
347-
1. In **Settings** select **Routes**.
349+
1. Expand **Settings** then select **Routes**.
348350
349351
1. Select **+ Add** in **Routes**.
350352
@@ -396,7 +398,9 @@ Create another virtual network in a different region for the first spoke of the
396398
397399
1. Select **Next** to proceed to the **IP addresses** tab.
398400
399-
1. In the **IP Addresses** tab in **IPv4 address space**, select the trash can to delete the address space that is auto populated.
401+
1. In the **IP Addresses** tab in **IPv4 address space**, select **Delete address space** to delete the address space that is auto populated.
402+
403+
1. Select **Add IPv4 address space**.
400404
401405
1. In **IPv4 address space** enter **10.1.0.0**. Leave the default of **/16 (65,536 addresses)** in the mask selection.
402406
@@ -406,11 +410,12 @@ Create another virtual network in a different region for the first spoke of the
406410
407411
| Setting | Value |
408412
| ------- | ----- |
409-
| **Subnet details** | |
410-
| Subnet template | Leave the default **Default**. |
413+
| Subnet purpose | Leave the default **Default**. |
411414
| Name | Enter **subnet-private**. |
412-
| Starting address | Enter **10.1.0.0**. |
413-
| Subnet size | Leave the default of **/24(256 addresses)**. |
415+
| **IPv4** | |
416+
| IPv4 address range| Leave the default of **10.1.0.0/16**. |
417+
| Starting address | Leave the default of **10.1.0.0**. |
418+
| Size | Leave the default of **/24(256 addresses)**. |
414419
415420
1. Select **Add**.
416421
@@ -433,22 +438,24 @@ A virtual network peering is used to connect the hub to spoke one and spoke one
433438
1. Enter or select the following information in **Add peering**:
434439
435440
| Setting | Value |
436-
| ------- | ----- |
437-
| **This virtual network** | |
438-
| Peering link name | Enter **vnet-hub-to-vnet-spoke-1**. |
439-
| Allow 'vnet-hub' to access 'vnet-spoke-1' | Leave the default of **Selected**. |
440-
| Allow 'vnet-hub' to receive forwarded traffic from 'vnet-spoke-1' | **Select** the checkbox. |
441-
| Allow gateway in 'vnet-hub' to forward traffic to 'vnet-spoke-1' | Leave the default of **Unselected**. |
442-
| Enable 'vnet-hub' to use 'vnet-spoke-1's' remote gateway | Leave the default of **Unselected**. |
443-
| **Remote virtual network** | |
441+
| ------- | -----
442+
| **Remote virtual network summary** | |
444443
| Peering link name | Enter **vnet-spoke-1-to-vnet-hub**. |
445444
| Virtual network deployment model | Leave the default of **Resource manager**. |
446445
| Subscription | Select your subscription. |
447-
| Virtual network | Select **vnet-spoke-1**. |
446+
| Virtual network | Select **vnet-spoke-1 (test-rg)**. |
447+
| **Remote virtual network peering settings** | |
448448
| Allow 'vnet-spoke-1' to access 'vnet-hub' | Leave the default of **Selected**. |
449-
| Allow 'vnet-spoke-1' to receive forwarded traffic from 'vnet-hub' | **Select** the checkbox. |
450-
| Allow gateway in 'vnet-spoke-1' to forward traffic to 'vnet-hub' | Leave the default of **Unselected**. |
451-
| Enable 'vnet-spoke-1' to use 'vnet-hub's' remote gateway | Leave the default of **Unselected**. |
449+
| Allow 'vnet-spoke-1' to receive forwarded traffic from 'vnet-hub' | Select the checkbox. |
450+
| Allow gateway or route server in 'vnet-spoke-1' to forward traffic to 'vnet-hub' | Leave the default of **Unselected**. |
451+
| Enable 'vnet-spoke-1' to use 'vnet-hub's' remote gateway or route server | Leave the default of **Unselected**. |
452+
| **Local virtual network summary** | |
453+
| Peering link name | Enter **vnet-hub-to-vnet-spoke-1**. |
454+
| **Local virtual network peering settings** | |
455+
| Allow 'vnet-hub' to access 'vnet-spoke-1' | Leave the default of **Selected**. |
456+
| Allow 'vnet-hub' to receive forwarded traffic from 'vnet-spoke-1' | Select the checkbox. |
457+
| Allow gateway or route server in 'vnet-hub' to forward traffic to 'vnet-spoke-1' | Leave the default of **Unselected**. |
458+
| Enable 'vnet-hub' to use 'vnet-spoke-1's' remote gateway or route server | Leave the default of **Unselected**. |
452459
453460
1. Select **Add**.
454461
@@ -562,6 +569,8 @@ A Windows Server 2022 virtual machine is used to test the outbound internet traf
562569
563570
1. Select **Create**.
564571
572+
Wait for the virtual machine to finishing deploying before continuing to the next steps.
573+
565574
## Install IIS on spoke one test virtual machine
566575
567576
IIS is installed on the Windows Server 2022 virtual machine to test outbound internet traffic through the NAT gateway and inter-spoke traffic in the hub and spoke network.
@@ -570,7 +579,7 @@ IIS is installed on the Windows Server 2022 virtual machine to test outbound int
570579
571580
1. Select **vm-spoke-1**.
572581
573-
1. In **Operations**, select **Run command**.
582+
1. Expand **Operations** then select **Run command**.
574583
575584
1. Select **RunPowerShellScript**.
576585
@@ -591,7 +600,7 @@ IIS is installed on the Windows Server 2022 virtual machine to test outbound int
591600
592601
1. Wait for the script to complete before continuing to the next step. It can take a few minutes for the script to complete.
593602
594-
1. When the script completes, the **Output*** displays the following:
603+
1. When the script completes, the **Output** displays the following:
595604
596605
```output
597606
Success Restart Needed Exit Code Feature Result
@@ -622,7 +631,9 @@ Create the second virtual network for the second spoke of the hub and spoke netw
622631
623632
1. Select **Next** to proceed to the **IP addresses** tab.
624633
625-
1. In the **IP Addresses** tab in **IPv4 address space**, select the trash can to delete the address space that is auto populated.
634+
1. In the **IP Addresses** tab in **IPv4 address space**, select **Delete address space** to delete the address space that is auto populated.
635+
636+
1. Select **Add IPv4 address space**.
626637
627638
1. In **IPv4 address space** enter **10.2.0.0**. Leave the default of **/16 (65,536 addresses)** in the mask selection.
628639
@@ -632,11 +643,12 @@ Create the second virtual network for the second spoke of the hub and spoke netw
632643
633644
| Setting | Value |
634645
| ------- | ----- |
635-
| **Subnet details** | |
636-
| Subnet template | Leave the default **Default**. |
646+
| Subnet purpose | Leave the default **Default**. |
637647
| Name | Enter **subnet-private**. |
638-
| Starting address | Enter **10.2.0.0**. |
639-
| Subnet size | Leave the default of **/24(256 addresses)**. |
648+
| **IPv4** | |
649+
| IPv4 address range | Leave the default of **10.2.0.0/16**. |
650+
| Starting address | Leave the default of **10.2.0.0**. |
651+
| Size | Leave the default of **/24(256 addresses)**. |
640652
641653
1. Select **Add**.
642654
@@ -667,23 +679,25 @@ Create a two-way virtual network peer between the hub and spoke two.
667679
1. Enter or select the following information in **Add peering**:
668680
669681
| Setting | Value |
670-
| ------- | ----- |
671-
| **This virtual network** | |
672-
| Peering link name | Enter **vnet-hub-to-vnet-spoke-2**. |
673-
| Allow 'vnet-hub' to access 'vnet-spoke-2' | Leave the default of **Selected**. |
674-
| Allow 'vnet-hub' to receive forwarded traffic from 'vnet-spoke-2' | **Select** the checkbox. |
675-
| Allow gateway in 'vnet-hub' to forward traffic to 'vnet-spoke-2' | Leave the default of **Unselected**. |
676-
| Enable 'vnet-hub' to use 'vnet-spoke-2's' remote gateway | Leave the default of **Unselected**. |
677-
| **Remote virtual network** | |
682+
| ------- | -----
683+
| **Remote virtual network summary** | |
678684
| Peering link name | Enter **vnet-spoke-2-to-vnet-hub**. |
679685
| Virtual network deployment model | Leave the default of **Resource manager**. |
680686
| Subscription | Select your subscription. |
681-
| Virtual network | Select **vnet-spoke-2**. |
682-
| Allow 'vnet-spoke-1' to access 'vnet-hub' | Leave the default of **Selected**. |
683-
| Allow 'vnet-spoke-1' to receive forwarded traffic from 'vnet-hub' | **Select** the checkbox. |
684-
| Allow gateway in 'vnet-spoke-1' to forward traffic to 'vnet-hub' | Leave the default of **Unselected**. |
685-
| Enable 'vnet-spoke-1' to use 'vnet-hub's' remote gateway | Leave the default of **Unselected**. |
686-
687+
| Virtual network | Select **vnet-spoke-2 (test-rg)**. |
688+
| **Remote virtual network peering settings** | |
689+
| Allow 'vnet-spoke-2' to access 'vnet-hub' | Leave the default of **Selected**. |
690+
| Allow 'vnet-spoke-2' to receive forwarded traffic from 'vnet-hub' | Select the checkbox. |
691+
| Allow gateway or route server in 'vnet-spoke-2' to forward traffic to 'vnet-hub' | Leave the default of **Unselected**. |
692+
| Enable 'vnet-spoke-2' to use 'vnet-hub's' remote gateway or route server | Leave the default of **Unselected**. |
693+
| **Local virtual network summary** | |
694+
| Peering link name | Enter **vnet-hub-to-vnet-spoke-2**. |
695+
| **Local virtual network peering settings** | |
696+
| Allow 'vnet-hub' to access 'vnet-spoke-2' | Leave the default of **Selected**. |
697+
| Allow 'vnet-hub' to receive forwarded traffic from 'vnet-spoke-2' | Select the checkbox. |
698+
| Allow gateway or route server in 'vnet-hub' to forward traffic to 'vnet-spoke-2' | Leave the default of **Unselected**. |
699+
| Enable 'vnet-hub' to use 'vnet-spoke-2's' remote gateway or route server | Leave the default of **Unselected**. |
700+
687701
1. Select **Add**.
688702
689703
1. Select **Refresh** and verify **Peering status** is **Connected**.
@@ -794,6 +808,8 @@ Create a Windows Server 2022 virtual machine for the test virtual machine in spo
794808
795809
1. Select **Create**.
796810
811+
Wait for the virtual machine to finish deploying before continuing to the next steps.
812+
797813
## Install IIS on spoke two test virtual machine
798814
799815
IIS is installed on the Windows Server 2022 virtual machine to test outbound internet traffic through the NAT gateway and inter-spoke traffic in the hub and spoke network.
@@ -853,7 +869,7 @@ Use Microsoft Edge on the Windows Server 2022 virtual machine to connect to http
853869
854870
1. Select **vm-spoke-1**.
855871
856-
1. In **Operations**, select **Bastion**.
872+
1. In **Overview**, select **Connect** then **Connect via Bastion**.
857873
858874
1. Enter the username and password you entered when the virtual machine was created.
859875
@@ -877,7 +893,7 @@ Use Microsoft Edge on the Windows Server 2022 virtual machine to connect to http
877893
878894
1. Select **vm-spoke-2**.
879895
880-
1. In **Operations**, select **Bastion**.
896+
1. In **Overview**, select **Connect** then **Connect via Bastion**.
881897
882898
1. Enter the username and password you entered when the virtual machine was created.
883899

0 commit comments

Comments
 (0)