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/deploy-basic-portal.md
+5-31Lines changed: 5 additions & 31 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 deploy Application Gateway Basic.
5
5
services: application-gateway
6
6
author: mbender-ms
7
7
ms.topic: how-to
8
-
ms.date: 07/11/2025
8
+
ms.date: 02/26/2026
9
9
ms.author: mbender
10
10
ms.service: azure-application-gateway
11
11
ms.custom:
@@ -151,36 +151,6 @@ On the **Configuration** tab, you connect the frontend and backend pool you crea
151
151
152
152
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 can take several minutes for Azure to create the application gateway. Wait until the deployment finishes successfully before moving on to the next section.
153
153
154
-
## Deploy Azure Bastion
155
-
156
-
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).
1. In the search box at the top of the portal, enter **Bastion**. Select **Bastions** in the search results.
162
-
163
-
1. Select **+ Create**.
164
-
165
-
1. In the **Basics** tab of **Create a Bastion**, enter, or select the following information:
166
-
167
-
| Setting | Value |
168
-
|---|---|
169
-
|**Project details**||
170
-
| Subscription | Select your subscription. |
171
-
| Resource group | Select **myResourceGroup**. |
172
-
|**Instance details**||
173
-
| Name | Enter **myBastionHost**. |
174
-
| Region | Select the same region as your application gateway. |
175
-
| Tier | Select **Developer**. |
176
-
|**Configure virtual networks**||
177
-
| Virtual network | Select **myVNet**. |
178
-
| Subnet | The **AzureBastionSubnet** is created automatically with an address space of **/26** or larger. |
179
-
180
-
1. Select **Review + create**.
181
-
182
-
1. Select **Create**.
183
-
184
154
## Add backend targets
185
155
186
156
In this example, you use virtual machines as the target backend. You can either use existing virtual machines or create new ones. You create two virtual machines as backend servers for the application gateway.
@@ -203,6 +173,10 @@ To do this:
203
173
-**Username**: Type a name for the administrator user name.
204
174
-**Password**: Type a password.
205
175
-**Public inbound ports**: None.
176
+
177
+
> [!NOTE]
178
+
> 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).
179
+
206
180
4. Accept the other defaults and then select **Next: Disks**.
207
181
5. Accept the **Disks** tab defaults and then select **Next: Networking**.
208
182
6. On the **Networking** tab, verify that **myVNet** is selected for the **Virtual network** and the **Subnet** is set to **myBackendSubnet**. Verify that **Public IP** is set 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's in, but you need to ensure there's IP connectivity.
0 commit comments