Skip to content

Commit ec6051f

Browse files
committed
docs: Replace Bastion deployment with NSG note and remove public IP
1 parent 15edd2e commit ec6051f

1 file changed

Lines changed: 5 additions & 31 deletions

File tree

articles/application-gateway/tutorial-protect-application-gateway-ddos.md

Lines changed: 5 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to set up an application gateway and protect it with Azur
55
services: application-gateway
66
author: duongau
77
ms.author: duau
8-
ms.date: 07/11/2025
8+
ms.date: 02/26/2026
99
ms.topic: quickstart
1010
ms.service: azure-application-gateway
1111
ms.custom: sfi-image-nochange
@@ -27,7 +27,6 @@ In this tutorial, you learn how to:
2727
> * Create a DDoS protection plan
2828
> * Create an application gateway
2929
> * Associate a DDoS Protection plan to the virtual network
30-
> * Deploy Azure Bastion
3130
> * Add VMs to the backend of the application gateway
3231
> * Test the application gateway
3332
@@ -178,35 +177,6 @@ Azure DDoS Network Protection is enabled at the virtual network where the resour
178177

179178
6. Select **Save**.
180179

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).
184-
185-
>[!NOTE]
186-
>[!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
187-
188-
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-
210180
## Add backend targets
211181

212182
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.
@@ -229,6 +199,10 @@ To do this, you'll:
229199
- **Username**: Type a name for the administrator user name.
230200
- **Password**: Type a password.
231201
- **Public inbound ports**: None.
202+
203+
> [!NOTE]
204+
> The default rules of the network security group block all inbound access from the internet, including RDP. To connect to the virtual machine, use Azure Bastion. For more information, see [Quickstart: Deploy Azure Bastion with default settings](../bastion/quickstart-host-portal.md).
205+
232206
4. Accept the other defaults and then select **Next: Disks**.
233207
5. Accept the **Disks** tab defaults and then select **Next: Networking**.
234208
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.

0 commit comments

Comments
 (0)