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/application-gateway/tutorial-protect-application-gateway-ddos.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn how to set up an application gateway and protect it with Azur
5
5
services: application-gateway
6
6
author: duongau
7
7
ms.author: duau
8
-
ms.date: 09/20/2023
8
+
ms.date: 07/11/2025
9
9
ms.topic: quickstart
10
10
ms.service: azure-application-gateway
11
11
ms.custom: sfi-image-nochange
@@ -27,6 +27,7 @@ In this tutorial, you learn how to:
27
27
> * Create a DDoS protection plan
28
28
> * Create an application gateway
29
29
> * Associate a DDoS Protection plan to the virtual network
30
+
> * Deploy Azure Bastion
30
31
> * Add VMs to the backend of the application gateway
31
32
> * Test the application gateway
32
33
@@ -177,6 +178,35 @@ Azure DDoS Network Protection is enabled at the virtual network where the resour
177
178
178
179
6. Select **Save**.
179
180
181
+
## Deploy Azure Bastion
182
+
183
+
Azure Bastion uses your browser to connect to VMs in your virtual network over remote desktop protocol (RDP) by using their private IP addresses. The VMs don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see [Azure Bastion](/azure/bastion/bastion-overview).
1. In the search box at the top of the portal, enter **Bastion**. Select **Bastions** in the search results.
189
+
190
+
1. Select **+ Create**.
191
+
192
+
1. In the **Basics** tab of **Create a Bastion**, enter, or select the following information:
193
+
194
+
| Setting | Value |
195
+
|---|---|
196
+
|**Project details**||
197
+
| Subscription | Select your subscription. |
198
+
| Resource group | Select **myResourceGroupAG**. |
199
+
|**Instance details**||
200
+
| Name | Enter **myBastionHost**. |
201
+
| Region | Select **Central US**. |
202
+
| Tier | Select **Developer**. |
203
+
|**Configure virtual networks**||
204
+
| Virtual network | Select **myVNet**. |
205
+
206
+
1. Select **Review + create**.
207
+
208
+
1. Select **Create**.
209
+
180
210
## Add backend targets
181
211
182
212
In this example, you'll use virtual machines as the target backend. You can either use existing virtual machines or create new ones. You'll create two virtual machines as backend servers for the application gateway.
@@ -201,7 +231,7 @@ To do this, you'll:
201
231
-**Public inbound ports**: None.
202
232
4. Accept the other defaults and then select **Next: Disks**.
203
233
5. Accept the **Disks** tab defaults and then select **Next: Networking**.
204
-
6. On the **Networking** tab, verify that **myVNet** is selected for the **Virtual network** and the **Subnet** is set to **myBackendSubnet**. Accept the other defaults and then select **Next: Management**.<br>Application Gateway can communicate with instances outside of the virtual network that it is in, but you need to ensure there's IP connectivity.
234
+
6. On the **Networking** tab, verify that **myVNet** is selected for the **Virtual network** and the **Subnet** is set to **myBackendSubnet**. Set **Public IP** to **None**. Accept the other defaults and then select **Next: Management**.<br>Application Gateway can communicate with instances outside of the virtual network that it is in, but you need to ensure there's IP connectivity.
205
235
7. On the **Management** tab, set **Boot diagnostics** to **Disable**. Accept the other defaults and then select **Review + create**.
206
236
8. On the **Review + create** tab, review the settings, correct any validation errors, and then select **Create**.
207
237
9. Wait for the virtual machine creation to complete before continuing.
0 commit comments