Merge branch 'main' of https://github.com/MicrosoftDocs/azure-stack-docs-pr into hubki1-06

Author: sethmanheim

AKS-Hybrid/TOC.yml

@@ -167,7 +167,7 @@
   - name: Resources
     items:
     - name: Azure Local
-      href: /azure-local/index
+      href: /azure/azure-local
     - name: Azure Adaptive Cloud
       href: /azure/adaptive-cloud
     - name: Azure Arc Jumpstart

AKS-Hybrid/deploy-ai-model.md

@@ -119,7 +119,7 @@ To deploy the AI model, follow these steps:
 
 1. Create a YAML file using the following template. KAITO supports popular OSS models such as Falcon, Phi3, Llama2, and Mistral. This list might increase over time.
 
-   - The **PresetName** is used to specify which model to deploy, and you can find its value in the [supported model file](https://github.com/Azure/kaito/blob/main/presets/models/supported_models.yaml) in the GitHub repo. In the following example, `falcon-7b-instruct` is used for the model deployment.
+   - The **PresetName** is used to specify which model to deploy, and you can find its value in the [supported model file](https://github.com/kaito-project/kaito/blob/main/presets/workspace/models/supported_models.yaml) in the GitHub repo. In the following example, `falcon-7b-instruct` is used for the model deployment.
    - We recommend using `labelSelector` and `preferredNodes` to explicitly select the GPU node by name. In the following example, `app: llm-inference` is used for the GPU node `moc-le4aoguwyd9`. You can choose any node label you want, as long as the labels match. The next step shows how to label the node.
 
    ```yaml

azure-stack/operator/known-issues.md

@@ -3,7 +3,7 @@ title: Azure Stack Hub known issues
 description: Learn about known issues in Azure Stack Hub releases.
 author: sethmanheim
 ms.topic: article
-ms.date: 12/04/2024
+ms.date: 01/06/2025
 ms.author: sethm
 ms.reviewer: rtiberiu
 ms.lastreviewed: 11/30/2023
@@ -121,8 +121,6 @@ To access known issues for a different version, use the version selector dropdow
 
 <!-- ## Alerts -->
 
-<!-- ## Portal -->
-
 <!-- ## Datacenter integration -->
 
 <!-- ## Storage -->
@@ -143,6 +141,17 @@ To access known issues for a different version, use the version selector dropdow
 
 ::: moniker-end
 
+::: moniker range="azs-2406 || azs-2408"
+## Portal
+
+### Deployments blade under subscription fails to load
+
+- Applicable: This issue applies to release 2406 and later.
+- Cause: Due to a change in how subscription-level deployments are stored, an internal server error occurs when deploying or viewing deployments at subscription scope.
+- Remediation: Microsoft is aware of the issue and is working on a fix.
+- Occurrence: Common.
+::: moniker-end
+
 ::: moniker range="azs-2311"
 
 <!-- ## Update -->
@@ -187,6 +196,8 @@ To access known issues for a different version, use the version selector dropdow
 
 ## Portal
 
+### Can't use Flow Timeout and BGP community string DNS options in the portal
+
 - Applicable: This issue applies to release 2311.
 - Cause: In the Azure Stack Hub user portal, under the **Virtual Networks** section, there are three new options for virtual networks: **DNS Servers**, **Flow Timeout**, and **BGP community string**. You can successfully modify the DNS configuration using the **DNS Servers** option. However, attempts to use the **Flow Timeout** and **BGP community string** options result in a failure within the portal notifications. No changes are made to the underlying services; the errors are only in the portal.
 - Remediation: Microsoft is aware of the problem and is working on a fix.
@@ -229,8 +240,8 @@ To access known issues for a different version, use the version selector dropdow
 <!------------------------------------------------------------>
 <!------------------- UNSUPPORTED VERSIONS ------------------->
 <!------------------------------------------------------------>
-::: moniker range="azs-2311"
-## 2311 archived known issues
+::: moniker range="azs-2306"
+## 2306 archived known issues
 ::: moniker-end
 ::: moniker range="azs-2301"
 ## 2301 archived known issues