Merge pull request #17494 from sethmanheim/ws3-27

AKS: WS only for 22H2

Author: sethmanheim

AKS-Arc/TOC.yml

@@ -278,6 +278,8 @@
     items:
     - name: AKS Edge Essentials PowerShell 
       href: ./reference/aks-edge-ps/index.md
+    - name: Get support
+      href: aks-edge-help-support.md
     - name: Troubleshooting 
       href: aks-edge-troubleshoot-overview.md
     - name: Logs 
@@ -364,7 +366,7 @@
         href: tutorial-kubernetes-prepare-application.md
       - name: 2 - Create container registry
         href: tutorial-kubernetes-prepare-azure-container-registry.md
-      - name: 3 - Deploy a workload cluster
+      - name: 3 - Deploy a Kubernetes cluster
         href: tutorial-kubernetes-deploy-cluster.md
       - name: 4 - Run an application
         href: tutorial-kubernetes-deploy-application.md
@@ -554,7 +556,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
@@ -573,7 +575,7 @@
       href: aks-hybrid-preview-uninstall.md
     - name: Troubleshooting overview
       href: troubleshoot-overview.md
-    - name: Azure Arc enabled Kubernetes
+    - name: Azure Arc-enabled Kubernetes
       href: known-issues-arc.yml
     - name: Pre-installation validation tests
       href: validation-tests.md
@@ -599,12 +601,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/ad-sso.md

@@ -1,31 +1,31 @@
 ---
-title: Use Active Directory single sign-on for secure connection to Kubernetes API server in AKS enabled by Azure Arc
+title: Use Active Directory single sign-on for secure connection to Kubernetes API server in AKS on Windows Server
 description: Use Active Directory Authentication to securely connect to the API server with SSO credentials
 author: sethmanheim
 ms.topic: how-to
-ms.date: 08/07/2024
+ms.date: 04/02/2025
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
-ms.reviewer: sulahiri
+ms.reviewer: leslielin
 
 # Intent: As an IT Pro, I want to ue Active Directory Authentication to securely connect to the Kubernetes API server with SSO credentials.
 # Keyword: secure connection to Kubernetes API server
 
 ---
 
-# Use Active Directory single sign-on for secure connection to Kubernetes API server in AKS enabled by Azure Arc
+# Use Active Directory single sign-on for secure connection to Kubernetes API server in AKS on Windows Server
 
 [!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)]
 
-You can create a secure connection to your Kubernetes API server in AKS enabled by Arc using Active Directory (AD) single sign-on (SSO) credentials.
+You can create a secure connection to your Kubernetes API server in AKS on Windows Server using Active Directory (AD) single sign-on (SSO) credentials.
 
-## Overview of AD in AKS enabled by Arc
+## Overview of AD in AKS on Windows Server
 
-Without Active Directory authentication, you must rely on a certificate-based _kubeconfig_ file when you connect to the API server via the `kubectl` command. The **kubeconfig** file contains secrets such as private keys and certificates that need to be carefully distributed, which can be a significant security risk.
+Without Active Directory authentication, you must rely on a certificate-based *kubeconfig* file when you connect to the API server via the `kubectl` command. The **kubeconfig** file contains secrets such as private keys and certificates that need to be carefully distributed, which can be a significant security risk.
 
-As an alternative to using certificate-based kubeconfig, you can use AD SSO credentials as a secure way to connect to the API server. AD integration with AKS Arc lets users on a Windows domain-joined machine connect to the API server via `kubectl` using their SSO credentials. This removes the need to manage and distribute certificate-based kubeconfig files that contain private keys.
+As an alternative to using certificate-based **kubeconfig**, you can use AD SSO credentials as a secure way to connect to the API server. AD integration with AKS Arc lets users on a Windows domain-joined machine connect to the API server via `kubectl` using their SSO credentials. This removes the need to manage and distribute certificate-based **kubeconfig** files that contain private keys.
 
-AD integration uses AD kubeconfig, which is distinct from the certificate-based kubeconfig files and doesn't contain any secrets. However, the certificate-based kubeconfig file can be used for backup purposes, such as troubleshooting, if there are issues with connecting using Active Directory credentials.
+AD integration uses AD **kubeconfig**, which is distinct from the certificate-based **kubeconfig** files and doesn't contain any secrets. However, the certificate-based **kubeconfig** file can be used for backup purposes, such as troubleshooting, if there are issues with connecting using Active Directory credentials.
 
 Another security benefit with AD integration is that the users and groups are stored as [security identifiers (SIDs)](/troubleshoot/windows-server/identity/security-identifiers-in-windows). Unlike group names, SIDs are immutable and unique and therefore present no naming conflicts.
 
@@ -77,7 +77,7 @@ Before you can install AD authentication, the workload cluster must be installed
 
 #### Option 1
 
-For a domain-joined Azure Local or Windows Server cluster, open PowerShell as an administrator and run the following command:
+For a domain-joined Windows Server cluster, open PowerShell as an administrator and run the following command:
 
 ```powershell
 Install-AksHciAdAuth -name mynewcluster1 -keytab .\current.keytab -SPN k8s/[email protected] -adminUser contoso\bob

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

@@ -1,6 +1,6 @@
 ---
 title: Adapt applications for use in mixed-OS Kubernetes clusters
-description: Learn how to use node selectors or taints and tolerations on Azure Kubernetes Service to ensure applications in mixed OS Kubernetes clusters running on AKS Arc are scheduled on the correct worker node operating system.
+description: Learn how to use node selectors or taints and tolerations on Azure Kubernetes Service to ensure applications in mixed OS Kubernetes clusters running on AKS on Windows Server are scheduled on the correct worker node operating system.
 author: sethmanheim
 ms.topic: how-to
 ms.date: 06/27/2024
@@ -16,9 +16,9 @@ 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 on Windows Server 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).
+This article assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for AKS on Windows Server](kubernetes-concepts.md).
 
 ## Node selectors
 

AKS-Arc/add-ons.md

@@ -1,6 +1,6 @@
 ---
-title: Add-ons and extensions available for AKS enabled by Arc
-description: Learn about what add-ons and integrations are supported in AKS enabled by Azure Arc.
+title: Add-ons and extensions available for AKS on Windows Server
+description: Learn about what add-ons and integrations are supported in AKS on Windows Server.
 author: sethmanheim
 ms.topic: how-to
 ms.date: 02/15/2024
@@ -9,9 +9,9 @@ ms.lastreviewed: 02/15/2023
 ms.reviewer: baziwane
 ---
 
-# Add-ons, extensions, and other integrations with AKS enabled by Arc
+# Add-ons, extensions, and other integrations with AKS on Windows Server
 
-Azure Kubernetes Service (AKS) enabled by Azure Arc provides augmented functionality for your Kubernetes cluster, mainly through extensions that are supported by Microsoft. There are also many integrations offered by open-source projects and third-party organizations. It's important to note that these integrations, which are not supported by AKS Arc, are not included in the [AKS Arc support policy](support-policies.md).
+Azure Kubernetes Service (AKS) on Windows Server provides augmented functionality for your Kubernetes cluster, mainly through extensions that are supported by Microsoft. There are also many integrations offered by open-source projects and third-party organizations. It's important to note that these integrations, which are not supported by AKS Arc, are not included in the [AKS Arc support policy](support-policies.md).
 
 ## Add-ons
 
@@ -30,15 +30,15 @@ The following rules are used by AKS Arc for applying updates to installed add-on
 | [Install-AksHciCsiNfs](reference/ps/install-akshcicsinfs.md)      | Installs the CSI NFS plug-in to a cluster.                       |
 | [Install-AksHciCsiSmb](reference/ps/install-akshcicsismb.md)      | Installs the CSI SMB plug-in to a cluster.                       |
 | [Install-AksHciGmsaWebhook](reference/ps/install-akshcigmsawebhook.md) | Installs gMSA webhook add-on to the cluster.                     |
-| [Install-AksHciMonitoring](reference/ps/install-akshcimonitoring.md)  | Installs Prometheus for monitoring in the AKS enabled by Arc deployment. |
+| [Install-AksHciMonitoring](reference/ps/install-akshcimonitoring.md)  | Installs Prometheus for monitoring in the AKS on Windows Server deployment. |
 
 ## Azure Arc extensions
 
 Cluster extensions build on top of certain Helm charts and provide an Azure Resource Manager-driven experience for installation and lifecycle management of different Azure capabilities on top of your Kubernetes cluster. You can [deploy these extensions to your clusters](/azure/azure-arc/kubernetes/extensions) to improve cluster management.
 
 ### Available extensions
 
-For more information about the specific cluster extensions for AKS enabled by Arc, see [Currently available extensions](/azure/azure-arc/kubernetes/extensions-release).
+For more information about the specific cluster extensions for AKS on Windows Server, see [Currently available extensions](/azure/azure-arc/kubernetes/extensions-release).
 
 ## Difference between extensions and add-ons
 
@@ -58,4 +58,4 @@ The following table shows examples of open-source and third-party integrations:
 
 ## Next steps
 
-- [AKS enabled by Arc overview](aks-overview.md)
+- [AKS on Windows Server overview](overview.md)

AKS-Arc/aks-edge-help-support.md

@@ -0,0 +1,63 @@
+---
+title: Get support for AKS Edge Essentials
+description: Learn about how to get support and open a support request for AKS Edge Essentials.
+author: sethmanheim
+ms.topic: conceptual
+ms.date: 04/07/2025
+ms.author: sethm 
+
+# 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 Edge Essentials support help requests
+---
+
+# Get support for AKS Edge Essentials
+
+If you encounter an issue with AKS Edge Essentials, this article describes how to open a support request.
+
+## Go to Support + troubleshooting in the Azure portal
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Browse to the subscription you're using for AKS Edge Essentials. 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":::
+
+1. From the dropdown, select the **Technical** issue type:
+
+    :::image type="content" source="media/help-support/select-type.png" alt-text="Screenshot of issue type selection." lightbox="media/help-support/select-type.png":::
+
+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 **Edge** in the search box to locate the **AKS Edge Essentials** service in the **Compute** category.
+
+    :::image type="content" source="media/help-support/service-type-edge.png" alt-text="Screenshot showing service selection." lightbox="media/help-support/service-type-edge.png":::
+
+1. Add a short description of your issue in the **Summary** field.
+
+1. Select the appropriate **Problem type** from the dropdown menu for your issue (for example, **Setup and configuration**). Also, select a **Problem subtype** (for example, **Deployment**):
+
+    :::image type="content" source="media/help-support/problem-type-edge.png" alt-text="Screenshot of completed problem type form." lightbox="media/help-support/problem-type-edge.png":::
+
+1. Select **Next**.
+
+1. Review the proposed **Solutions** to determine if they address your issue.
+
+1. If the solutions are not applicable, select **Return to support request** at the top of the page.
+
+1. Select **Next**.
+
+1. Fill in the problem details and description in the appropriate fields: 
+
+    :::image type="content" source="media/help-support/service-request-details.png" alt-text="Screenshot showing details of service request." lightbox="media/help-support/service-request-details.png":::
+
+1. Scroll down and fill in your preferred support method of contact:
+
+    :::image type="content" source="media/help-support/service-request-support-method.png" alt-text="Screenshot showing support method preferences." lightbox="media/help-support/service-request-support-method.png":::
+
+1. Select **Next**. Review the information you submitted. If anything is incorrect, select **Previous** and correct it. When all looks correct, select **Create**.
+
+    :::image type="content" source="media/help-support/review-create-edge.png" alt-text="Screenshot of confirmation screen to create support request." lightbox="media/help-support/review-create-edge.png":::
+
+## Next steps
+
+- [Troubleshoot common issues in AKS Edge Essentials](aks-edge-troubleshoot-overview.md)

AKS-Arc/aks-edge-licensing.md

@@ -32,7 +32,7 @@ The volume licensing model is only available in the Microsoft Enterprise Agreeme
 
 ### Third party access for software purchased via hoster's enterprise agreement
 
-Third-party access to solutions built on the volume licensing model procured via EA is granted via the [Azure Customer Solution](https://wwlpdocumentsearch.blob.core.windows.net/prodv2/Licensing_brief_PLT_Microsoft_Azure_Customer_Solution%20(9).pdf?sv=2020-08-04&se=2123-03-31T18:47:42Z&sr=b&sp=r&sig=dXbUQPxSo4dF1eANpQ8Zkr6ZA%2FgXxGBhCeUMEeoIdA0%3D). This means that, if the end customer needs to deploy a disconnected AKS Edge Essentials, a hoster/service provider needing a disconnected scenario is able to use the AKS Edge Essentials volume licensing model purchased with an EA. The volume licensing model doesn't offer the same per-tenant billing and CSP Partner Center integration benefits as the pay-as-you-use model, but it eliminates the need to connect the AKS Edge Essentials clusters to Azure to report usage.
+Third-party access to solutions built on the volume licensing model procured via EA is granted via the Azure Customer Solution. This means that, if the end customer needs to deploy a disconnected AKS Edge Essentials, a hoster/service provider needing a disconnected scenario is able to use the AKS Edge Essentials volume licensing model purchased with an EA. The volume licensing model doesn't offer the same per-tenant billing and CSP Partner Center integration benefits as the pay-as-you-use model, but it eliminates the need to connect the AKS Edge Essentials clusters to Azure to report usage.
 
 > [!CAUTION]
 > Microsoft will be a controller of [personal data](https://www.microsoft.com/licensing/terms/product/Glossary/all) processed in connection with your use of AKS Edge Essentials, and Microsoft handles the [personal data](https://www.microsoft.com/licensing/terms/product/Glossary/all) in accordance with the [Microsoft Privacy Statement](https://aka.ms/privacy).

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](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 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