Tweaks

Author: sethmanheim

azure-stack/operator/known-issues.md

@@ -92,17 +92,6 @@ 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 attempting to access the deployments for a subscription in the Administrator portal. Therefore, Azure Stack Hub deployments are not viewable in the Azure portal.
-- Remediation: Microsoft is aware of the issue and is working on a fix.
-- Occurrence: Common.
-::: moniker-end
-
 ::: moniker range="azs-2406"
 
 <!-- ## Update -->
@@ -152,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 attempting to access the deployments for a subscription in the Administrator portal. Therefore, Azure Stack Hub deployments are not viewable in the Azure portal.
+- Remediation: Microsoft is aware of the issue and is working on a fix.
+- Occurrence: Common.
+::: moniker-end
+
 ::: moniker range="azs-2311"
 
 <!-- ## Update -->
@@ -196,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.