Last ones

Author: sethmanheim

AKS-Arc/TOC.yml

@@ -547,7 +547,7 @@
       - name: Use OpenFaaS
         href: openfaas.md
       - name: Use Bridge to Kubernetes with Visual Studio Code
-        href: https://code.visualstudio.com/docs/containers/bridge-to-kubernetes
+        href: /visualstudio/bridge/bridge-to-kubernetes-vs-code
       - name: Use Bridge to Kubernetes with Visual Studio
         href: /visualstudio/containers/bridge-to-kubernetes
       - name: Deploy a Java application with Open Liberty or WebSphere Liberty
@@ -592,12 +592,6 @@
       href: known-issues-uninstall.yml
     - name: Other
       href: known-issues.yml
-    - name: Azure Local issues
-      items:
-      - name: Cluster validation reporting in Azure Local
-        href: /azure-stack/hci/manage/validate-qos
-      - name: CredSSP in Azure Local
-        href: /azure-stack/hci/manage/troubleshoot-credssp
     - name: Support policies
       href: support-policies.md
     - name: Get support

AKS-Arc/adapt-apps-mixed-os-clusters.md

@@ -16,7 +16,7 @@ ms.reviewer: abha
 
 [!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)]
 
-AKS enabled by Arc enables you to run Kubernetes clusters with both Linux and Windows nodes, but you must make small edits to your apps for use in these mixed-OS clusters. This how-to guide describes how to ensure your application gets scheduled on the right host OS using either node selectors or taints and tolerations.
+AKS enabled by Azure Arc enables you to run Kubernetes clusters with both Linux and Windows nodes, but you must make small edits to your apps for use in these mixed-OS clusters. This how-to guide describes how to ensure your application gets scheduled on the right host OS using either node selectors or taints and tolerations.
 
 This article assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for AKS enabled by Arc](kubernetes-concepts.md).
 

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

@@ -3,7 +3,7 @@ title: Before you begin - uninstall the AKS cluster provisioning preview
 description: Learn how to uninstall the AKS cluster provisioning from Azure preview.
 ms.topic: overview
 ms.custom: devx-track-azurecli
-ms.date: 01/30/2024
+ms.date: 04/03/2025
 author: sethmanheim
 ms.author: sethm 
 ms.reviewer: guanghu
@@ -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/deploy-java-liberty-app.md

@@ -6,10 +6,11 @@ ms.author: sethm
 ms.topic: conceptual
 ms.date: 06/27/2024
 ms.lastreviewed: 01/14/2022
-ms.reviewer: scooley
+ms.custom:  devx-track-extended-java, devx-track-java, devx-track-javaee, devx-track-javaee-liberty, devx-track-javaee-liberty-aks, devx-track-azurecli
+
 # Intent: As an IT Pro, I want to learn how to use Open Liberty or WebSphere Liberty to deploy a Java application. 
 # Keyword: java jakartaee javaee microprofile open-liberty websphere-liberty aks-hci kubernetes
-ms.custom:  devx-track-extended-java, devx-track-java, devx-track-javaee, devx-track-javaee-liberty, devx-track-javaee-liberty-aks, devx-track-azurecli
+
 ---
 
 # Deploy Java app with Open Liberty or WebSphere Liberty on Azure Kubernetes Service cluster

AKS-Arc/help-support.md

@@ -2,12 +2,12 @@
 title: Get support for AKS Arc and AKS Edge Essentials
 description: Learn about how to get support and open a support request for AKS enabled by Azure Arc or AKS Edge Essentials.
 ms.topic: conceptual
-ms.date: 07/11/2024
+ms.date: 04/03/2025
 ms.custom: fasttrack-edit
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
-ms.reviewer: mikek
 author: sethmanheim
+
 # Intent: As an IT Pro, I want to find out what options are available to get help and support, such as creating a ticket.
 # Keyword: AKS support AKS help support requests
 ---
@@ -20,10 +20,10 @@ If you encounter an issue with AKS enabled by Azure Arc or AKS Edge Essentials,
 
 Select the product you're using to see the relevant instructions on opening a support request.
 
-# [AKS on Azure Local](#tab/akshci)
+# [AKS on Windows Server](#tab/akshci)
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-1. Browse to the subscription you're using for Azure Kubernetes Services on Azure Local. Select the subscription to open its dashboard.
+1. Browse to the subscription you're using for Azure Kubernetes Services on Windows Server. Select the subscription to open its dashboard.
 1. From the **Support + troubleshooting** category in the navigation menu in the left-hand pane, select **New Support Request**:
 
     :::image type="content" source="media/help-support/new-support-request-sidebar.png" alt-text="Screenshot of the Azure portal Help and Support sidebar." lightbox="media/help-support/new-support-request-sidebar.png":::
@@ -34,7 +34,7 @@ Select the product you're using to see the relevant instructions on opening a su
 
 1. Your subscription name should auto-populate in the **Subscription** field. If it doesn't, select it from the dropdown.
 
-1. Select the **All services** button, then select the **Service type** dropdown. Begin typing **Azure Kubernetes Service** in the search box to locate the **Azure Kubernetes Service on Azure Local (AKS-HCI)** service in the **Compute** category.
+1. Select the **All services** button, then select the **Service type** dropdown. Begin typing **Azure Kubernetes Service** in the search box to locate the **Azure Kubernetes Service on Windows Server** service in the **Compute** category.
 
     :::image type="content" source="media/help-support/service-type.png" alt-text="Screenshot showing service selection." lightbox="media/help-support/service-type.png":::
 

AKS-Arc/known-issues-arc.yml

@@ -10,7 +10,7 @@ metadata:
 
 title: Resolve errors when enabling or disabling Azure Arc on your AKS workload clusters in AKS enabled by Arc
 summary: |
-  Applies to: AKS on Azure Local, AKS on Windows Server
+  Applies to: AKS on Windows Server
   
   This article describes errors you might encounter (and their workarounds) while connecting or disconnecting your AKS workload clusters to Azure Arc using the PowerShell cmdlets [`Enable-AksHciArcConnection`](./reference/ps/enable-akshciarcconnection.md) and [`Disable-AksHciArcConnection`](./reference/ps/disable-akshciarcconnection.md) in AKS Arc. For issues that are not covered in this article, see [Troubleshooting Arc enabled Kubernetes](/azure/azure-arc/kubernetes/troubleshooting).
   
@@ -57,10 +57,10 @@ sections:
         answer: | 
           This error usually points to one of the following issues:
           
-          - The clusters were created in an Azure VM in a virtualized environment, or you deployed AKS on Azure Local on multiple levels of virtualization. 
+          - The clusters were created in an Azure VM in a virtualized environment, or you deployed AKS on Windows Server on multiple levels of virtualization. 
           - A slow internet caused the timeout.
           
-          If one of the above scenarios applies to you, run [Disable-AksHciArcConnection](./reference/ps/disable-akshciarcconnection.md), and try connecting again. If the above scenario doesn't apply to you, [open a support issue](./help-support.md) for AKS on Azure Local.
+          If one of the above scenarios applies to you, run [Disable-AksHciArcConnection](./reference/ps/disable-akshciarcconnection.md), and try connecting again. If the above scenario doesn't apply to you, [open a support issue](./help-support.md) for AKS on Windows Server.
       - question: | 
           Error: "Secrets "sh.helm.release.v1.azure-arc.v1" not found"
 
@@ -90,7 +90,7 @@ sections:
 
         answer: | 
           This error usually means that you already connected your AKS cluster to Arc-enabled Kubernetes.
-          To confirm it's connected, go to the [Azure portal](https://portal.azure.com) and check under the subscription and resource group you provided when you ran [`Set-AksHciRegistration`](./reference/ps/set-akshciregistration.md) (if you used default values) or [`Enable-AksHciArcConnection`](./reference/ps/enable-akshciarcconnection.md) (if you didn't use default values). You can also confirm if your AKS on Azure Local cluster is connected to Azure by running the [`az connectedk8s show` ](/cli/azure/connectedk8s#az-connectedk8s-show) Azure CLI command. If you don't see your workload cluster, run `Disable-AksHciArcConnection` and try again.
+          To confirm it's connected, go to the [Azure portal](https://portal.azure.com) and check under the subscription and resource group you provided when you ran [`Set-AksHciRegistration`](./reference/ps/set-akshciregistration.md) (if you used default values) or [`Enable-AksHciArcConnection`](./reference/ps/enable-akshciarcconnection.md) (if you didn't use default values). You can also confirm if your AKS on Windows Server cluster is connected to Azure by running the [`az connectedk8s show` ](/cli/azure/connectedk8s#az-connectedk8s-show) Azure CLI command. If you don't see your workload cluster, run `Disable-AksHciArcConnection` and try again.
           
           
       - question: | 

AKS-Arc/known-issues-installation.yml

@@ -10,7 +10,7 @@ metadata:
   ms.date: 07/26/2024
 title: Resolve issues and errors during an AKS Arc installation
 summary: |
-  **Applies to: AKS on Azure Local, AKS on Windows Server**
+  **Applies to: AKS on Windows Server**
   This article describes known issues and errors you may encounter when installing AKS Arc. You can also review known issues with when [upgrading AKS Arc](/azure-stack/aks-hci/known-issues-upgrade) and when using [Windows Admin Center](/azure-stack/aks-hci/known-issues-windows-admin-center).
   
 sections:
@@ -23,7 +23,7 @@ sections:
           This error message appears after running [Install-AksHci](./reference/ps/install-akshci.md).
 
           > [!NOTE]
-          > The error might be caused by having Private Link enabled on the setup. Currently, there is no workaround for this scenario. AKS on Azure Local does not work with Private Link.
+          > The error might be caused by having Private Link enabled on the setup. Currently, there is no workaround for this scenario. AKS on Windows Server does not work with Private Link.
           
           If you are not using Private Link, to resolve this issue use the following steps:
           

AKS-Arc/openfaas.md

@@ -7,7 +7,7 @@ ms.custom: linux-related-content
 ms.date: 06/27/2024
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
-ms.reviewer: scooley
+
 # Keyword: OpenFaaS serverless functions
 ---
 

AKS-Arc/overview.md

@@ -15,6 +15,9 @@ ms.date: 04/02/2025
 
 [!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)]
 
+> [!IMPORTANT]
+> Microsoft is retiring the current architecture of AKS on Windows Server 2019 and AKS on Windows Server 2022 on March 27, 2028. We recommend that you upgrade to [AKS on Azure Local](aks-whats-new-23h2.md). For more information, see [Retirement of AKS architecture on Windows Server 2019 and Windows Server 2022](aks-windows-server-retirement.md).
+
 Azure Kubernetes Service (AKS) on Windows Server is an on-premises Kubernetes implementation of AKS. AKS on Windows Server automates running containerized applications at scale. AKS on Windows Server makes it quicker to get started hosting Linux and Windows containers in your datacenter.
 
 To get started with on-premises Kubernetes using AKS, [set up AKS enabled by Azure Arc](setup.md).

AKS-Arc/prepare-windows-nodes-gmsa.md

@@ -1,9 +1,9 @@
 ---
-title: Configure group Managed Service Accounts (gMSA) for Windows containers with Azure Kubernetes Service on Azure Local and Windows Server
+title: Configure group Managed Service Accounts (gMSA) for Windows containers with Azure Kubernetes Service on Windows Server
 description: Learn how to configure  Managed Service Accounts (gMSA) for containers on Windows nodes
 author: sethmanheim
 ms.topic: how-to
-ms.date: 02/13/2024
+ms.date: 04/03/2025
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: abha
@@ -13,7 +13,7 @@ ms.reviewer: abha
 
 ---
 
-# Configure group Managed Service Accounts (gMSA) for Windows containers with Azure Kubernetes Service on Azure Local and Windows Server
+# Configure group Managed Service Accounts (gMSA) for Windows containers with Azure Kubernetes Service on Windows Server
 
 [!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)]
 
@@ -46,7 +46,7 @@ To run a Windows container with a group managed service account, you need the fo
 - An Active Directory domain with at least one domain controller running Windows Server 2012 or later. There are no forest or domain functional level requirements to use gMSAs, but only domain controllers running Windows Server 2012 or later can distribute gMSA passwords. For more information, see [Active Directory requirements for gMSAs](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#BKMK_gMSA_Req).
 - Permission to create a gMSA account. To create a gMSA account, you must be a Domain Administrator or use an account that has permissions to create **msDS-GroupManagedServiceAccount** objects.
 - Access to the internet to download the [CredentialSpec](https://aka.ms/credspec) PowerShell module. If you're working in a disconnected environment, you can [save the module](/powershell/module/powershellget/save-module?preserve-view=true&view=powershell-5.1) on a computer with internet access and copy it to your development machine or container host.
-- To ensure gMSA and AD authentication work, ensure that the Azure Local and Windows Server cluster nodes are configured to synchronize their time with either a domain controller or other time source. You should also make sure Hyper-V is configured to synchronize time to any virtual machines.
+- To ensure gMSA and AD authentication work, ensure that the Windows Server cluster nodes are configured to synchronize their time with either a domain controller or other time source. You should also make sure Hyper-V is configured to synchronize time to any virtual machines.
 
 ## Prepare the gMSA in the domain controller
 
@@ -72,7 +72,7 @@ To prepare the gMSA credential spec JSON file, follow the steps for [creating a
 
 ## Configure gMSA for Windows pods and containers in the cluster
 
-The Kubernetes community already supports domain joined Windows worker nodes for [gMSA](https://kubernetes.io/docs/tasks/configure-pod-container/configure-gmsa/). Although you don't need to domain join a Windows worker node in AKS on Azure Local and Windows Server, there are other required configuration steps. These steps include installing the webhook, the custom resource definition (CRD), and the credential spec, and enabling role-based access control (RBAC role). The following steps use PowerShell commands that are built to help simplify the configuration process.
+The Kubernetes community already supports domain joined Windows worker nodes for [gMSA](https://kubernetes.io/docs/tasks/configure-pod-container/configure-gmsa/). Although you don't need to domain join a Windows worker node in AKS on Windows Server, there are other required configuration steps. These steps include installing the webhook, the custom resource definition (CRD), and the credential spec, and enabling role-based access control (RBAC role). The following steps use PowerShell commands that are built to help simplify the configuration process.
 
 Before completing the following steps, make sure the **AksHci** PowerShell module is installed and `kubectl` can connect to your cluster.
 
@@ -248,4 +248,4 @@ Uninstall-AksHciGMSAWebhook -Name <cluster name>
 ## Next steps
 
 - [Use persistent volume on a Kubernetes cluster](persistent-volume.md)
-- [Monitor AKS on Azure Local and Windows Server clusters](monitor-logging.md)
+- [Monitor AKS on Windows Server clusters](monitor-logging.md)