@@ -93,27 +93,43 @@ Now, create the VNet:
93
93
1 . From the Azure portal home page, select ** Create a resource** .
94
94
2 . Under ** Networking** , select ** Virtual network** .
95
95
4 . For ** Name** , type ** VNet-Spoke** .
96
- 5 . For ** Address space** , type ** 192.168 .0.0/16** .
96
+ 5 . For ** Address space** , type ** 10.6 .0.0/16** .
97
97
6 . For ** Subscription** , select your subscription.
98
98
7 . For ** Resource group** , select ** Test-FW-RG** .
99
99
8 . For ** Location** , select the same location that you used previously.
100
100
9 . Under ** Subnet** , for ** Name** type ** SN-Workload** .
101
- 10 . For ** Address range** , type ** 10.6.1 .0/24** .
101
+ 10 . For ** Address range** , type ** 10.6.0 .0/24** .
102
102
11 . Accept the other default settings, and then select ** Create** .
103
103
104
+ Now create a second subnet for the gateway.
105
+
106
+ 1 . On the ** VNet-Spoke** page, select ** Subnets** .
107
+ 2 . Select ** +Subnet** .
108
+ 3 . For ** Name** , type ** GatewaySubnet** .
109
+ 4 . For ** Address range (CIDR block)** type ** 10.6.1.0/24** .
110
+ 5 . Select ** OK** .
111
+
104
112
## Create the on-premises virtual network
105
113
106
114
1 . From the Azure portal home page, select ** Create a resource** .
107
115
2 . Under ** Networking** , select ** Virtual network** .
108
116
4 . For ** Name** , type ** VNet-OnPrem** .
109
- 5 . For ** Address space** , type ** 10.6 .0.0/16** .
117
+ 5 . For ** Address space** , type ** 192.168 .0.0/16** .
110
118
6 . For ** Subscription** , select your subscription.
111
119
7 . For ** Resource group** , select ** FW-Hybrid-Test** .
112
120
8 . For ** Location** , select the same location that you used previously.
113
121
9 . Under ** Subnet** , for ** Name** type ** SN-Corp** .
114
122
10 . For ** Address range** , type ** 192.168.1.0/24** .
115
123
11 . Accept the other default settings, and then select ** Create** .
116
124
125
+ Now create a second subnet for the gateway.
126
+
127
+ 1 . On the ** VNet-Onprem** page, select ** Subnets** .
128
+ 2 . Select ** +Subnet** .
129
+ 3 . For ** Name** , type ** GatewaySubnet** .
130
+ 4 . For ** Address range (CIDR block)** type ** 192.168.2.0/24** .
131
+ 5 . Select ** OK** .
132
+
117
133
### Create a public IP address
118
134
119
135
This is the public IP address used for the on-premises gateway.
@@ -124,8 +140,7 @@ This is the public IP address used for the on-premises gateway.
124
140
4 . For the name, type ** VNet-Onprem-GW-pip** .
125
141
5 . For the resource group, type ** FW-Hybrid-Test** .
126
142
6 . For ** Location** , select the same location that you used previously.
127
-
128
- Accept the other defaults, and then select ** Create** .
143
+ 7 . Accept the other defaults, and then select ** Create** .
129
144
130
145
## Configure and deploy the firewall
131
146
@@ -141,13 +156,13 @@ Now deploy the firewall into the firewall hub virtual network.
141
156
| Resource group | ** FW-Hybrid-Test** |
142
157
| Name | ** AzFW01** |
143
158
| Location | Select the same location that you used previously|
144
- | Choose a virtual network | ** Use existing** : ** VNet-hub** |
145
- | Public IP address | ** Create new** . The Public IP address must be the Standard SKU type. |
159
+ | Choose a virtual network | ** Use existing** :< br > ** VNet-hub** |
160
+ | Public IP address | Create new: < br > ** Name ** - ** fw-pip ** . |
146
161
147
162
5 . Select ** Review + create** .
148
163
6 . Review the summary, and then select ** Create** to create the firewall.
149
164
150
- This will take a few minutes to deploy.
165
+ This takes a few minutes to deploy.
151
166
7 . After deployment completes, go to the ** FW-Hybrid-Test** resource group, and select the ** AzFW01** firewall.
152
167
8 . Note the private IP address. You'll use it later when you create the default route.
153
168
@@ -225,7 +240,7 @@ In this step, you create the connection from the hub virtual network to the on-p
225
240
1 . Open the ** FW-Hybrid-Test** resource group and select the ** GW-hub** gateway.
226
241
2 . Select ** Connections** in the left column.
227
242
3 . Select ** Add** .
228
- 4 . The the connection name, type ** hub -to-Onprem** .
243
+ 4 . The the connection name, type ** Hub -to-Onprem** .
229
244
5 . Select ** VNet-to-VNet** for ** Connection type** .
230
245
6 . For the ** Second virtual network gateway** , select ** GW-Onprem** .
231
246
7 . For ** Shared key (PSK)** , type ** AzureA1b2C3** .
@@ -236,7 +251,7 @@ Create the on-premises to hub virtual network connection. This step is similar t
236
251
1 . Open the ** FW-Hybrid-Test** resource group and select the ** GW-Onprem** gateway.
237
252
2 . Select ** Connections** in the left column.
238
253
3 . Select ** Add** .
239
- 4 . The the connection name, type ** OnPrem -to-hub ** .
254
+ 4 . The the connection name, type ** Onprem -to-Hub ** .
240
255
5 . Select ** VNet-to-VNet** for ** Connection type** .
241
256
6 . For the ** Second virtual network gateway** , select ** GW-hub** .
242
257
7 . For ** Shared key (PSK)** , type ** AzureA1b2C3** .
@@ -298,7 +313,7 @@ Next, create a couple routes:
298
313
299
314
Now associate the route to the subnet.
300
315
301
- 1 . On the ** UDR-Hub-Spoke** page, select ** Subnets** .
316
+ 1 . On the ** UDR-Hub-Spoke - Routes ** page, select ** Subnets** .
302
317
2 . Select ** Associate** .
303
318
3 . Select ** Choose a virtual network** .
304
319
4 . Select ** VNet-hub** .
@@ -327,7 +342,7 @@ Now create the default route from the spoke subnet.
327
342
328
343
Now associate the route to the subnet.
329
344
330
- 1 . On the ** UDR-DG** page, select ** Subnets** .
345
+ 1 . On the ** UDR-DG - Routes ** page, select ** Subnets** .
331
346
2 . Select ** Associate** .
332
347
3 . Select ** Choose a virtual network** .
333
348
4 . Select ** VNet-spoke** .
@@ -345,14 +360,14 @@ Create a virtual machine in the spoke virtual network, running IIS, with no publ
345
360
1 . From the Azure portal home page, select ** Create a resource** .
346
361
2 . Under ** Popular** , select ** Windows Server 2016 Datacenter** .
347
362
3 . Enter these values for the virtual machine:
348
- - ** Resource group** - Select existing, and then select ** FW-Hybrid-Test** .
349
- - ** Virtual machine name** - * VM-Spoke-01* .
363
+ - ** Resource group** - Select ** FW-Hybrid-Test** .
364
+ - ** Virtual machine name** : * VM-Spoke-01* .
350
365
- ** Region** - Same region that you're used previously.
351
- - ** User name** - * azureuser* .
352
- - ** Password** - * Azure123456!* .
366
+ - ** User name** : * azureuser* .
367
+ - ** Password** : * Azure123456!*
353
368
4 . Select ** Next: Disks ** .
354
369
5 . Accept the defaults and select ** Next: Networking ** .
355
- 6 . Make sure that ** VNet-Spoke** is selected for the virtual network and the subnet is ** SN-Workload** .
370
+ 6 . Select ** VNet-Spoke** for the virtual network and the subnet is ** SN-Workload** .
356
371
7 . For ** Public IP** , select ** None** .
357
372
8 . For ** Public inbound ports** , select ** Allow selected ports** , and then select ** HTTP (80)** , and ** RDP (3389)**
358
373
9 . Select ** Next: Management ** .
@@ -361,20 +376,20 @@ Create a virtual machine in the spoke virtual network, running IIS, with no publ
361
376
362
377
### Install IIS
363
378
364
- 1 . Open the interactive shell and make sure that it's set to ** PowerShell** .
379
+ 1 . From the Azure portal, open the Cloud Shell and make sure that it's set to ** PowerShell** .
365
380
2 . Run the following command to install IIS on the virtual machine:
366
381
367
- ``` azurepowershell-interactive
368
- Set-AzVMExtension `
369
- -ResourceGroupName FW-Hybrid-Test `
370
- -ExtensionName IIS `
371
- -VMName VM-Spoke-01 `
372
- -Publisher Microsoft.Compute `
373
- -ExtensionType CustomScriptExtension `
374
- -TypeHandlerVersion 1.4 `
375
- -SettingString '{"commandToExecute":"powershell Add-WindowsFeature Web-Server; powershell Add-Content -Path \"C:\\inetpub\\wwwroot\\Default.htm\" -Value $($env:computername)"}' `
376
- -Location EastUS
377
- ```
382
+ ``` azurepowershell-interactive
383
+ Set-AzVMExtension `
384
+ -ResourceGroupName FW-Hybrid-Test `
385
+ -ExtensionName IIS `
386
+ -VMName VM-Spoke-01 `
387
+ -Publisher Microsoft.Compute `
388
+ -ExtensionType CustomScriptExtension `
389
+ -TypeHandlerVersion 1.4 `
390
+ -SettingString '{"commandToExecute":"powershell Add-WindowsFeature Web-Server; powershell Add-Content -Path \"C:\\inetpub\\wwwroot\\Default.htm\" -Value $($env:computername)"}' `
391
+ -Location EastUS
392
+ ```
378
393
379
394
### Create the on-premises virtual machine
380
395
@@ -386,11 +401,11 @@ This is a virtual machine that you use to connect using Remote Desktop to the pu
386
401
- ** Resource group** - Select existing, and then select ** FW-Hybrid-Test** .
387
402
- ** Virtual machine name** - * VM-Onprem* .
388
403
- ** Region** - Same region that you're used previously.
389
- - **User name** - *azureuser*.
390
- - **Password** - *Azure123456!*.
404
+ - ** User name** : * azureuser* .
405
+ - ** Password** : * Azure123456!* .
391
406
4 . Select ** Next: Disks ** .
392
407
5 . Accept the defaults and select ** Next: Networking ** .
393
- 6. Make sure that **VNet-Onprem** is selected for the virtual network and the subnet is **SN-Corp**.
408
+ 6 . Select ** VNet-Onprem** for virtual network and the subnet is ** SN-Corp** .
394
409
7 . For ** Public inbound ports** , select ** Allow selected ports** , and then select ** RDP (3389)**
395
410
8 . Select ** Next: Management ** .
396
411
9 . For ** Boot diagnostics** , Select ** Off** .
@@ -406,11 +421,12 @@ This is a virtual machine that you use to connect using Remote Desktop to the pu
406
421
You should get a reply.--->
407
422
3 . Open a web browser on ** VM-Onprem** , and browse to http://\< VM-spoke-01 private IP\> .
408
423
409
- You should see the Internet Information Services default page.
424
+ You should see the ** VM-spoke-01** web page:
425
+ ![ VM-Spoke-01 web page] ( media/tutorial-hybrid-portal/VM-Spoke-01-web.png )
410
426
411
- 4. From **VM-Onprem**, open a remote desktop to **VM-spoke-01** at the private IP address.
427
+ 4 . From the ** VM-Onprem** virtual machine , open a remote desktop to ** VM-spoke-01** at the private IP address.
412
428
413
- Your connection should succeed, and you should be able to sign in using your chosen username and password .
429
+ Your connection should succeed, and you should be able to sign in.
414
430
415
431
So now you've verified that the firewall rules are working:
416
432
0 commit comments