Skip to content

Commit 238f024

Browse files
committed
revert gh issue 119523
1 parent f103d14 commit 238f024

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,30 @@
11
---
22
title: Configure an internal load balancer (ILB) endpoint
33
titleSuffix: Azure Application Gateway
4-
description: This article provides information on how to configure Application Gateway Standard v2 with a private frontend IP address
4+
description: This article provides information on how to configure Application Gateway Standard v1 with a private frontend IP address
55
services: application-gateway
66
author: greg-lindsay
77
ms.service: application-gateway
88
ms.topic: how-to
9-
ms.date: 02/07/2024
9+
ms.date: 08/09/2024
1010
ms.author: greglin
1111
---
1212

1313
# Configure an application gateway with an internal load balancer (ILB) endpoint
1414

15-
Azure Application Gateway Standard v2 can be configured with an Internet-facing VIP or with an internal endpoint that isn't exposed to the Internet. An internal endpoint uses a private IP address for the frontend, which is also known as an *internal load balancer (ILB) endpoint*.
15+
Azure Application Gateway Standard v1 can be configured with an Internet-facing VIP or with an internal endpoint that isn't exposed to the Internet. An internal endpoint uses a private IP address for the frontend, which is also known as an *internal load balancer (ILB) endpoint*.
16+
17+
> [!NOTE]
18+
> Application Gateway v1 is being retired. See the [v1 retiredment announcement](/azure/application-gateway/v1-retirement).<br>
19+
> To configure a v2 application gateway with a private frontend IP address, see [Private Application Gateway deployment](/azure/application-gateway/application-gateway-private-deployment)
1620
1721
Configuring the gateway using a frontend private IP address is useful for internal line-of-business applications that aren't exposed to the Internet. It's also useful for services and tiers within a multi-tier application that are in a security boundary that isn't exposed to the Internet but:
1822

1923
- still require round-robin load distribution
2024
- session stickiness
2125
- or Transport Layer Security (TLS) termination (previously known as Secure Sockets Layer (SSL)).
2226

23-
This article guides you through the steps to configure a Standard v2 Application Gateway with an ILB using the Azure portal.
27+
This article guides you through the steps to configure a Standard v1 Application Gateway with an ILB using the Azure portal.
2428

2529
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
2630

@@ -38,7 +42,7 @@ In this example, you create a new virtual network. You can create a virtual netw
3842
2. Select **Networking** and then select **Application Gateway** in the Featured list.
3943
3. Enter *myAppGateway* for the name of the application gateway and *myResourceGroupAG* for the new resource group.
4044
4. For **Region**, select **Central US**.
41-
5. For **Tier**, select **Standard V2**.
45+
5. For **Tier**, select **Standard**.
4246
6. Under **Configure virtual network** select **Create new**, and then enter these values for the virtual network:
4347
- *myVNet* - for the name of the virtual network.
4448
- *10.0.0.0/16* - for the virtual network address space.

0 commit comments

Comments
 (0)