Skip to content

Commit 6999bb1

Browse files
committed
run through test, add image
1 parent 865aa80 commit 6999bb1

File tree

2 files changed

+51
-35
lines changed

2 files changed

+51
-35
lines changed
17.2 KB
Loading

articles/firewall/tutorial-hybrid-portal.md

Lines changed: 51 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -93,27 +93,43 @@ Now, create the VNet:
9393
1. From the Azure portal home page, select **Create a resource**.
9494
2. Under **Networking**, select **Virtual network**.
9595
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**.
9797
6. For **Subscription**, select your subscription.
9898
7. For **Resource group**, select **Test-FW-RG**.
9999
8. For **Location**, select the same location that you used previously.
100100
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**.
102102
11. Accept the other default settings, and then select **Create**.
103103

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+
104112
## Create the on-premises virtual network
105113

106114
1. From the Azure portal home page, select **Create a resource**.
107115
2. Under **Networking**, select **Virtual network**.
108116
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**.
110118
6. For **Subscription**, select your subscription.
111119
7. For **Resource group**, select **FW-Hybrid-Test**.
112120
8. For **Location**, select the same location that you used previously.
113121
9. Under **Subnet**, for **Name** type **SN-Corp**.
114122
10. For **Address range**, type **192.168.1.0/24**.
115123
11. Accept the other default settings, and then select **Create**.
116124

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+
117133
### Create a public IP address
118134

119135
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.
124140
4. For the name, type **VNet-Onprem-GW-pip**.
125141
5. For the resource group, type **FW-Hybrid-Test**.
126142
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**.
129144

130145
## Configure and deploy the firewall
131146

@@ -141,13 +156,13 @@ Now deploy the firewall into the firewall hub virtual network.
141156
|Resource group |**FW-Hybrid-Test** |
142157
|Name |**AzFW01**|
143158
|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**. |
146161

147162
5. Select **Review + create**.
148163
6. Review the summary, and then select **Create** to create the firewall.
149164

150-
This will take a few minutes to deploy.
165+
This takes a few minutes to deploy.
151166
7. After deployment completes, go to the **FW-Hybrid-Test** resource group, and select the **AzFW01** firewall.
152167
8. Note the private IP address. You'll use it later when you create the default route.
153168

@@ -225,7 +240,7 @@ In this step, you create the connection from the hub virtual network to the on-p
225240
1. Open the **FW-Hybrid-Test** resource group and select the **GW-hub** gateway.
226241
2. Select **Connections** in the left column.
227242
3. Select **Add**.
228-
4. The the connection name, type **hub-to-Onprem**.
243+
4. The the connection name, type **Hub-to-Onprem**.
229244
5. Select **VNet-to-VNet** for **Connection type**.
230245
6. For the **Second virtual network gateway**, select **GW-Onprem**.
231246
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
236251
1. Open the **FW-Hybrid-Test** resource group and select the **GW-Onprem** gateway.
237252
2. Select **Connections** in the left column.
238253
3. Select **Add**.
239-
4. The the connection name, type **OnPrem-to-hub**.
254+
4. The the connection name, type **Onprem-to-Hub**.
240255
5. Select **VNet-to-VNet** for **Connection type**.
241256
6. For the **Second virtual network gateway**, select **GW-hub**.
242257
7. For **Shared key (PSK)**, type **AzureA1b2C3**.
@@ -298,7 +313,7 @@ Next, create a couple routes:
298313

299314
Now associate the route to the subnet.
300315

301-
1. On the **UDR-Hub-Spoke** page, select **Subnets**.
316+
1. On the **UDR-Hub-Spoke - Routes** page, select **Subnets**.
302317
2. Select **Associate**.
303318
3. Select **Choose a virtual network**.
304319
4. Select **VNet-hub**.
@@ -327,7 +342,7 @@ Now create the default route from the spoke subnet.
327342

328343
Now associate the route to the subnet.
329344

330-
1. On the **UDR-DG** page, select **Subnets**.
345+
1. On the **UDR-DG - Routes** page, select **Subnets**.
331346
2. Select **Associate**.
332347
3. Select **Choose a virtual network**.
333348
4. Select **VNet-spoke**.
@@ -345,14 +360,14 @@ Create a virtual machine in the spoke virtual network, running IIS, with no publ
345360
1. From the Azure portal home page, select **Create a resource**.
346361
2. Under **Popular**, select **Windows Server 2016 Datacenter**.
347362
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*.
350365
- **Region** - Same region that you're used previously.
351-
- **User name** -*azureuser*.
352-
- **Password** -*Azure123456!*.
366+
- **User name**: *azureuser*.
367+
- **Password**: *Azure123456!*
353368
4. Select **Next:Disks**.
354369
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**.
356371
7. For **Public IP**, select **None**.
357372
8. For **Public inbound ports**, select **Allow selected ports**, and then select **HTTP (80)**, and **RDP (3389)**
358373
9. Select **Next:Management**.
@@ -361,20 +376,20 @@ Create a virtual machine in the spoke virtual network, running IIS, with no publ
361376

362377
### Install IIS
363378

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**.
365380
2. Run the following command to install IIS on the virtual machine:
366381

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+
```
378393

379394
### Create the on-premises virtual machine
380395

@@ -386,11 +401,11 @@ This is a virtual machine that you use to connect using Remote Desktop to the pu
386401
- **Resource group** - Select existing, and then select **FW-Hybrid-Test**.
387402
- **Virtual machine name** - *VM-Onprem*.
388403
- **Region** - Same region that you're used previously.
389-
- **User name** -*azureuser*.
390-
- **Password** -*Azure123456!*.
404+
- **User name**: *azureuser*.
405+
- **Password**: *Azure123456!*.
391406
4. Select **Next:Disks**.
392407
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**.
394409
7. For **Public inbound ports**, select **Allow selected ports**, and then select **RDP (3389)**
395410
8. Select **Next:Management**.
396411
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
406421
You should get a reply.--->
407422
3. Open a web browser on **VM-Onprem**, and browse to http://\<VM-spoke-01 private IP\>.
408423

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)
410426

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.
412428

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.
414430

415431
So now you've verified that the firewall rules are working:
416432

0 commit comments

Comments
 (0)