Merge pull request #299562 from radwiv/IPv6

New Article

Author: JillGrant615

articles/vpn-gateway/TOC.yml

@@ -76,6 +76,8 @@
     href: about-zone-redundant-vnet-gateways.md
   - name: VPN Gateway configuration settings
     href: vpn-gateway-about-vpn-gateway-settings.md
+  - name: IPv6 configuration settings
+    href: ipv6-configuration.md
 - name: Create & manage a VPN gateway
   items:
   - name: Create a VPN gateway

articles/vpn-gateway/ipv6-configuration.md

@@ -0,0 +1,66 @@
+---
+title: Configure IPv6 in dual stack
+titleSuffix: Azure VPN Gateway
+description: Learn how to configure IPv6 in dual stack for VPN Gateway.
+author: radwiv
+ms.service: azure-vpn-gateway
+ms.topic: how-to
+ms.date: 05/02/2025
+ms.author: radwiv
+---
+
+# Configure IPv6 for VPN Gateway - Preview
+
+You can use IPv6 in a dual-stack configuration for Azure VPN Gateway. This configuration allows seamless IPv6 traffic traversal within the VPN tunnel when connecting from on-premises or remote user devices to Azure VPN Gateway.
+
+This article helps you configure IPv6 in dual stack for VPN Gateway using the Azure portal. Configuration steps are similar to the existing IPv4 configuration. You can also use PowerShell, or CLI for this configuration. If you use PowerShell or CLI, you can configure IPv6 addresses along with IPv4 addresses.
+
+> [!IMPORTANT]
+> IPv6 in dual stack configuration is currently in PREVIEW.
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+## Prerequisites
+
+During Preview, you can opt in to configure IPv6 in dual stack. To opt in, send your subscription ID to **[email protected]** and request your subscription to be enabled for IPv6.
+
+## Configure using the Azure portal
+
+When you deploy VPN Gateway with IPv6 in dual stack mode, you can use the same steps as you would for an IPv4 deployment, but with IPv6 addresses. The following steps show how to configure IPv6 in dual stack mode using the Azure portal.
+
+1. Create a virtual network with IPv4 and IPv6 address ranges.
+
+   :::image type="content" source="./media/ipv6-configuration/vnet-ipv6.png" alt-text="Diagram shows IPv6 configuration for Virtual Network." lightbox="./media/ipv6-configuration/vnet-ipv6.png":::
+
+1. Create the gateway subnet with IPv4 and IPv6 address ranges.
+
+   :::image type="content" source="./media/ipv6-configuration/gateway-subnet-ipv6.png" alt-text="Diagram shows IPv6 configuration for Virtual Network." lightbox="./media/ipv6-configuration/gateway-subnet-ipv6.png":::
+
+1. Create the virtual network gateway and local network gateway using IPv6 configurations.
+
+   **Virtual network gateway**
+
+   :::image type="content" source="./media/ipv6-configuration/vng-vpn-config.png" alt-text="Diagram shows IPv6 configuration for Virtual Network." lightbox="./media/ipv6-configuration/vng-vpn-config.png":::
+
+   **Local network gateway**
+
+   :::image type="content" source="./media/ipv6-configuration/lng-vpn-ipv6-config.png" alt-text="Diagram shows IPv6 configuration for Virtual Network." lightbox="./media/ipv6-configuration/lng-vpn-ipv6-config.png":::
+
+    **Address pool**
+
+   :::image type="content" source="./media/ipv6-configuration/vng-vpn-p2s-ipv6-config.png" alt-text="Diagram shows IPv6 configuration for Virtual Network." lightbox="./media/ipv6-configuration/vng-vpn-p2s-ipv6-config.png":::
+
+## Limitations
+
+The following limitations apply to IPv6 in dual stack configuration for VPN Gateway:
+
+* IPv6 support is available for new gateway deployments using VpnGw1-5 and VpnGw1AZ-5AZ SKUs.
+* A VPN gateway deployed in IPv6 dual stack mode can't be moved to an IPv4 only configuration.
+* IPv6 can be used with IPv4 in dual stack mode to set up VPN Gateway connectivity.
+* Point-to-Site VPN gateways using IKEv2 and OpenVPN protocols support IPv6. Point-to-Site VPN gateways don't support IPv6 when using IKEv1 and SSTP protocols.
+* Currently IPv6 for VPN in Virtual WAN isn't supported.
+* Currently User Defined Routes (UDR) with IPv6 using a virtual network gateway VPN as the next hop aren't supported.
+* IPv6 support is available for inner traffic only. Currently, support for IPv6 in the outer VPN tunnel isn't available.
+
+## Next steps
+
+For more information about VPN Gateway, see the [VPN Gateway FAQ](vpn-gateway-vpn-faq.md).

articles/vpn-gateway/media/ipv6-configuration/gateway-subnet-ipv6.png

@@ -4,7 +4,7 @@ description: Get answers to frequently asked questions about VPN Gateway connect
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 03/31/2025
+ms.date: 05/09/2025
 ms.author: cherylmc
 ---
 
@@ -166,6 +166,10 @@ Yes. You can use the Set Pre-Shared Key REST API and PowerShell cmdlet to config
 
 You're limited to using preshared keys for authentication.
 
+### Does Azure VPN Gateway support IPv6?
+
+Yes. For additional information see [Configure IPv6 for VPN Gateway](ipv6-configuration.md).
+
 ### How do I specify which traffic goes through the VPN gateway?
 
 For the Azure Resource Manager deployment model:

articles/vpn-gateway/media/ipv6-configuration/lng-vpn-ipv6-config.png

@@ -4,7 +4,7 @@ description: Learn what's new with Azure VPN Gateway such as the latest release
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 02/18/2025
+ms.date: 05/08/2025
 ms.author: cherylmc
 ---
 
@@ -26,11 +26,11 @@ You can also find the latest VPN Gateway updates and subscribe to the RSS feed [
 > [!NOTE]
 > Timelines are subject to change.
 
-| Event | Customer impact| Anticipated timelines | Customer action/ prerequisites | Documentation | Annoucement Links |
+| Event | Customer impact| Anticipated timelines | Customer action/ prerequisites | Documentation | Announcement Links |
 |---|---|---|---|---|---|
 |Basic SKU public IP address migration - For all VPN SKU's except Basic SKU Gateway |- New [pricing changes](https://azure.microsoft.com/pricing/details/ip-addresses/).<br>- To qualify for successful migration, ensure you have the right IP address space and subnet size.<br>- Up to 10 minutes of downtime is expected during customer-controlled migration.<br>- Customers will have 3 months to migrate after the release of the migration tool.|- **Apr/May 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for for active-passive gateways.<br>- **Jul/Aug 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for for active-active gateways.<br>- **May 2025 to Sep 2025**: Customer-controlled migration can be initiated after tool availability.<br>- **Sep 2025**: Basic SKU public IP addresses are deprecated.  |- Ensure you have the right IP address space and subnet size, check here.<br>- If your VPN gateway is using a Basic SKU public IP address, migrate it to a Standard SKU public IP address.<br> - If your VPN gateway is already using a Standard SKU public IP address, no action is required.|Available when the migration tool is released. |[Basic SKU public IP address retirement](https://azure.microsoft.com/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired) |
 |Basic SKU public IP address migration - For Basic SKU Gateway | Impact details to be updated by **May 15, 2025** | Migration plan for Basic IP address for Basic Gateway SKU’s will be published by **May 15, 2025** | Customer action to be updated by **May 15, 2025** | Available when the migration details are released | [Basic SKU public IP address retirement](https://azure.microsoft.com/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired) |
-|Non-AZ gateway SKU retirement |- New pricing for AZ gateway SKUs applied since Jan 2025.<br>- Non-AZ gateway SKUs will be migrated to AZ gateway SKUs with no downtime expected.<br>- Non-AZ gateway SKU creates to be blocked by May 2025. |- **Jan 2025**: New pricing for AZ gatway SKUs activated.<br> - **May 2025 to Sep 2026**: Non-AZ gateway SKU-to-AZ gateway SKU migration available.<br> - **Sep 2026**: Non-AZ gateway SKU retirement.|- If the VPN gateway is using a Basic public IP address SKU, migrate it to a Standard public IP address SKU.|[VPN Gateway SKU consolidation and migration](gateway-sku-consolidation.md)| [Non-AZ gateway SKU retirement](https://azure.microsoft.com/updates?id=vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026)|
+|Non-AZ gateway SKU retirement |- New pricing for AZ gateway SKUs applied since Jan 2025.<br>- Non-AZ gateway SKUs will be migrated to AZ gateway SKUs with no downtime expected.<br>- Non-AZ gateway SKU creates to be blocked by May 2025. |- **Jan 2025**: New pricing for AZ gateway SKUs activated.<br> - **May 2025 to Sep 2026**: Non-AZ gateway SKU-to-AZ gateway SKU migration available.<br> - **Sep 2026**: Non-AZ gateway SKU retirement.|- If the VPN gateway is using a Basic public IP address SKU, migrate it to a Standard public IP address SKU.|[VPN Gateway SKU consolidation and migration](gateway-sku-consolidation.md)| [Non-AZ gateway SKU retirement](https://azure.microsoft.com/updates?id=vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026)|
 |Gateway SKU retirement: Standard and High Performance SKUs.|- New Standard/High Perf SKU gateway creations blocked Nov 2023.<br> - Standard/High Perf SKU gateways will be migrated to VpnGw1/VpnGw2.<br> - No downtime is expected for migration.|- **May 2025 to Sep 2025**: Standard/HighPerf SKU migration.<br>- **Sep 2025**: Standard/HighPerf SKU retirement.| - No action required|[Working with VPN Gateway legacy SKUs](vpn-gateway-about-skus-legacy.md)|[Standard and HighPerf gateway SKU retirement](https://azure.microsoft.com/updates?id=standard-and-highperformance-vpn-gateway-skus-will-be-retired-on-30-september-2025)|
 |Classic VPN gateways retired|- Classic VPN gateways will be decommissioned.|- **Aug 2024**: Retirement<br>- **By Aug 2025**: Decommission|- Migrate your classic VPN gateway to an Azure Resource Manager gateway|[VPN Gateway classic to Resource Manager migration](vpn-gateway-classic-resource-manager-migration.md)|[Classic resource retirement](https://azure.microsoft.com/updates?id=cloud-services-retirement-announcement)|
 
@@ -39,7 +39,8 @@ You can also find the latest VPN Gateway updates and subscribe to the RSS feed [
 
 | Type | Area | Name | Description | Date added | Limitations |
 |---|---|---|---|---|---|
-|SKU Consolidation | N/A | [VpnGw1-5 non-AZ VPN Gateway SKU](gateway-sku-consolidation.md) | VpnGw1-5 non-AZ SKU will be deprecated on 30 Sep 2026. View the announcement [here](https://azure.microsoft.com/updates/v2/vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026) | Sep 2024 | N/A
+|IPv6 Preview | N/A | [VPN Gateway IPv6](ipv6-configuration.md) | Azure VPN Gateway supports IPv6 in dual stack. View the announcement [here](https://aka.ms/vpnipv6preview) | May 2025 | N/A |
+|SKU Consolidation | N/A | [VpnGw1-5 non-AZ VPN Gateway SKU](gateway-sku-consolidation.md) | VpnGw1-5 non-AZ SKU will be deprecated on 30 Sep 2026. View the announcement [here](https://azure.microsoft.com/updates/v2/vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026) | Sep 2024 | N/A |
 | P2S VPN | P2S | [Azure VPN Client for Linux](#linux)| [Certificate](point-to-site-certificate-client-linux-azure-vpn-client.md) authentication, [Microsoft Entra ID ](point-to-site-entra-vpn-client-linux.md) authentication.| May 2024 | N/A|
 | P2S VPN | P2S | [Azure VPN Client for macOS](#macos) | Microsoft Entra ID authentication updates, additional features.  | Sept 2024 | N/A|
 | P2S VPN | P2S | [Azure VPN Client for Windows](#windows) | Microsoft Entra ID authentication updates, additional features.  | May 2024 | N/A|