Skip to content

Commit c855952

Browse files
Merge pull request #310445 from seligj95/aseip
App Service Environment source IP limitation
2 parents 681e8d4 + 4859e7a commit c855952

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

articles/app-service/environment/networking.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,10 @@ You can bring your own inbound address to your App Service Environment. If you c
7878
- For App Service Environment with external VIP, the Azure Public IP address resource must be in the same subscription as the App Service Environment.
7979
- The inbound address can't be changed after the App Service Environment is created.
8080

81+
### ILB App Service Environment inbound traffic limitation
82+
83+
For App Service Environments with an internal VIP, inbound traffic to the front ends can be dropped if the source IP address falls within the infrastructure address range used for the App Service Environment's front ends. **Don't use source IP addresses in the `172.31.192.0/25` address space when connecting to an ILB App Service Environment**.
84+
8185
## Ports and network restrictions
8286

8387
For your app to receive traffic, ensure that inbound network security group (NSG) rules allow the App Service Environment subnet to receive traffic from the required ports. In addition to any ports you'd like to receive traffic on, you should ensure that Azure Load Balancer is able to connect to the subnet on port 80. This port is used for health checks of the internal virtual machine. You can still control port 80 traffic from the virtual network to your subnet.

0 commit comments

Comments
 (0)