Update retirement FAQ for Application Gateway V1

Clarified support status and implications for V1 SKU after retirement date, including traffic guarantees and hardware decommissioning. Added note on subnet requirements for V1 and V2 gateways.

Signed-off-by: MJyot <[email protected]>

Author: MJyot

articles/application-gateway/retirement-faq.md

@@ -21,7 +21,7 @@ New Customers won't be allowed to create V1 from 1 July 2023 onwards. However, a
 
 ### What happens to existing Application Gateway V1 after 28 April 2026?
 
-Once the deadline arrives V1 gateways aren't supported. Any V1 SKU resources that are still active are stopped, and force deleted.
+After April 28th 2026, V1 SKU will no longer be supported, and no SLA will be provided for customers using this SKU of Application Gateway. Traffic passing through V1 SKUs after retirement cannot be guaranteed as our teams begin the process of cleaning up and decommissioning the hardware that supported V1 SKUs of Application Gateway. 
 
 ### What is the definition of a new customer on Application Gateway V1 SKU?
 
@@ -96,6 +96,10 @@ No, the Azure PowerShell script only migrates the configuration. Actual traffic
 
 The Azure PowerShell script creates a new v2 gateway with an appropriate size to handle the traffic on your existing v1 gateway. Autoscaling is disabled by default, but you can enable autoscaling when you run the script.
 
+### Can I create an Application Gateway V2 in the same subnet as an existing V1 gateway?
+
+No, V1 and V2 gateways cannot coexist in the same subnet. Each gateway type requires its own dedicated subnet within the virtual network. If you plan to migrate from V1 to V2, you must create a new subnet for the V2 gateway and ensure sufficient IP address space is allocated.
+
 ### I configured my v1 gateway  to send logs to Azure storage. Does the script replicate this configuration for v2 as well?
 
 No, the script doesn't replicate this configuration for v2. You must add the log configuration separately to the migrated v2 gateway.