Remove version from Azure Local refs

Author: sethmanheim

.openpublishing.redirection.aks.json

@@ -1439,6 +1439,21 @@
         "source_path": "AKS-Arc/aks-known-issues.md",
         "redirect_url": "/azure/aks/aksarc/aks-troubleshoot",
         "redirect_document_id": false
+      },
+      {
+        "source_path": "AKS-Arc/aks-whats-new-23h2.md",
+        "redirect_url": "/azure/aks/aksarc/aks-whats-new-local",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "AKS-Arc/azure-rbac-23h2.md",
+        "redirect_url": "/azure/aks/aksarc/azure-rbac-local",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "AKS-Arc/kubernetes-rbac-23h2.md",
+        "redirect_url": "/azure/aks/aksarc/kubernetes-rbac-local",
+        "redirect_document_id": false
       }
     ]
   }

AKS-Arc/TOC.yml

@@ -11,11 +11,11 @@
     href: data-collection.md
   - name: Blogs and announcements
     href: blogs-announcements.md
-- name: AKS on Azure Local, version 23H2
+- name: AKS on Azure Local
   expanded: true
   items:
-  - name: What's new in AKS on Azure Local, version 23H2
-    href: aks-whats-new-23h2.md
+  - name: What's new in AKS on Azure Local
+    href: aks-whats-new-local.md
   - name: Concepts
     items:
     - name: Architecture
@@ -85,9 +85,9 @@
       - name: Enable Microsoft Entra ID authentication for Kubernetes clusters
         href: enable-authentication-microsoft-entra-id.md
       - name: Use Azure RBAC for Kubernetes authorization
-        href: azure-rbac-23h2.md
+        href: azure-rbac-local.md
       - name: Use Kubernetes RBAC with Microsoft Entra ID
-        href: kubernetes-rbac-23h2.md
+        href: kubernetes-rbac-local.md
       - name: Retrieve certificate-based admin kubeconfig
         href: retrieve-admin-kubeconfig.md
       - name: Configure SSH keys for a cluster

AKS-Arc/aks-arc-use-node-taints.md

@@ -1,8 +1,7 @@
 ---
 title: Manage node taints for an AKS cluster
-description: Learn how to manage node taints in AKS on Azure Local, version 23H2
+description: Learn how to manage node taints in AKS on Azure Local
 ms.topic: how-to
-ms.custom:
 ms.date: 06/03/2024
 author: sethmanheim
 ms.author: sethm 

AKS-Arc/aks-create-clusters-cli.md

@@ -16,7 +16,7 @@ ms.reviewer: guanghu
 
 This article describes how to create Kubernetes clusters in Azure Local using Azure CLI. The workflow is as follows:
 
-1. Create a Kubernetes cluster in Azure Local, version 23H2 using Azure CLI. The cluster is Azure Arc-connected by default.
+1. Create a Kubernetes cluster in Azure Local using Azure CLI. The cluster is Azure Arc-connected by default.
 1. While creating the cluster, you provide a Microsoft Entra group that contains the list of Microsoft Entra users with Kubernetes cluster administrator access.
 1. Access the cluster using kubectl and your Microsoft Entra ID.
 1. Run a sample multi-container application with a web front end and a Redis instance in the cluster.
@@ -62,7 +62,7 @@ Note the following considerations when you create a cluster:
 - By default, the SSH key is stored at **~/.ssh/id_rsa.pub**. During cluster creation, you can specify an alternate location using the `--ssh-key-value` parameter.
 
 > [!IMPORTANT]
-> To use Azure RBAC or workload identity for an AKS cluster, you must pass the required parameters during cluster creation using Azure CLI. Currently, updating an existing AKS cluster to enable workload identity and/or Azure RBAC is not supported. For more information, see [Use Azure RBAC for Kubernetes authorization](/azure/aks/hybrid/azure-rbac-23h2) or [Deploy and configure Workload Identity for your cluster](workload-identity.md).
+> To use Azure RBAC or workload identity for an AKS cluster, you must pass the required parameters during cluster creation using Azure CLI. Currently, updating an existing AKS cluster to enable workload identity and/or Azure RBAC is not supported. For more information, see [Use Azure RBAC for Kubernetes authorization](/azure/aks/hybrid/azure-rbac-local) or [Deploy and configure Workload Identity for your cluster](workload-identity.md).
 
 ## Connect to the Kubernetes cluster
 

AKS-Arc/aks-create-clusters-portal.md

@@ -82,5 +82,5 @@ This article describes how to create Kubernetes clusters in Azure Local using th
 
 ## Next steps
 
-- [Review AKS on Azure Local, version 23H2 prerequisites](aks-hci-network-system-requirements.md)
-- [What's new in AKS on Azure Local](aks-whats-new-23h2.md)
+- [Review AKS on Azure Local prerequisites](aks-hci-network-system-requirements.md)
+- [What's new in AKS on Azure Local](aks-whats-new-local.md)

AKS-Arc/aks-hci-ip-address-planning.md

@@ -111,4 +111,4 @@ AKS provides a **default value of 10.96.0.0/12** for the service network CIDR. A
 
 ## Next steps
 
-[Create logical networks for Kubernetes clusters on Azure Local, version 23H2](aks-networks.md)
+[Create logical networks for Kubernetes clusters on Azure Local](aks-networks.md)

AKS-Arc/aks-hci-network-system-requirements.md

@@ -22,15 +22,15 @@ In this conceptual article, the following key components are introduced. These c
 
 ## Logical networks for AKS Arc VMs and control plane IP
 
-Kubernetes nodes are deployed as specialized virtual machines in AKS enabled by Arc. These VMs are allocated IP addresses to enable communication between Kubernetes nodes. AKS Arc uses Azure Local logical networks to provide IP addresses and networking for the underlying VMs of the Kubernetes clusters. For more information about logical networks, see [Logical networks for Azure Local](/azure-stack/hci/manage/create-logical-networks?tabs=azurecli). You must plan to reserve one IP address per AKS cluster node VM in your Azure Local environment.
+Kubernetes nodes are deployed as specialized virtual machines in AKS enabled by Arc. These VMs are allocated IP addresses to enable communication between Kubernetes nodes. AKS Arc uses Azure Local logical networks to provide IP addresses and networking for the underlying VMs of the Kubernetes clusters. For more information about logical networks, see [Logical networks for Azure Local](/azure/azure-local/manage/create-logical-networks?tabs=azurecli). You must plan to reserve one IP address per AKS cluster node VM in your Azure Local environment.
 
 > [!NOTE]
-> Static IP is the only supported mode for assigning an IP address to AKS Arc VMs. This is because Kubernetes requires the IP address assigned to a Kubernetes node to be constant throughout the lifecycle of the Kubernetes cluster. 
-> Software defined virtual networks and SDN related features are currently not supported on AKS on Azure Local, version 23H2. 
+> Static IP is the only supported mode for assigning an IP address to AKS Arc VMs. This is because Kubernetes requires the IP address assigned to a Kubernetes node to be constant throughout the lifecycle of the Kubernetes cluster.
+> Software defined virtual networks and SDN related features are currently not supported on AKS on Azure Local.
 
 The following parameters are required in order to use a logical network for AKS Arc cluster create operation:
 
-| [Az CLI logical networks parameter](/azure-stack/hci/manage/create-logical-networks?tabs=azurecli) | Description| Required parameter for AKS Arc cluster|
+| [Az CLI logical networks parameter](/azure/azure-local/manage/create-logical-networks?tabs=azurecli) | Description| Required parameter for AKS Arc cluster|
 |------------------|---------|-----------|
 | `--address-prefixes` | AddressPrefix for the network. Currently only 1 address prefix is supported. Usage: `--address-prefixes "10.220.32.16/24"`. | ![Supported](media/aks-hybrid-networks/check.png) |
 | `--dns-servers`      | Space-separated list of DNS server IP addresses. Usage: `--dns-servers 10.220.32.16 10.220.32.17`. | ![Supported](media/aks-hybrid-networks/check.png) |
@@ -62,19 +62,19 @@ Regardless of the option you choose, you must ensure that the IP addresses alloc
 
 ## Proxy settings
 
-Proxy settings in AKS are inherited from the underlying infrastructure system. The functionality to set individual proxy settings for Kubernetes clusters and change proxy settings isn't supported yet. For more information on how to set proxy correctly, see [proxy requirements for Azure Local](/azure-stack/hci/manage/configure-proxy-settings-23h2).
+Proxy settings in AKS are inherited from the underlying infrastructure system. The functionality to set individual proxy settings for Kubernetes clusters and change proxy settings isn't supported yet. For more information on how to set proxy correctly, see [proxy requirements for Azure Local](/azure/azure-local/manage/configure-proxy-settings-23h2).
 
 ## Firewall URL exceptions
 
-Firewall requirements for AKS have been consolidated with Azure Local firewall requirements. See [Azure Local firewall requirements](/azure-stack/hci/concepts/firewall-requirements) for list of URLs that need to be allowed to successfully deploy AKS.
+Firewall requirements for AKS have been consolidated with Azure Local firewall requirements. See [Azure Local firewall requirements](/azure/azure-local/concepts/firewall-requirements) for list of URLs that need to be allowed to successfully deploy AKS.
 
 ## DNS server settings
 
 You need to ensure that the DNS server of the logical network can resolve the FQDN of the Azure Local cluster. DNS name resolution is required for all Azure Local nodes to be able to communicate with the AKS VM nodes. 
 
 ## Network port and cross-VLAN requirements
 
-When you deploy Azure Local, you allocate a contiguous block of at least [six static IP addresses on your management network's subnet](/azure-stack/hci/deploy/deploy-via-portal#specify-network-settings), omitting addresses already used by the physical machines. These IPs are used by Azure Local and internal infrastructure (Arc Resource Bridge) for Arc VM management and AKS Arc. If your management network that provides IP addresses to Arc Resource Bridge related Azure Local services are on a different VLAN than the logical network you used to create AKS clusters, you need to ensure that the following ports are opened to successfully create and operate an AKS cluster. 
+When you deploy Azure Local, you allocate a contiguous block of at least [six static IP addresses on your management network's subnet](/azure/azure-local/deploy/deploy-via-portal#specify-network-settings), omitting addresses already used by the physical machines. These IPs are used by Azure Local and internal infrastructure (Arc Resource Bridge) for Arc VM management and AKS Arc. If your management network that provides IP addresses to Arc Resource Bridge related Azure Local services are on a different VLAN than the logical network you used to create AKS clusters, you need to ensure that the following ports are opened to successfully create and operate an AKS cluster. 
 
 | Destination Port | Destination | Source | Description | Bi-directional cross VLAN networking notes |
 |------------------|-------------|--------|-------------|----------------|
@@ -84,4 +84,5 @@ When you deploy Azure Local, you allocate a contiguous block of at least [six st
 | 65000 | IP addresses in management network | Logical network used for AKS Arc VMs | Cloud Agent gRPC authentication | If you use separate VLANs, the AKS Arc VMs need to access the IP addresses in management network used for cloud agent IP and cluster IP on this port and vice-versa. |
 
 ## Next steps
+
 [IP address planning and considerations for Kubernetes clusters and applications](aks-hci-ip-address-planning.md)

AKS-Arc/aks-hybrid-preview-uninstall.md

@@ -14,7 +14,7 @@ ms.lastreviewed: 01/30/2024
 
 [!INCLUDE [aks-hybrid-applies-to-azure-stack-hci-windows-server-sku](includes/aks-hci-applies-to-skus/aks-hybrid-applies-to-azure-stack-hci-windows-server-sku.md)]
 
-This step is only required if you installed the AKS cluster provisioning from Azure preview. The preview ended with the release of [AKS enabled by Azure Arc on Azure Local version 23H2](aks-overview.md). This article describes the steps to uninstall the preview bits before upgrading to AKS Arc.
+This step is only required if you installed the AKS cluster provisioning from Azure preview. The preview ended with the release of [AKS enabled by Azure Arc on Azure Local](aks-overview.md). This article describes the steps to uninstall the preview bits before upgrading to AKS Arc.
 
 ## Step 1: delete all preview AKS clusters and Azure vnets created using Az CLI
 

AKS-Arc/aks-monitor-logging.md

@@ -15,7 +15,7 @@ ms.reviewer: guanghu
 
 # Monitor and log data
 
-[!INCLUDE [applies-to-azure stack-hci-and-windows-server-skus](includes/aks-hci-applies-to-skus/aks-hybrid-applies-to-azure-stack-hci-windows-server-sku.md)], Azure Local, version 23H2, AKS enabled by Azure Arc on VMware (preview)
+[!INCLUDE [applies-to-azure stack-hci-and-windows-server-skus](includes/aks-hci-applies-to-skus/aks-hybrid-applies-to-azure-stack-hci-windows-server-sku.md)], Azure Local, AKS enabled by Azure Arc on VMware (preview)
 
 This article describes how to monitor your AKS enabled by Azure Arc deployment using on-premises monitoring. Two types of monitoring and logging solutions are available, as described in the following table:
 
@@ -53,7 +53,7 @@ The objects and endpoints that the Prometheus solution scrapes include the follo
 
 Prometheus is an open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach. Grafana is a tool used to view, query, and visualize metrics on the Grafana dashboards. It can be configured to use Prometheus as the data source. Usually, they are used together for Kubernetes cluster monitoring.
 
-To view the Grafana dashboards available in AKS enabled by Arc, see [Grafana dashboards available in AKS](https://github.com/microsoft/AKS-HCI-Apps/blob/main/Monitoring/Grafana.md#grafana-dashboards-available-in-aks-hci).
+To view the Grafana dashboards available in AKS enabled by Arc, see [Grafana dashboards available in AKS](https://github.com/microsoft/AKS-Arc-Apps/blob/main/Monitoring/Grafana.md#grafana-dashboards-available-in-aks-hci).
 
 You can view Microsoft's deployment [guidance on GitHub](https://github.com/microsoft/AKS-Arc-Apps/tree/main/Monitoring) to deploy Prometheus on your Kubernetes cluster and configure Grafana to use Prometheus as data source. You can also follow any publicly available documentation to deploy any specific version of Prometheus or Grafana.
 

AKS-Arc/aks-networks.md

@@ -1,6 +1,6 @@
 ---
-title: Create logical networks for Kubernetes clusters on Azure Local, version 23H2
-description: Learn how to create Arc-enabled logical networks for AKS.
+title: Create logical networks for Kubernetes clusters on Azure Local
+description: Learn how to create Arc-enabled logical networks for AKS enabled by Azure Arc.
 ms.topic: how-to
 author: sethmanheim
 ms.date: 04/01/2025
@@ -9,18 +9,18 @@ ms.lastreviewed: 04/01/2024
 ms.reviewer: abha
 ---
 
-# Create logical networks for Kubernetes clusters on Azure Local, version 23H2
+# Create logical networks for Kubernetes clusters on Azure Local
 
 [!INCLUDE [hci-applies-to-23h2](includes/hci-applies-to-23h2.md)]
 
-After you install and configure Azure Local, version 23H2, you must create Arc VM logical networks. AKS on Azure Local uses static logical networks to provide IP addresses to the underlying VMs of the AKS clusters.
+After you install and configure Azure Local, you must create Arc VM logical networks. AKS on Azure Local uses static logical networks to provide IP addresses to the underlying VMs of the AKS clusters.
 
 ## Before you begin
 
 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).
+- Install and configure Azure Local. 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](aks-hci-network-system-requirements.md).
 - 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: