addressed comment

Author: rashrig

articles/operator-nexus/includes/kubernetes-cluster/cluster-connect-ps.md

@@ -1,7 +1,7 @@
 ---
 author: rashirg
 ms.author: rajeshwarig
-ms.date: 09/28/2023
+ms.date: 10/03/2023
 ms.topic: include
 ms.service: azure-operator-nexus
 ---
@@ -11,26 +11,23 @@ ms.service: azure-operator-nexus
 
 To access your cluster, you need to set up the cluster connect `kubeconfig`. After logging into Azure PowerShell with the relevant Azure AD entity, you can obtain the `kubeconfig` necessary to communicate with the cluster from anywhere, even outside the firewall that surrounds it.
 
-1. Set `CLUSTER_NAME`, `RESOURCE_GROUP` and `SUBSCRIPTION_ID` variables.
-    ```azurepowershell
-    $CLUSTER_NAME="myNexusK8sCluster"
-    $RESOURCE_GROUP="myResourceGroup"
-    $LOCATION   
-    ```
+1. Set CLUSTER_NAME, RESOURCE_GROUP, LOCATION and SUBSCRIPTION_ID variables.
 
-2. Set the environment variables needed for Azure PowerShell to use the outbound proxy server:
     ```azurepowershell
-    $Env:HTTP_PROXY = "<proxy-server-ip-address>:<port>"
-    $Env:HTTPS_PROXY = "<proxy-server-ip-address>:<port>"
-    $Env:NO_PROXY = "<cluster-apiserver-ip-address>:<port>"
+    $CLUSTER_NAME="myNexusK8sCluster"
+    $LOCATION="<ClusterAzureRegion>"
+    $MANAGED_RESOURCE_GROUP=(Get-AzNetworkCloudKubernetesCluster -KubernetesClusterName $CLUSTER_NAME `
+    -SubscriptionId <mySubscription> `
+    -ResourceGroupName myResourceGroup `
+    | Select-Object -Property ManagedResourceGroupConfigurationName)
     ```
-
-3. The following command starts a connectedk8s proxy that allows you to connect to the Kubernetes API server for the specified Nexus Kubernetes cluster.
+    
+2. Run the following command to connect to the cluster.
     ```azurecpowershell
-    New-AzConnectedKubernetes -ClusterName $CLUSTER_NAME -ResourceGroupName $RESOURCE_GROUP -Location $LOCATION -Proxy 'https://<proxy-server-ip-address>:<port>'
+    New-AzConnectedKubernetes -ClusterName $CLUSTER_NAME -ResourceGroupName $MANAGED_RESOURCE_GROUP -Location $LOCATION'
     ```
 
-4. Use `kubectl` to send requests to the cluster:
+2. Use `kubectl` to send requests to the cluster:
 
     ```console
     kubectl get pods -A

articles/operator-nexus/includes/kubernetes-cluster/quickstart-prereq-ps.md

@@ -16,7 +16,7 @@ ms.custom: devx-track-azurecpowershell
 * If you are running PowerShell locally, install the Az PowerShell module and connect to your Azure account using the [Connect-AzAccount](/powershell/module/az.accounts/Connect-AzAccount) cmdlet. For more information about installing the Az PowerShell module, see [Install Azure PowerShell][install-azure-powershell].
 
 * If you have multiple Azure subscriptions, select the appropriate subscription ID in which the resources should be billed using the
-[Set-AzContext](/powershell/module/az.accounts/set-azcontext) cmdlet.
+[Set-AzContext](/powershell/module/az.accounts/set-azcontext) cmdlet. On setting the subscription, one need not pass the 'SubscriptionID' each time executing the PowerShell command.
 
 * Refer the VM SKU table in the [reference section](../../reference-nexus-kubernetes-cluster-sku.md) for the list of supported VM SKUs.
 

articles/operator-nexus/includes/kubernetes-cluster/quickstart-review-deployment-ps.md

@@ -12,14 +12,14 @@ To view the details of the ```myNexusK8sCluster``` cluster in the ```myResourceG
 
 ```azurepowershell-interactive
 Get-AzNetworkCloudKubernetesCluster -KubernetesClusterName myNexusK8sCluster `
--SubscriptionId mySubscription `
--ResourceGroupName myResourceGroup
+-ResourceGroupName myResourceGroup `
+-SubscriptionId <mySubscription>
 ```
 
 Additionally, to get a list of agent pool names associated with the ```myNexusK8sCluster``` cluster in the ```myResourceGroup``` resource group, you can use the following Azure PowerShell command.
 
 ```azurepowershell-interactive
  Get-AzNetworkCloudAgentPool -KubernetesClusterName myNexusK8sCluster `
  -ResourceGroupName myResourceGroup `
- -SubscriptionId mySubscription
+ -SubscriptionId <mySubscription>
 ```

articles/operator-nexus/includes/kubernetes-cluster/quickstart-review-nodepool-ps.md

@@ -1,7 +1,7 @@
 ---
 author: rashirg
 ms.author: rajeshwarig
-ms.date: 09/27/2023
+ms.date: 10/07/2023
 ms.topic: include
 ms.service: azure-operator-nexus
 ---
@@ -12,7 +12,9 @@ ms.service: azure-operator-nexus
 The following output example resembles successful creation of the agent pools.
 
 ```azurepowershell
-Get-AzNetworkCloudAgentPool -KubernetesClusterName myNexusK8sCluster -SubscriptionId mySubscription -ResourceGroupName myResourceGroup
+Get-AzNetworkCloudAgentPool -KubernetesClusterName myNexusK8sCluster `
+-ResourceGroupName myResourceGroup `
+-SubscriptionId <mySubscription> 
 
 Location  Name                            SystemDataCreatedAt   SystemDataCreatedBy    SystemDataCreatedByType SystemDataLastModifiedAt SystemDataLastModifiedBy
 --------  ----                           -------------------   -------------------    ----------------------- ------------------------      ------------

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-ps.md

@@ -69,8 +69,8 @@ $DNS_SERVICE_IP="10.96.0.10"
 # AgentPoolConfiguration parameters
 $INITIAL_AGENT_POOL_COUNT="1"
 $MODE="System"
-$INITIAL_AGENT_POOL_NAME="agenpool1"
-$INITIAL_AGENT_POOL_VM_SIZE="NC_G2_v1"
+$INITIAL_AGENT_POOL_NAME="agentpool1"
+$INITIAL_AGENT_POOL_VM_SIZE="NC_P10_56_v1"
 
 # NAKS Cluster Parameters
 $CLUSTER_NAME="myNexusK8sCluster"
@@ -81,7 +81,7 @@ $K8S_VERSION="1.24.9"
 $AAD_ADMIN_GROUP_OBJECT_ID="3d4c8620-ac8c-4bd6-9a92-f2b75923ef9f"
 $ADMIN_USERNAME="azureuser"
 $CONTROL_PLANE_COUNT="1"
-$CONTROL_PLANE_VM_SIZE="NC_G2_v1"
+$CONTROL_PLANE_VM_SIZE="NC_G6_28_v1"
 
 $AGENT_POOL_CONFIGURATION = New-AzNetworkCloudInitialAgentPoolConfigurationObject `
 -Count $INITIAL_AGENT_POOL_COUNT `
@@ -140,7 +140,7 @@ $CUSTOM_LOCATION_TYPE="CustomLocation"
 $LOCATION="<ClusterAzureRegion>"
 $CLUSTER_NAME="myNexusK8sCluster"
 $AGENT_POOL_NAME="myNexusK8sCluster-nodepool-2"
-$AGENT_POOL_VM_SIZE="NC_G2_v1"
+$AGENT_POOL_VM_SIZE="NC_P10_56_v1"
 $AGENT_POOL_COUNT="1"
 $AGENT_POOL_MODE="User"
 ```