Merge pull request #16704 from MicrosoftDocs/main

1/6/2025 PM Publish

Author: Taojunshen

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

azure-local/manage/create-logical-networks.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-stack-hci
-ms.date: 10/22/2024
+ms.date: 01/06/2025
 ---
 
 # Create logical networks for Azure Local
@@ -85,6 +85,11 @@ Complete the following steps to create a logical network using Azure CLI.
 
 You can use the `az stack-hci-vm network lnet create` cmdlet to create a logical network on the VM switch for a DHCP or a static IP configuration. The parameters used to create a DHCP and a static logical network are different.
 
+> [!NOTE]
+> For both dynamic and static logical networks, the following apply:
+> - Creating logical networks with overlapping IP pools on the same VLAN isn't permitted.
+> - If a VLAN ID isn't specified, the value defaults to 0.
+
 #### Create a static logical network via CLI
 
 In this release, you can create virtual machines using a static IP only via the Azure CLI.
@@ -127,6 +132,7 @@ Create a static logical network when you want to create virtual machines with ne
 
     > [!NOTE]
     > DNS server and gateway must be specified if you're creating a static logical network.
+ 
 
 1. Create a static logical network. Run the following cmdlet:
 

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