Merge branch 'release-azurelocal-rebrand' of https://github.com/MicrosoftDocs/azure-stack-docs-pr into 15-azlreb

Author: alkohli

azure-local/TOC.yml

@@ -87,7 +87,7 @@ items:
         href: security-update/security-update-dec-2023.md
       - name: November 2023 
         href: security-update/security-update-nov-2023.md
-  - name: Disconnected operations (Preview)
+  - name: Disconnected operations
     href: manage/disconnected-operations-overview.md
   - name: OEM License
     items: 
@@ -353,14 +353,14 @@ items:
         href: manage/vm-affinity.md
       - name: VM load balancing
         href: manage/vm-load-balancing.md
-      - name: Dynamic CPU compatibility
-        href: /windows-server/virtualization/hyper-v/manage/dynamic-processor-compatibility-mode?pivots=azure-stack-hci&context=/azure-local/context/context
-      - name: Use GPUs with clustered VMs
-        href: /windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm?pivots=azure-stack-hci&context=/azure-local/context/context
-      - name: GPU Partitioning
-        href: /windows-server/virtualization/hyper-v/gpu-partitioning?pivots=azure-stack-hci&context=/azure-local/context/context
-      - name: Partition and assign GPUs to a virtual machine
-        href: /windows-server/virtualization/hyper-v/partition-assign-vm-gpu?pivots=azure-stack-hci&context=/azure-local/context/context
+    #  - name: Dynamic CPU compatibility
+    #    href: /windows-server/virtualization/hyper-v/manage/dynamic-processor-compatibility-mode?pivots=azure-stack-hci&context=/azure-local/context/context
+    #  - name: Use GPUs with clustered VMs
+    #    href: /windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm?pivots=azure-stack-hci&context=/azure-local/context/context
+    #  - name: GPU Partitioning
+    #    href: /windows-server/virtualization/hyper-v/gpu-partitioning?pivots=azure-stack-hci&context=/azure-local/context/context
+    #  - name: Partition and assign GPUs to a virtual machine
+    #    href: /windows-server/virtualization/hyper-v/partition-assign-vm-gpu?pivots=azure-stack-hci&context=/azure-local/context/context
       - name: Attach GPU to Linux VM
         href: manage/attach-gpu-to-linux-vm.md
 
@@ -387,6 +387,8 @@ items:
       href: manage/manage-syslog-forwarding.md
     - name: Manage with Microsoft Defender for Cloud
       href: manage/manage-security-with-defender-for-cloud.md
+    - name: Manage security post upgrade
+      href: manage/manage-security-post-upgrade.md
 
   - name: Systems
     items:
@@ -526,6 +528,8 @@ items:
     href: manage/collect-logs.md
   - name: Troubleshoot deployment validation issues
     href: manage/troubleshoot-deployment.md
+  - name: Use the Diagnostic Support tool
+    href: manage/support-tools.md
   - name: Get support for deployment issues
     href: manage/get-support-for-deployment-issues.md
   - name: Get support for Azure Local
@@ -603,7 +607,7 @@ items:
   - name: Host networking
     items:
     - name: Network ATC overview
-      href: concepts/network-atc-overview.md?pivots=azure-stack-hci
+      href: concepts/network-atc-overview.md?pivots=azure-local
   - name: SDN
     items:
     - name: SDN technical reference
@@ -658,7 +662,7 @@ items:
       - name: Create a system with PowerShell
         href: deploy/create-cluster-powershell.md
       - name: Host networking with Network ATC
-        href: deploy/network-atc.md?pivots=azure-stack-hci
+        href: deploy/network-atc.md?pivots=azure-local
     - name: Deploy SDN 
       items:
       - name: Deploy using Windows Admin Center
@@ -730,7 +734,7 @@ items:
       - name: Manage systems with PowerShell
         href: manage/cluster-powershell.md
       - name: Manage Network ATC
-        href: manage/manage-network-atc.md?pivots=azure-stack-hci
+        href: manage/manage-network-atc.md?pivots=azure-local
       - name: Update the system
         href: manage/update-cluster.md
       - name: Manage quick restarts
@@ -779,8 +783,6 @@ items:
       href: /windows-server/storage/storage-spaces/storage-spaces-states?context=/azure-local/context/context
     - name: Collect diagnostic data
       href: manage/collect-diagnostic-data.md
-    - name: Use the Diagnostic Support tool
-      href: manage/support-tools.md
   - name: Concepts
     items:
     - name: Storage and systems

azure-local/concepts/cache.md

@@ -12,6 +12,8 @@ ms.date: 02/21/2024
 
 > Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022, Windows Server 2019
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 Storage Spaces Direct, the foundational storage virtualization technology behind Azure Stack HCI and Windows Server, features a built-in server-side cache to maximize storage performance while reducing costs. It's a large, persistent, real-time read *and* write cache that is configured automatically upon deployment. In most cases, no manual management whatsoever is required. How the cache works depends on the types of drives present.
 
 ## Drive types and deployment options

azure-local/concepts/choose-drives.md

@@ -12,6 +12,8 @@ ms.date: 02/21/2024
 
 > Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022, Windows Server 2019
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 This article provides guidance on how to choose drives to meet your performance and capacity requirements.
 
 ## Drive types

azure-local/concepts/data-collection.md

@@ -12,6 +12,8 @@ ms.date: 04/24/2023
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-22h2.md)]
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 This topic describes required data collected to keep Azure Stack HCI secure, up to date, and working as expected.
 
 Customer data, including the names, metadata, configuration, and contents of your on-premises virtual machines (VMs) is never sent to the cloud unless you turn on additional services like Azure Backup or Azure Site Recovery, or unless you enroll those VMs individually into cloud management services like Azure Arc.

azure-local/concepts/deploy-persistent-memory.md

@@ -12,6 +12,8 @@ ms.date: 04/17/2023
 
 > Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows 10
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 Persistent memory (or PMem) is a new type of memory technology that retains its content through power cycles and can be used as top-tier storage, which is why you may hear people refer to PMem as "storage-class memory" or SCM. This article provides background on persistent memory and explains how to deploy it as the top storage tier in Azure Stack HCI and Windows Server.
 
 ## What is persistent memory?

azure-local/concepts/drive-symmetry-considerations.md

@@ -12,6 +12,8 @@ ms.date: 02/22/2024
 
 > Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022, Windows Server 2019
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 Azure Stack HCI and Windows Server clusters work best when every server has exactly the same drives.
 
 In reality, we recognize this is not always practical. Today, you may buy spacious 3 TB hard drives; next year, it may become impossible to find drives that small. Therefore, some amount of mixing-and-matching is expected and supported. Keep in mind, however, that more symmetry is always better.

azure-local/concepts/fault-tolerance.md

@@ -11,6 +11,8 @@ ms.date: 04/17/2023
 
 > Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022, Windows Server 2019
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 This article explains the resiliency options available and outlines the scale requirements, storage efficiency, and general advantages and tradeoffs of each.
 
 ## Overview

azure-local/concepts/nested-resiliency.md

@@ -11,6 +11,8 @@ ms.date: 02/22/2024
 
 >Applies to: Azure Stack HCI, versions 22H2 and 21H2; Windows Server 2022 and Windows Server 2019
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 Nested resiliency is a capability of [Storage Spaces Direct](/azure-stack/hci/concepts/storage-spaces-direct-overview) in Azure Stack HCI and Windows Server. It enables a two-server cluster to withstand multiple hardware failures at the same time without loss of storage availability, so users, apps, and virtual machines continue to run without disruption. This article explains how nested resiliency works, provides step-by-step instructions to get started, and answers the most frequently asked questions.
 
 ## Before you begin

azure-local/concepts/nested-virtualization.md

@@ -12,6 +12,8 @@ ms.date: 04/17/2023
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-22h2.md)]
 
+[!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
+
 Nested virtualization is a feature that lets you run Hyper-V inside a Hyper-V virtual machine (VM). This allows you to maximize your hardware investments and gain flexibility in evaluation and testing scenarios.
 
    > [!IMPORTANT]

azure-local/concepts/network-atc-overview.md

@@ -55,13 +55,9 @@ Network ATC provides the following features:
 - **Storage adapter configuration**: Network ATC automatically configures the following components for your storage network.
 
   - Physical adapter properties
-
   - Data Center Bridging
-
   - Determines if a virtual switch is needed, and if so, creates the required virtual adapters
-
   - Maps the virtual adapters to the appropriate physical adapter
-
   - Assigns VLANs
 
   :::zone pivot="azure-local"
@@ -70,8 +66,6 @@ Network ATC provides the following features:
 
   :::zone-end
 
-<br />
-
   :::zone pivot="windows-server"
 
   - Network ATC automatically assigns IP Addresses for storage adapters.
@@ -83,11 +77,8 @@ Network ATC provides the following features:
 - **Live Migration guidelines**: Network ATC keeps you up to date with the recommended guidelines for Live Migration based on the operating system version (you can always override). Network ATC manages the following Live Migration settings:
 
   - The maximum number of simultaneous live migrations
-
   - The live migration network
-
   - The live migration transport
-
   - The maximum amount of SMBDirect (RDMA) bandwidth used for live migration
 
 - **Proxy configuration**: Network ATC can help you configure all cluster nodes with the same proxy configuration information if your environment requires it.
@@ -129,9 +120,9 @@ To get started with Network ATC, review the following articles:
 
 :::zone pivot="azure-local"
 
-- Review Network ATC defaults and example deployment options. See [Deploy host networking with Network ATC](../deploy/network-atc.md?pivots=azure-stack-hci).
+- Review Network ATC defaults and example deployment options. See [Deploy host networking with Network ATC](../deploy/network-atc.md?pivots=azure-local).
 - Configure Network ATC using PowerShell. See [Step 4: Configure host networking](../deploy/create-cluster-powershell.md#step-4-configure-host-networking).
-- Manage Network ATC after deployment. See [Manage host networking using Network ATC](../manage/manage-network-atc.md?pivots=azure-stack-hci).
+- Manage Network ATC after deployment. See [Manage host networking using Network ATC](../manage/manage-network-atc.md?pivots=azure-local).
 - [Migrate an existing cluster to Network ATC](https://techcommunity.microsoft.com/t5/networking-blog/migrate-an-existing-cluster-to-network-atc/ba-p/3843606).
 - To learn more about the latest networking announcements, build your skills, and connect with the Microsoft Edge Networking community, see the [Tech Community Networking Blog](https://techcommunity.microsoft.com/t5/networking-blog/bg-p/NetworkingBlog).