Merge pull request #257561 from jaesoni/same-port-ga

Same port ga

Author: v-dirichards

articles/application-gateway/application-gateway-faq.yml

@@ -270,7 +270,7 @@ sections:
           
       - question: Can I use the same port for both public-facing and private-facing listeners?
         answer: |
-          Yes, you can use public-facing and private-facing listeners with the same port number to simultaneously support both public and private clients (feature in Preview). Note that if a Network Security Group (NSG) is associated with your application gateway's subnet, a specific Inbound rule may be needed depending on its configuration. [Know more](./configuration-listeners.md#frontend-port).
+          Yes, you can use public-facing and private-facing listeners with the same port number to simultaneously support both public and private clients. Note that if a Network Security Group (NSG) is associated with your application gateway's subnet, a specific Inbound rule may be needed depending on its configuration. [Know more](./configuration-listeners.md#frontend-port).
 
       - question: Does Application Gateway support IPv6?
         answer: Application Gateway v2 supports IPv4 and IPv6  frontends (Public Preview). Currently, IPv6 support is available for new Application Gateways only. To support IPv6, VNet should be dual stack. Application Gateway v1 doesn't support dual stack VNets. 

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

@@ -39,7 +39,7 @@ Only one public IP address and one private IP address is supported. You choose t
 A frontend IP address is associated to a *listener*, which checks for incoming requests on the frontend IP.
 
 >[!NOTE] 
-> 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 allow-inbound rule with **Destination IP addresses** as your application gateway's Public and Private frontend IPs. When using the same port, your application gateway changes the "Destination" of the inbound flow to the frontend IPs of your gateway.
+> 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 may need an allow-inbound rule with **Destination IP addresses** as your application gateway's Public and Private frontend IPs. When using the same port, your application gateway changes the "Destination" of the inbound flow to the frontend IPs of your gateway.
 > 
 > **Inbound Rule**:
 > - Source: (as per your requirement)

articles/application-gateway/configuration-infrastructure.md

@@ -119,7 +119,7 @@ To use NSG with your application gateway, you will need to create or retain some
 |---|---|---|---|---|---|
 |`<as per need>`|Any|`<Subnet IP Prefix>`|`<listener ports>`|TCP|Allow|
 
-Upon configuring **active public and private listeners** (with Rules) **with the same port number** (in Preview), your application gateway changes the "Destination" of all inbound flows to the frontend IPs of your gateway. This is true even for the listeners not sharing any port. You must thus include your gateway's frontend Public and Private IP addresses in the Destination of the inbound rule when using the same port configuration.
+Upon configuring **active public and private listeners** (with Rules) **with the same port number**, your application gateway changes the "Destination" of all inbound flows to the frontend IPs of your gateway. This is true even for the listeners not sharing any port. You must thus include your gateway's frontend Public and Private IP addresses in the Destination of the inbound rule when using the same port configuration.
 
 
 | Source  | Source ports | Destination | Destination ports | Protocol | Access |