You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update Firewall hybrid network tutorial to use curl-only testing
- Updated article date to 01/27/2026
- Removed SSH network rule (AllowSSH) from firewall configuration
- Changed virtual machine description from IIS to NGINX
- Simplified testing procedure to use curl only (removed SSH connection test)
- Fixed plural 'virtual machines' to singular 'virtual machine' in learning objectives
- Streamlined verification steps to focus on web traffic testing
AB#544783
Copy file name to clipboardExpand all lines: articles/firewall/tutorial-hybrid-portal-policy.md
+3-27Lines changed: 3 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: firewall
5
5
author: duau
6
6
ms.service: azure-firewall
7
7
ms.topic: tutorial
8
-
ms.date: 08/05/2024
8
+
ms.date: 01/27/2026
9
9
ms.author: duau
10
10
ms.custom: sfi-image-nochange
11
11
#Customer intent: As an administrator, I want to control network access from an on-premises network to an Azure virtual network.
@@ -36,7 +36,7 @@ In this tutorial, you learn how to:
36
36
> * Create and connect the VPN gateways
37
37
> * Peer the hub and spoke virtual networks
38
38
> * Create the routes
39
-
> * Create the virtual machines
39
+
> * Create the virtual machine
40
40
> * Test the firewall
41
41
42
42
If you want to use Azure PowerShell instead to complete this procedure, see [Deploy and configure Azure Firewall in a hybrid network using Azure PowerShell](tutorial-hybrid-ps.md).
@@ -190,19 +190,6 @@ First, add a network rule to allow web traffic.
190
190
1. For **Destination type**, select **IP address**.
191
191
1. For **Destination**, type **10.6.0.0/16**.
192
192
193
-
Now add a rule to allow SSH traffic.
194
-
195
-
On the second rule row, type the following information:
196
-
197
-
1.**Name**, type **AllowSSH**.
198
-
3. For **Source type**, select **IP address**.
199
-
4. For **Source**, type **192.168.1.0/24**.
200
-
2. For **Protocol**, select **TCP**.
201
-
1. For **Destination Ports**, type **22**.
202
-
1. For **Destination type**, select **IP address**.
203
-
1. For **Destination**, type **10.6.0.0/16**
204
-
1. Select **Add**.
205
-
206
193
## Create and connect the VPN gateways
207
194
208
195
The hub and on-premises virtual networks are connected via VPN gateways.
@@ -386,7 +373,7 @@ Now create the spoke workload and on-premises virtual machines, and place them i
386
373
387
374
### Create the workload virtual machine
388
375
389
-
Create a virtual machine in the spoke virtual network, running IIS, with no public IP address.
376
+
Create a virtual machine in the spoke virtual network, running NGINX, with no public IP address.
390
377
391
378
1. From the Azure portal home page, select **Create a resource**.
392
379
2. Under **Popular Marketplace products**, select **Ubuntu Server 22.04 LTS**.
@@ -511,20 +498,9 @@ Now deploy Azure Bastion in the hub virtual network to provide secure access to
511
498
curl http://<VM-spoke-01 private IP>
512
499
```
513
500
514
-
You should see the **VM-spoke-01** web page with the hostname displayed.
515
-
516
-
9. From the **VM-Onprem** SSH session, connect to **VM-spoke-01** using SSH:
517
-
518
-
```bash
519
-
ssh azureuser@<VM-spoke-01 private IP>
520
-
```
521
-
522
-
Your connection should succeed, and you should see a login prompt. Type **exit** to close the SSH connection.
523
-
524
501
So now you verified that the firewall rules are working:
525
502
526
503
- You can browse the web server on the spoke virtual network.
527
-
- You can connect to the server on the spoke virtual network using SSH.
528
504
529
505
Next, change the firewall network rule collection action to **Deny** to verify that the firewall rules work as expected.
0 commit comments