Skip to content

Commit d633d47

Browse files
Merge pull request #271533 from rnautiyal/IPv6GAPorta
IPv6 Portal update
2 parents 72da743 + 0f6c7a9 commit d633d47

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/application-gateway/ipv6-application-gateway-portal.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: mvc, mode-ui
1414
# Configure Application Gateway with a frontend public IPv6 address using the Azure portal
1515

1616
> [!IMPORTANT]
17-
> Application Gateway IPv6 support is now generally available. Updates to the Azure portal for IPv6 support are currently being deployed across all regions and will be fully available within the next few weeks. In the meantime to use the portal to create an IPv6 Application Gateway continue using the [preview registration process](/azure/azure-resource-manager/management/preview-features?tabs=azure-portal) in the Azure portal to opt in for **Allow Application Gateway IPv6 Access**.
17+
> Application Gateway IPv6 support is now generally available.
1818
1919
[Azure Application Gateway](overview.md) supports dual stack (IPv4 and IPv6) frontend connections from clients. To use IPv6 frontend connectivity, you need to create a new Application Gateway. Currently you can’t upgrade existing IPv4 only Application Gateways to dual stack (IPv4 and IPv6) Application Gateways. Also, currently backend IPv6 addresses aren't supported.
2020

@@ -37,7 +37,7 @@ You can also complete this quickstart using [Azure PowerShell](ipv6-application-
3737

3838
## Regions and availability
3939

40-
The IPv6 Application Gateway preview is available to all public cloud regions where Application Gateway v2 SKU is supported. It's also available in [Microsoft Azure operated by 21Vianet](https://www.azure.cn/) and [Azure Government](https://azure.microsoft.com/overview/clouds/government/)
40+
The IPv6 Application Gateway is available to all public cloud regions where Application Gateway v2 SKU is supported. It's also available in [Microsoft Azure operated by 21Vianet](https://www.azure.cn/) and [Azure Government](https://azure.microsoft.com/overview/clouds/government/)
4141

4242
## Limitations
4343

@@ -56,7 +56,7 @@ An Azure account with an active subscription is required. If you don't already
5656

5757
Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
5858

59-
Use the [preview registration process](/azure/azure-resource-manager/management/preview-features?tabs=azure-portal) in the Azure portal to **Allow Application Gateway IPv6 Access**. This is required until the feature is completely rolled out in the Azure portal.
59+
6060

6161
## Create an application gateway
6262

@@ -103,14 +103,14 @@ Create the application gateway using the tabs on the **Create application gatewa
103103
1. On the **Frontends** tab, verify **Frontend IP address type** is set to **Public**.
104104

105105
> [!IMPORTANT]
106-
> For the Application Gateway v2 SKU, there must be a **Public** frontend IP configuration. A private IPv6 frontend IP configuration (Only ILB mode) is currently not supported for the IPv6 Application Gateway preview.
106+
> For the Application Gateway v2 SKU, there must be a **Public** frontend IP configuration. A private IPv6 frontend IP configuration (Only ILB mode) is currently not supported for the IPv6 Application Gateway.
107107
108108
2. Select **Add new** for the **Public IP address**, enter a name for the public IP address, and select **OK**. For example, **myAGPublicIPAddress**.
109109

110110
![A screenshot of create new application gateway: frontends.](./media/ipv6-application-gateway-portal/ipv6-frontends.png)
111111

112112
> [!NOTE]
113-
> IPv6 Application Gateway (preview) supports up to 4 frontend IP addresses: two IPv4 addresses (Public and Private) and two IPv6 addresses (Public and Private)
113+
> IPv6 Application Gateway supports up to 4 frontend IP addresses: two IPv4 addresses (Public and Private) and two IPv6 addresses (Public and Private)
114114
115115

116116
3. Select **Next: Backends**.

0 commit comments

Comments
 (0)