Skip to content

Commit 8080cf2

Browse files
authored
Merge pull request #299346 from mbender-ms/avnm-sec-hs-us426193
virtual network manager | UUF | Updated article tutorial-create-secured-hub-and-spoke.md
2 parents 1df91a4 + cd0f615 commit 8080cf2

File tree

2 files changed

+21
-4
lines changed

2 files changed

+21
-4
lines changed

articles/virtual-network-manager/tutorial-create-secured-hub-and-spoke.md

Lines changed: 21 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,26 @@ This procedure walks you through creating three virtual networks that will be co
6969
| vnet-learn-prod-eastus-002 IP addresses | IPv4 address space: 10.1.0.0/16 </br> Subnet name: default </br> Subnet address space: 10.1.0.0/24|
7070
| vnet-learn-hub-eastus-001 IP addresses | IPv4 address space: 10.2.0.0/16 </br> Subnet name: default </br> Subnet address space: 10.2.0.0/24|
7171

72+
## Create a virtual network gateway subnet
73+
74+
Create a virtual network gateway subnet in the hub virtual network. This subnet is used by the virtual network gateway to route traffic to and from the virtual network.
75+
76+
1. Go to **vnet-learn-hub-eastus-001** virtual network and select **Subnets** under **Settings**.
77+
1. Select **+ Subnet** to create a new subnet.
78+
1. In the *Add subnet* page, enter or select the following information:
79+
80+
| Setting | Value |
81+
| ------- | ----- |
82+
| Subnet purpose | Select **Virtual network gateway** from the dropdown menu. |
83+
| **IPv4** | |
84+
| Size | Select **/27** from the dropdown menu. |
85+
86+
1. Select **Add** and verify the new subnet is created.
87+
88+
> [!NOTE]
89+
> The gateway subnet is a special subnet that is used by the virtual network gateway. The size of the gateway subnet must be at least **/27**. The address space of the gateway subnet must not overlap with any other subnets in the virtual network. The address space of the gateway subnet must be a subset of the address space of the virtual network.
90+
> Also, the gateway subnet must be named **GatewaySubnet**. If you don't name the subnet **GatewaySubnet**, the virtual network gateway won't be able to use it.
91+
7292
## Deploy a virtual network gateway
7393

7494
Deploy a virtual network gateway into the hub virtual network. This virtual network gateway is necessary for the spokes to *Use hub as a gateway* setting.
@@ -77,8 +97,6 @@ Deploy a virtual network gateway into the hub virtual network. This virtual netw
7797

7898
1. On the *Basics* tab, enter or select the following settings:
7999

80-
:::image type="content" source="./media/tutorial-create-secured-hub-and-spoke/gateway-basics.png" alt-text="Screenshot of create the virtual network gateway basics tab.":::
81-
82100
| Setting | Value |
83101
| -------- | ----- |
84102
| Subscription | Select the subscription you want to deploy this virtual network into. |
@@ -90,7 +108,6 @@ Deploy a virtual network gateway into the hub virtual network. This virtual netw
90108
| Public IP address name | Enter the name **gwpip-learn-hub-eastus-001** for the public IP. |
91109
| **SECOND PUBLIC IP ADDRESS** | |
92110
| Public IP address name | Enter the name **gwpip-learn-hub-eastus-002** for the public IP. |
93-
94111

95112
1. Select **Review + create** and then select **Create** after validation has passed. The deployment of a virtual network gateway can take about 30 minutes. You can move on to the next section while waiting for this deployment to complete. However, you may find **gw-learn-hub-eastus-001** doesn't display that it has a gateway due to timing and sync across the Azure portal.
96113

@@ -232,7 +249,7 @@ Make sure the virtual network gateway has been successfully deployed before depl
232249

233250
:::image type="content" source="./media/tutorial-create-secured-hub-and-spoke/verify-security-admin-configuration.png" alt-text="Screenshot of security admin configuration applied to the virtual network.":::
234251

235-
1. Select **Peerings** under **Settings** to list the virtual network peerings created by Virtual Network Manager. Its name starts with **ANM_**.
252+
1. Go to **vnet-learn-hub-eastus-001** and select **Peerings** under **Settings** to list the virtual network peerings created by Virtual Network Manager. Its name starts with **ANM_**.
236253

237254
:::image type="content" source="./media/tutorial-create-secured-hub-and-spoke/vnet-peerings.png" alt-text="Screenshot of virtual network peerings created by Virtual Network Manager." lightbox="media/tutorial-create-secured-hub-and-spoke/vnet-peerings-large.png":::
238255

0 commit comments

Comments
 (0)