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/app-service/environment/integrate-with-application-gateway.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,15 +42,15 @@ For details on how to create an ILB App Service Environment, see [Create an App
42
42
43
43
* After ILB App Service Environment is created, the default domain is `<YourAseName>.appserviceenvironment.net`.
44
44
45
-
:::image type="content" source="./media/integrate-with-application-gateway/ilb-ase.png" alt-text="Screenshot of ILB App Service Environment Overview":::
45
+
:::image type="content" source="./media/integrate-with-application-gateway/ilb-ase.png" alt-text="Screenshot of ILB App Service Environment Overview.":::
46
46
47
47
* An internal load balancer is provisioned for inbound access. You can check the Inbound address in the IP addresses under App Service Environment Settings. You can create a private DNS zone mapped to this IP address later.
48
48
49
49
:::image type="content" source="./media/integrate-with-application-gateway/ip-addresses.png" alt-text="Screenshot of getting the inbound address from ILB App Service Environment IP addresses settings.":::
50
50
51
51
### A private DNS zone
52
52
53
-
You need a [private DNS zone](../../dns/private-dns-overview.md)for internal name resolution. Create it using the App Service Environment name using the record sets shown in the following table (for instructions, see [Quickstart - Create an Azure private DNS zone using the Azure portal](../../dns/private-dns-getstarted-portal.md)).
53
+
You need a [private DNS zone](../../dns/private-dns-overview.md)for internal name resolution. Create it using the App Service Environment name using the record sets shown in the following table (for instructions, see [Quickstart - Create an Azure private DNS zone using the Azure portal](../../dns/private-dns-getstarted-portal.md)).
54
54
55
55
| Name | Type | Value |
56
56
| ----- | ---- | ------------------- |
@@ -128,7 +128,7 @@ In the Azure portal, select **New** > **Network** > **Application Gateway** to c
128
128
129
129
:::image type="content" source="./media/integrate-with-application-gateway/http-routing-rule.png" alt-text="Screenshot of HTTP Listener of the application gateway Routing Rule.":::
130
130
131
-
* To connect to the application gateway with TLS encryption, you can create a listener with following settings,
131
+
* To connect to the application gateway with TLS encryption, you can create a listener with following settings:
@@ -20,7 +20,7 @@ This article walks through how to configure Application Gateway with App Service
20
20
21
21
You can use private endpoints to secure traffic between Application Gateway and your App Service app. You need to ensure that Application Gateway can use DNS to resolve the private IP address of the App Service apps. Alternatively, you can use the private IP address in the back-end pool and override the host name in the HTTP settings.
22
22
23
-
:::image type="content" source="./media/overview-app-gateway-integration/private-endpoint-appgw.png" alt-text="Diagram that shows traffic flowing to an application gateway in an Azure virtual network and then flowing through a private endpoint to instances of apps in App Service.":::
23
+
:::image type="content" source="./media/overview-app-gateway-integration/private-endpoint-appgw.png" alt-text="Diagram that shows traffic flowing to an application gateway through a private endpoint to instances of apps in App Service.":::
24
24
25
25
Application Gateway caches the DNS lookup results. If you use fully qualified domain names (FQDNs) and rely on DNS lookup to get the private IP address, you might need to restart the application gateway if the DNS update or the link to an Azure private DNS zone happened after you configured the back-end pool.
0 commit comments