Skip to content

Commit c58bea7

Browse files
authored
Update configuration-frontend-ip.md
1 parent ac91dd7 commit c58bea7

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 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/14/2023
8+
ms.date: 06/27/2024
99
ms.author: greglin
1010
---
1111

@@ -38,6 +38,9 @@ A frontend IP address is associated to a *listener*, which checks for incoming r
3838

3939
You can create private and public listeners with the same port number. However, be aware of any network security group (NSG) associated with the Application Gateway subnet. Depending on your NSG's configuration, you might need an allow-inbound rule with **Destination IP addresses** as your application gateway's public and private frontend IPs. When you use the same port, your application gateway changes the **Destination** of the inbound flow to the frontend IPs of your gateway.
4040

41+
> [!NOTE]
42+
> Currently, the use of the same port number for public and private TCP, TLS protocols or IPv6 listeners is not supported.
43+
4144
**Inbound rule**:
4245

4346
- **Source**: According to your requirement

0 commit comments

Comments
 (0)