Updated NPM user doc- Removed the preview details

Author: Khushbu-Parekh

articles/aks/use-network-policies.md

@@ -33,31 +33,19 @@ Azure provides two ways to implement Network Policy. You choose a Network Policy
 * Azure's own implementation, called *Azure Network Policy Manager (NPM)*.
 * *Calico Network Policies*, an open-source network and network security solution founded by [Tigera][tigera].
 
-Azure NPM for Linux uses Linux *IPTables* and Azure NPM for Windows uses *Host Network Service (HNS) ACLPolicies* to enforce the specified policies. Policies are translated into sets of allowed and disallowed IP pairs. These pairs are then programmed as IPTable/HNS ACLPolicy filter rules.
+Azure NPM for Linux uses Linux *IPTables* to enforce the specified policies. Policies are translated into sets of allowed and disallowed IP pairs. These pairs are then programmed as IPTable filter rules.
 
 ## Differences between Azure NPM and Calico Network Policy and their capabilities
 
 | Capability                               | Azure  NPM                    | Calico Network Policy                     |
 |------------------------------------------|----------------------------|-----------------------------|
-| Supported platforms                      | Linux, Windows Server 2022                      | Linux, Windows Server 2019 and 2022  |
+| Supported platforms                      | Linux                     | Linux, Windows Server 2019 and 2022  |
 | Supported networking options             | Azure CNI                  | Azure CNI (Linux, Windows Server 2019 and 2022) and kubenet (Linux)  |
 | Compliance with Kubernetes specification | All policy types supported |  All policy types supported |
 | Additional features                      | None                       | Extended policy model consisting of Global Network Policy, Global Network Set, and Host Endpoint. For more information on using the `calicoctl` CLI to manage these extended features, see [calicoctl user reference][calicoctl]. |
 | Support                                  | Supported by Azure support and Engineering team | Calico community support. For more information on additional paid support, see [Project Calico support options][calico-support]. |
 | Logging                                  | Logs available with **kubectl log -n kube-system <network-policy-pod>** command | For more information, see [Calico component logs][calico-logs] |
 
-## Limitations:
-
-Azure Network Policy Manager(NPM) does not support IPv6. Otherwise, Azure NPM fully supports the network policy spec in Linux.
-* In Windows, Azure NPM does not support the following:
-    * named ports
-    * SCTP protocol
-    * negative match label or namespace selectors (e.g. all labels except "debug=true")
-    * "except" CIDR blocks (a CIDR with exceptions)
-
->[!NOTE]
-> * Azure NPM pod logs will record an error if an unsupported policy is created.
-
 ## Create an AKS cluster and enable Network Policy
 
 To see network policies in action, let's create an AKS cluster that supports network policy and then work on adding policies. 
@@ -75,7 +63,7 @@ The following example script:
 
 Instead of using a system-assigned identity, you can also use a user-assigned identity. For more information, see [Use managed identities](use-managed-identity.md).
 
-### Create an AKS cluster with Azure NPM enabled - Linux only 
+### Create an AKS cluster with Azure NPM enabled 
 
 In this section, we will work on creating a cluster with Linux node pools and Azure NPM enabled. 
 
@@ -99,64 +87,6 @@ az aks create \
     --network-policy azure
 ```
 
-### Create an AKS cluster with Azure NPM enabled - Windows Server 2022 (Preview)
-
-In this section, we will work on creating a cluster with Windows node pools and Azure NPM enabled.
-
-Please execute the following commands prior to creating a cluster:
-
-```azurecli
- az extension add --name aks-preview
- az extension update --name aks-preview
- az feature register --namespace Microsoft.ContainerService --name AKSWindows2022Preview
- az feature register --namespace Microsoft.ContainerService --name WindowsNetworkPolicyPreview
- az provider register -n Microsoft.ContainerService
-```
-
-> [!NOTE]
-> At this time, Azure NPM with Windows nodes is available on Windows Server 2022 only
->
-
-Now, you should replace the values for *$RESOURCE_GROUP_NAME*, *$CLUSTER_NAME* and *$WINDOWS_USERNAME* variables.
-
-```azurecli-interactive
-$RESOURCE_GROUP_NAME=myResourceGroup-NP
-$CLUSTER_NAME=myAKSCluster
-$WINDOWS_USERNAME=myWindowsUserName
-$LOCATION=canadaeast
-```
-
-Create a username to use as administrator credentials for your Windows Server containers on your cluster. The following command prompts you for a username. Set it to `$WINDOWS_USERNAME`(remember that the commands in this article are entered into a BASH shell).
-
-```azurecli-interactive
-echo "Please enter the username to use as administrator credentials for Windows Server containers on your cluster: " && read WINDOWS_USERNAME
-```
-
-Use the following command to create a cluster :
-
-```azurecli
-az aks create \
-    --resource-group $RESOURCE_GROUP_NAME \
-    --name $CLUSTER_NAME \
-    --node-count 1 \
-    --windows-admin-username $WINDOWS_USERNAME \
-    --network-plugin azure \
-    --network-policy azure
-```
-
-It takes a few minutes to create the cluster. By default, your cluster is created with only a Linux node pool. If you would like to use Windows node pools, you can add one. For example:
-
-```azurecli
-az aks nodepool add \
-    --resource-group $RESOURCE_GROUP_NAME \
-    --cluster-name $CLUSTER_NAME \
-    --os-type Windows \
-    --name npwin \
-    --node-count 1
-```
-
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ### Create an AKS cluster for Calico network policies
 
 Create the AKS cluster and specify *azure* for the network plugin, and *calico* for the Network Policy. Using *calico* as the Network Policy enables Calico networking on both Linux and Windows node pools.

articles/virtual-network/kubernetes-network-policies.md

@@ -26,7 +26,7 @@ Network Policies provides micro-segmentation for pods just like Network Security
 
 ![Kubernetes network policies overview](./media/kubernetes-network-policies/kubernetes-network-policies-overview.png)
 
-Azure NPM implementation works in conjunction with the Azure CNI that provides VNet integration for containers. NPM is supported only on Linux and Windows Server 2022 today. The implementation enforces traffic filtering by configuring allow and deny IP rules in Linux IPTables or Windows HNS ACLPolicies based on the defined policies. These rules are grouped together using Linux IPSets or Windows HNS SetPolicies.
+Azure NPM implementation works in conjunction with the Azure CNI that provides VNet integration for containers. NPM is supported only on Linux today. The implementation enforces traffic filtering by configuring allow and deny IP rules in Linux IPTables based on the defined policies. These rules are grouped together using Linux IPSets.
 
 ## Planning security for your Kubernetes cluster
 When implementing security for your cluster, use network security groups (NSGs) to filter traffic entering and leaving your cluster subnet (North-South traffic). Use Azure NPM for traffic between pods in your cluster (East-West traffic).