Merge pull request #303853 from seligj95/patch-5

App Service inbound ipv6 GA

Author: prmerger-automator[bot]

articles/app-service/overview-inbound-outbound-ips.md

@@ -4,7 +4,7 @@ description: Learn how inbound and outbound IP addresses are used in Azure App S
 author: msangapu-msft
 ms.author: msangapu
 ms.topic: article
-ms.date: 07/16/2025
+ms.date: 08/05/2025
 ms.update-cycle: 1095-days
 ms.custom:
   - UpdateFrequency3
@@ -111,12 +111,12 @@ The tag can be used to allow outbound traffic in a Network security group (NSG)
 > [!NOTE]
 > Service tag helps you define network access, but it shouldn't be considered as a replacement for proper network security measures as it doesn't provide granular control over individual IP addresses.
 
-## Inbound IPv6 support (public preview)
+## Inbound IPv6 support
 
-Azure App Service supports IPv6 for inbound traffic. Apps can receive traffic over both IPv4 and IPv6 protocols, providing compatibility with modern networks and clients that require IPv6 connectivity.
+Azure App Service supports IPv6 for inbound traffic on all Basic, Standard, and Premium SKUs, as well as Functions Consumption, Functions Elastic Premium, and Logic Apps Standard plans. Apps can receive traffic over both IPv4 and IPv6 protocols, providing compatibility with modern networks and clients that require IPv6 connectivity.
 
 > [!NOTE]
-> Inbound IPv6 support is in public preview. Outbound IPv6 support is in public preview just for Windows apps. For more information on outbound IPv6 support, see [Announcing App Service Outbound IPv6 Support in Public Preview](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-app-service-outbound-ipv6-support-in-public-preview/4423368). All outbound connections from your Linux apps still use IPv4.
+> Outbound IPv6 support is in public preview just for Windows apps. For more information on outbound IPv6 support, see [Announcing App Service Outbound IPv6 Support in Public Preview](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-app-service-outbound-ipv6-support-in-public-preview/4423368). All outbound connections from your Linux apps still use IPv4.
 
 ### Prerequisites
 
@@ -209,16 +209,6 @@ When using custom domains, you can configure DNS records to support IPv6:
 - **IPv6 only**: Add an AAAA record pointing to your app's IPv6 address. Clients must support IPv6.
 - **Dual-stack**: Add both A (IPv4) and AAAA (IPv6) records, or use a CNAME record to the default hostname, which inherits the `IPMode` behavior.
 
-### IPv6 considerations
-
-Consider the following factors when implementing IPv6 support:
-
-- **Compatibility**: Use `IPv4AndIPv6` mode for maximum client compatibility
-- **Testing**: Verify that your network infrastructure and test environments support IPv6
-- **Client support**: Ensure your application clients can handle IPv6 addresses
-- **Outbound traffic**: Remember that outbound connections always use IPv4
-- **Client testing**: To ensure propert functionality, test your application with both IPv4 and IPv6 clients
-
 ## Next steps
 
 * Learn how to [restrict inbound traffic](./app-service-ip-restrictions.md) by source IP addresses.