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/configure-application-gateway-with-private-frontend-ip.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Azure Application Gateway Standard v1 can be configured with an Internet-facing
16
16
17
17
> [!NOTE]
18
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)
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).
20
20
21
21
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:
22
22
@@ -63,7 +63,7 @@ In this example, you create a new virtual network. You can create a virtual netw
63
63
9. Select **Next:Backends**.
64
64
10. Select **Add a backend pool**.
65
65
11. For **Name**, type *appGatewayBackendPool*.
66
-
12. For **Add backend pool without targets**, select **Yes**. You'll add the targets later.
66
+
12. For **Add backend pool without targets**, select **Yes**. Targets are added later.
67
67
13. Select **Add**.
68
68
14. Select **Next:Configuration**.
69
69
15. Under **Routing rules**, select **Add a routing rule**.
@@ -84,9 +84,9 @@ In this example, you create a new virtual network. You can create a virtual netw
84
84
85
85
## Add backend pool
86
86
87
-
The backend pool is used to route requests to the backend servers that serve the request. The backend can be composed of NICs, virtual machine scale sets, public IP addresses, internal IP addresses, fully qualified domain names (FQDN), and multi-tenant backends like Azure App Service. In this example, you use virtual machines as the target backend. You can either use existing virtual machines or create new ones. In this example, you create two virtual machines that Azure uses as backend servers for the application gateway.
87
+
The backend pool is used to route requests to the backend servers that serve the request. The backend can be composed of NICs, virtual machine scale sets, public IP addresses, internal IP addresses, fully qualified domain names (FQDN), and multitenant backends like Azure App Service. In this example, you use virtual machines as the target backend. You can either use existing virtual machines or create new ones. In this example, you create two virtual machines that Azure uses as backend servers for the application gateway.
88
88
89
-
To do this, you:
89
+
To do this:
90
90
91
91
1. Create two new virtual machines, *myVM* and *myVM2*, used as backend servers.
92
92
2. Install IIS on the virtual machines to verify that the application gateway was created successfully.
0 commit comments