Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

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

@@ -6,7 +6,7 @@ metadata:
   author: greg-lindsay
   ms.service: application-gateway
   ms.topic: faq
-  ms.date: 08/22/2023
+  ms.date: 11/06/2023
   ms.author: greglin
   ms.custom: references_regions, devx-track-azurepowershell
 title: Frequently asked questions about Application Gateway
@@ -273,7 +273,7 @@ sections:
           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).
 
       - question: Does Application Gateway support IPv6?
-        answer: Application Gateway v2 doesn't currently support IPv6. It can operate in a dual stack VNet using only IPv4, but the gateway subnet must be IPv4-only. Application Gateway v1 doesn't support dual stack VNets. 
+        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. 
 
       - question: Does Application Gateway support FIPS?
         answer: Application Gateway v1 SKUs can run in a FIPS 140-2 approved mode of operation, commonly referred to as "FIPS mode".  FIPS mode calls a FIPS 140-2 validated cryptographic module that ensures FIPS-compliant algorithms for encryption, hashing, and signing when enabled.  To ensure FIPS mode is enabled, the FIPSMode setting must be configured via PowerShell, ARM Template, or REST API once the subscription has been enrolled to enable configuration of FIPSmode.

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

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: conceptual
-ms.date: 02/26/2023
+ms.date: 09/14/2023
 ms.author: greglin
 ---
 
@@ -28,6 +28,10 @@ A public IP address isn't required for an internal endpoint that's not exposed t
 
 Only one public IP address and one private IP address is supported. You choose the frontend IP when you create the application gateway.
 
+  > [!NOTE]
+  > Application Gateway frontend supports dual-stack IP addresses (Public Preview). You can create up to four frontend IPs: Two IPv4 addresses (public and private) and two IPv6 addresses (public and private).
+
+
 - For a public IP address, you can create a new public IP address or use an existing public IP in the same location as the application gateway. For more information, see [static vs. dynamic public IP address](./application-gateway-components.md#static-versus-dynamic-public-ip-address).
 
 - For a private IP address, you can specify a private IP address from the subnet where the application gateway is created. For Application Gateway v2 sku deployments, a static IP address must be defined when adding a private IP address to the gateway.  For Application Gateway v1 sku deployments, if you don't specify an IP address, an available IP address is automatically selected from the subnet. The IP address type that you select (static or dynamic) can't be changed later. For more information, see [Create an application gateway with an internal load balancer](./application-gateway-ilb-arm.md).

articles/application-gateway/configuration-listeners.md

@@ -35,6 +35,10 @@ For the v2 SKU, multi-site listeners are processed before basic listeners, unles
 
 Choose the frontend IP address that you plan to associate with this listener. The listener will listen to incoming requests on this IP.
 
+  > [!NOTE]
+  > Application Gateway frontend supports dual-stack IP addresses (Public Preview). You can create up to four frontend IP addresses: Two IPv4 addresses (public and private) and two IPv6 addresses (public and private).
+
+
 ## Frontend port
 
 Associate a frontend port. You can select an existing port or create a new one. Choose any value from the [allowed range of ports](./application-gateway-components.md#ports). You can use not only well-known ports, such as 80 and 443, but any allowed custom port that's suitable. The same port can be used for public and private listeners (Preview feature).