Skip to content

Commit a255eb9

Browse files
committed
docs: Replace Bastion deployment with NSG note and remove public IP
1 parent d4abbec commit a255eb9

1 file changed

Lines changed: 5 additions & 31 deletions

File tree

articles/application-gateway/create-ssl-portal.md

Lines changed: 5 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: mbender-ms
66
ms.service: azure-application-gateway
77
ms.topic: tutorial
8-
ms.date: 07/11/2025
8+
ms.date: 02/26/2026
99
ms.author: mbender
1010
ms.custom: sfi-image-nochange
1111
#Customer intent: As an IT administrator, I want to use the Azure portal to configure Application Gateway with TLS termination so I can secure my application traffic.
@@ -21,7 +21,6 @@ In this tutorial, you learn how to:
2121
> [!div class="checklist"]
2222
> * Create a self-signed certificate
2323
> * Create an application gateway with the certificate
24-
> * Deploy Azure Bastion for secure VM connectivity
2524
> * Create the virtual machines used as backend servers
2625
> * Test the application gateway
2726
@@ -174,35 +173,6 @@ On the **Configuration** tab, you'll connect the frontend and backend pool you c
174173

175174
Review the settings on the **Review + create** tab, and then select **Create** to create the virtual network, the public IP address, and the application gateway. It may take several minutes for Azure to create the application gateway. Wait until the deployment finishes successfully before moving on to the next section.
176175

177-
## Deploy Azure Bastion
178-
179-
Azure Bastion uses your browser to connect to VMs in your virtual network over secure shell (SSH) or 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).
180-
181-
>[!NOTE]
182-
>[!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
183-
184-
1. In the search box at the top of the portal, enter **Bastion**. Select **Bastions** in the search results.
185-
186-
1. Select **+ Create**.
187-
188-
1. In the **Basics** tab of **Create a Bastion**, enter or select the following information:
189-
190-
| Setting | Value |
191-
|---|---|
192-
| **Project details** | |
193-
| Subscription | Select your subscription. |
194-
| Resource group | Select **myResourceGroupAG**. |
195-
| **Instance details** | |
196-
| Name | Enter **myBastionHost**. |
197-
| Region | Select the same region as your application gateway. |
198-
| Tier | Select **Developer**. |
199-
| **Configure virtual networks** | |
200-
| Virtual network | Select **myVNet**. |
201-
202-
1. Select **Review + create**.
203-
204-
1. Select **Create**.
205-
206176
## Add backend targets
207177

208178
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 that Azure uses as backend servers for the application gateway.
@@ -228,6 +198,10 @@ To do this, you'll:
228198
- **Username**: Enter a name for the administrator user name.
229199
- **Password**: Enter a password for the administrator account.
230200
- **Public inbound ports**: Select **None**.
201+
202+
> [!NOTE]
203+
> 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).
204+
231205
1. Accept the other defaults and then select **Next: Disks**.
232206
2. Accept the **Disks** tab defaults and then select **Next: Networking**.
233207
3. On the **Networking** tab, verify that **myVNet** is selected for the **Virtual network** and the **Subnet** is set to **myBackendSubnet**. For **Public IP**, select **None**. Accept the other defaults and then select **Next: Management**.

0 commit comments

Comments
 (0)