Skip to content

Commit c34bdde

Browse files
authored
Update application-gateway-troubleshooting-502.md
In Line 44, please update it to this. Adding relevant documentation for app gateway subnet NSG configurations. 1. Check NSGs associated with the application gateway subnet. Ensure that communication to the backend isn't blocked. For more information, please refer to https://learn.microsoft.com/en-us/azure/application-gateway/configuration-infrastructure#network-security-groups
1 parent fce7828 commit c34bdde

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/application-gateway-troubleshooting-502.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Similarly, the presence of a custom DNS in the VNet could also cause issues. An
4141

4242
Validate NSG, UDR, and DNS configuration by going through the following steps:
4343

44-
1. Check NSGs associated with the application gateway subnet. Ensure that communication to backend isn't blocked.
44+
1. Check NSGs associated with the application gateway subnet. Ensure that communication to backend isn't blocked. For more information, please refer to(/azure/application-gateway/configuration-infrastructure#network-security-groups)
4545
2. Check UDR associated with the application gateway subnet. Ensure that the UDR isn't directing traffic away from the backend subnet. For example, check for routing to network virtual appliances or default routes being advertised to the application gateway subnet via ExpressRoute/VPN.
4646

4747
```azurepowershell

0 commit comments

Comments
 (0)