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
Copy file name to clipboardExpand all lines: articles/firewall/tutorial-hybrid-portal.md
+70-48Lines changed: 70 additions & 48 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: how-to
8
-
ms.date: 08/31/2023
8
+
ms.date: 01/28/2026
9
9
ms.author: duau
10
10
#Customer intent: As an administrator, I want to control network access from an on-premises network to an Azure virtual network.
11
11
# Customer intent: As a network administrator, I want to deploy and configure Azure Firewall in a hybrid network, so that I can effectively control and secure access between on-premises and Azure virtual networks.
@@ -187,17 +187,6 @@ First, add a network rule to allow web traffic:
187
187
1. For **Destination Address**, enter **10.6.0.0/16**.
188
188
1. For **Destination Ports**, enter **80**.
189
189
190
-
Now, add a rule to allow RDP traffic. On the second rule row, enter the following information:
191
-
192
-
1. For **Name**, enter **AllowRDP**.
193
-
1. For **Protocol**, select **TCP**.
194
-
1. For **Source type**, select **IP address**.
195
-
1. For **Source**, enter **192.168.0.0/24**.
196
-
1. For **Destination type**, select **IP address**.
197
-
1. For **Destination Address**, enter **10.6.0.0/16**.
198
-
1. For **Destination Ports**, enter **3389**.
199
-
1. Select **Add**.
200
-
201
190
## Create and connect the VPN gateways
202
191
203
192
The hub and on-premises virtual networks are connected via VPN gateways.
@@ -376,17 +365,21 @@ Create the spoke workload and on-premises virtual machines, and place them in th
376
365
377
366
### Create the workload virtual machine
378
367
379
-
Create a virtual machine in the spoke virtual network that runs Internet Information Services (IIS) and has no public IP address:
368
+
Create a virtual machine in the spoke virtual network that runs Nginx web server and has no public IP address:
380
369
381
370
1. On the Azure portal home page, select **Create a resource**.
382
-
1. Under **Popular Marketplace products**, select **Windows Server 2019 Datacenter**.
371
+
1. Under **Popular Marketplace products**, select **Ubuntu Server 22.04 LTS**.
1. Wait for the command to complete. The output displays the hostname of the virtual machine.
405
+
416
406
### Create the on-premises virtual machine
417
407
418
-
Create a virtual machine that you use to connect via remote access to the public IP address. From there, you can connect to the spoke server through the firewall.
408
+
Create a virtual machine that you use to connect via Azure Bastion. From there, you can connect to the spoke server through the firewall.
419
409
420
410
1. On the Azure portal home page, select **Create a resource**.
421
-
1. Under **Popular**, select **Windows Server 2019 Datacenter**.
411
+
1. Under **Popular**, select **Ubuntu Server 22.04 LTS**.
422
412
1. Enter these values for the virtual machine:
423
413
-**Resource group**: Select **Existing**, and then select **RG-fw-hybrid-test**.
424
414
-**Virtual machine name**: Enter **VM-Onprem**.
425
415
-**Region**: Select the same region that you used previously.
426
-
-**User name**: Enter a username.
427
-
-**Password**: Enter a user password.
428
-
1. For **Public inbound ports**, select **Allow selected ports**, and then select **RDP (3389)**.
416
+
-**Image**: Ubuntu Server 22.04 LTS - x64 Gen2
417
+
-**Size**: Standard_B2s
418
+
-**Authentication type**: SSH public key
419
+
-**Username**: **azureuser**
420
+
-**SSH public key source**: Generate new key pair
421
+
-**Key pair name**: **VM-Onprem_key**
422
+
1. For **Public inbound ports**, select **None**.
429
423
1. Select **Next: Disks**.
430
424
1. Accept the defaults and select **Next: Networking**.
431
425
1. For the virtual network, select **VNet-Onprem**. The subnet is **SN-Corp**.
432
426
1. Select **Next: Management**.
433
427
1. Select **Next: Monitoring**.
434
428
1. For **Boot diagnostics**, select **Disable**.
435
429
1. Select **Review+Create**, review the settings on the summary page, and then select **Create**.
430
+
1. On the **Generate new key pair** dialog, select **Download private key and create resource**. Save the key file as **VM-Onprem_key.pem**.
0 commit comments