edit

v-thepet · v-thepet · commit 1b4bf32f08fd · 2024-11-01T16:12:51.000-07:00
diff --git a/AKS-Hybrid/aks-known-issues.md b/AKS-Hybrid/aks-known-issues.md
@@ -38,7 +38,7 @@ This release maps to software version 10.2311.0.26 of Azure Local.
 | Portal           | The available list of VM types is not complete when creating Kubernetes clusters in the Azure portal.                            |                                                                                                                                            |
 | Cluster upgrade  | The Azure CLI command for cluster upgrade `az akshybrid upgrade` does not work without specifying the target Kubernetes version. | You must specify the target Kubernetes version when you run the `az akshybrid upgrade` command with the `--version <target version>` parameter. |
 | Supported VM size | The `az akshybrid vmsize` command does not correctly return the required available VM types.                                 | Wait for 10 minutes and rerun the same command to view the supported VM types. |
-| Azure Local upgrade      | Creating an AKS Arc cluster in the Azure portal results in the error "The cluster extension does not support resource type **Microsoft.HybridContainerService/ProvisionedClusterInstances** with api-version `2024-01-01`". | The Azure portal is upgraded to the GA version, which doesn't support the preview of AKS on Azure Local 23H2. You must upgrade your Azure Local to the latest version. |
+| Azure Local upgrade      | Creating an AKS Arc cluster in the Azure portal results in the error "The cluster extension does not support resource type **Microsoft.HybridContainerService/ProvisionedClusterInstances** with api-version `2024-01-01`". | The Azure portal is upgraded to the GA version, which doesn't support the preview of AKS on Azure Local, version 23H2. You must upgrade Azure Local to the latest version. |
 
 ## Next steps
 
diff --git a/AKS-Hybrid/aks-networks.md b/AKS-Hybrid/aks-networks.md
@@ -21,7 +21,7 @@ Before you begin, make sure you have the following prerequisites:
 
 - Install and configure Azure Local, version 23H2. Make sure you have the custom location Azure Resource Manager ID, as this ID is a required parameter for creating a logical network.
 - Make sure that the logical network you create contains enough usable IP addresses to avoid IP address exhaustion. IP address exhaustion can lead to Kubernetes cluster deployment failures. For more information, see [Networking concepts in AKS on Azure Local, version 23H2](aks-hci-network-system-requirements.md).
-- Make sure you have an external VM switch that can be accessed by all the servers in your Azure Local cluster. By default, an external switch is created during the deployment of your Azure Local cluster that you can use to associate with the logical network you will create.
+- Make sure you have an external VM switch that can be accessed by all the machines in your Azure Local cluster. By default, an external switch is created during the deployment of your Azure Local cluster that you can use to associate with the logical network you will create.
 
 Run the following command to get the name of the external VM switch on your Azure Local cluster:
 
diff --git a/AKS-Hybrid/aks-whats-new-23h2.md b/AKS-Hybrid/aks-whats-new-23h2.md
@@ -105,11 +105,11 @@ The following Kubernetes cluster deployment and management capabilities are avai
 
 ### Release 2311
 
-Starting with this release, you can run Azure Kubernetes Service (AKS) workloads on your Azure Local system. AKS on Azure Local, version 23H2 uses Azure Arc to create new Kubernetes clusters on Azure Local directly from Azure.
+Starting with this release, you can run Azure Kubernetes Service (AKS) workloads on your Azure Local instance. AKS on Azure Local, version 23H2 uses Azure Arc to create new Kubernetes clusters on Azure Local directly from Azure.
 
 The following Kubernetes cluster deployment and management capabilities are available:
 
-- **Simplified infrastructure deployment on Azure Local**. In this release, the infrastructure components of AKS Arc, including the Arc Resource Bridge, Custom Location, and the Kubernetes Extension for the AKS Arc operator, are all deployed as part of the Azure Local, version 23H2 deployment. For more information, see [Deploy an Azure Local, version 23H2 system using the Azure portal](/azure-stack/hci/deploy/deploy-via-portal).
+- **Simplified infrastructure deployment on Azure Local**. In this release, the infrastructure components of AKS Arc, including the Arc Resource Bridge, Custom Location, and the Kubernetes Extension for the AKS Arc operator, are all deployed as part of the Azure Local, version 23H2 deployment. For more information, see [Deploy an Azure Local, version 23H2 instance using the Azure portal](/azure-stack/hci/deploy/deploy-via-portal).
 - **Integrated infrastructure upgrade on Azure Local**. The whole lifecycle management of AKS Arc infrastructure follows the same approach as the other components on Azure Local, version 23H2. For more information, see [Infrastructure component updates](infrastructure-components.md).
 - **New CLI consistent with Azure**. Starting with this release, a new consistent command-line experience is available to create and manage Kubernetes clusters.
 - **Cloud-based management**. You can now create and manage Kubernetes clusters on Azure Local with familiar tools such as the Azure portal and Azure CLI. For more information, see [Create Kubernetes clusters using Azure CLI](aks-create-clusters-cli.md).
diff --git a/AKS-Hybrid/deploy-gpu-node-pool.md b/AKS-Hybrid/deploy-gpu-node-pool.md
@@ -73,7 +73,7 @@ Install the Azure Local, version 23H2 operating system locally on each server in
 On each host machine, navigate to **Control Panel > Add or Remove programs**, uninstall the NVIDIA host driver, then reboot the machine. After the machine reboots, confirm that the driver was successfully uninstalled. Open an elevated PowerShell terminal and run the following command:
 
 ```powershell
-Get-PnpDevice  | select status, class, friendlyname, instanceid | findstr /i /c:"3d video" 
+Get-PnpDevice  | select status, class, friendlyname, instanceid | where {$_.friendlyname -eq "3D Video Controller"} 
 ```
 
 You should see the GPU devices appear in an error state as shown in this example output:
@@ -99,7 +99,7 @@ Dismount-VMHostAssignableDevice -LocationPath $lp1 -Force
 To confirm that the GPUs were correctly dismounted from the host, run the following command. You should put GPUs in an `Unknown` state:
 
 ```powershell
-Get-PnpDevice  | select status, class, friendlyname, instanceid | findstr /i /c:"3d video"
+Get-PnpDevice  | select status, class, friendlyname, instanceid | where {$_.friendlyname -eq "3D Video Controller"}
 ```
 
 ```output
@@ -131,7 +131,7 @@ pnputil /scan-devices
 After you install the mitigation driver, the GPUs are listed in the **OK** state under **Nvidia A2_base - Dismounted**:
 
 ```powershell
-Get-PnpDevice  | select status, class, friendlyname, instanceid | findstr /i /c:"nvidia"
+Get-PnpDevice  | select status, class, friendlyname, instanceid | where {$_.friendlyname -match "Nvidia"}"
 ```
 
 ```output
diff --git a/AKS-Hybrid/deploy-load-balancer-cli.md b/AKS-Hybrid/deploy-load-balancer-cli.md
@@ -83,7 +83,7 @@ Microsoft.KubernetesRuntime  RegistrationRequired  Registered
 Obtain the Application ID of the Arc extension by running [az ad sp list](/cli/azure/ad/sp#az-ad-sp-list). In order to run the following command, you must be a `user` member of your Azure tenant. For more information about user and guest membership, see [default user permissions in Microsoft Entra ID](/entra/fundamentals/users-default-permissions).
 
 ```azurecli
-$objID = az ad sp list --filter "appId eq '087fca6e-4606-4d41-b3f6-5ebdf75b8b4c'" --query "[].id" --output tsv
+$objID = az ad sp list --filter "appId eq '00001111-aaaa-2222-bbbb-3333cccc4444'" --query "[].id" --output tsv
 ```
 
 Once you have the $objID, you can install the MetalLB Arc extension on your Kubernetes cluster. To run the below command, you need to have [**Kubernetes extension contributor**](/azure/role-based-access-control/built-in-roles/containers#kubernetes-extension-contributor) role.
