Merge pull request #272047 from allyford/windows-disable-outbound-nat-ga

Windows Disable Outbond NAT GA

Author: prmerger-automator[bot]

articles/aks/nat-gateway.md

@@ -131,44 +131,15 @@ This configuration requires bring-your-own networking (via [Kubenet][byo-vnet-ku
         --assign-identity $IDENTITY_ID
     ```
 
-## Disable OutboundNAT for Windows (Preview)
+## Disable OutboundNAT for Windows
 
 Windows OutboundNAT can cause certain connection and communication issues with your AKS pods. An example issue is node port reuse. In this example, Windows OutboundNAT uses ports to translate your pod IP to your Windows node host IP, which can cause an unstable connection to the external service due to a port exhaustion issue.
 
 Windows enables OutboundNAT by default. You can now manually disable OutboundNAT when creating new Windows agent pools.
 
 ### Prerequisites
 
-* If you're using Kubernetes version 1.25 or older, you need to [update your deployment configuration][upgrade-kubernetes].
-* You need to install or update `aks-preview` and register the feature flag.
-
-  1. Install or update `aks-preview` using the [`az extension add`][az-extension-add] or [`az extension update`][az-extension-update] command.
-
-    ```azurecli-interactive
-    # Install aks-preview
-    az extension add --name aks-preview
-
-    # Update aks-preview
-    az extension update --name aks-preview
-    ```
-
-  2. Register the feature flag using the [`az feature register`][az-feature-register] command.
-
-    ```azurecli-interactive
-    az feature register --namespace Microsoft.ContainerService --name DisableWindowsOutboundNATPreview
-    ```
-
-  3. Check the registration status using the [`az feature list`][az-feature-list] command.
-
-    ```azurecli-interactive
-    az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/DisableWindowsOutboundNATPreview')].{Name:name,State:properties.state}"
-    ```
-
-  4. Refresh the registration of the `Microsoft.ContainerService` resource provider using the [`az provider register`][az-provider-register] command.
-
-    ```azurecli-interactive
-    az provider register --namespace Microsoft.ContainerService
-    ```
+* Existing AKS cluster with v1.26 or above. If you're using Kubernetes version 1.25 or older, you need to [update your deployment configuration][upgrade-kubernetes].
 
 ### Limitations