Skip to content

Commit 51a5e42

Browse files
authored
Update configuration-frontend-ip.md
1 parent 824d4bf commit 51a5e42

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

articles/application-gateway/configuration-frontend-ip.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: greg-lindsay
66
ms.service: application-gateway
77
ms.topic: conceptual
8-
ms.date: 09/09/2020
8+
ms.date: 02/26/2023
99
ms.author: greglin
1010
---
1111

@@ -33,6 +33,17 @@ Only one public IP address and one private IP address is supported. You choose t
3333

3434
A frontend IP address is associated to a *listener*, which checks for incoming requests on the frontend IP.
3535

36+
>[!NOTE]
37+
> You can create private and public listeners with the same port number (Preview feature). However, be aware of any Network Security Group (NSG) associated with the application gateway subnet. Depending on your NSG's configuration, you may need an inbound rule with **Destination IP addresses** as your application gateway's public and private frontend IPs.
38+
>
39+
> **Inbound Rule**:
40+
> - Source: (as per your requirement)
41+
> - Destination IP addresses: Public and Private frontend IPs of your application gateway.
42+
> - Destination Port: (as per listener configuration)
43+
> - Protocol: TCP
44+
>
45+
> **Outbound Rule**: (no specific requirement)
46+
3647
## Next steps
3748

3849
- [Learn about listener configuration](configuration-listeners.md)

0 commit comments

Comments
 (0)