Merge pull request #16319 from alkohli/12-azlreb

Updating docfx.json and zone pivot definition file to reflect new bra…

Author: Jill Grant

azure-local/concepts/sdn-multisite-overview.md

@@ -6,11 +6,13 @@ ms.topic: conceptual
 author: alkohli
 ms.subservice: core-os
 zone_pivot_groups: windows-os
-ms.date: 11/06/2024
+ms.date: 11/12/2024
 ---
 
 # What is SDN Multisite?
 
+:::zone pivot="azure-local"
+
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
 ::: zone-end
@@ -25,7 +27,7 @@ This article provides an overview of SDN Multisite, including its benefits and c
 
 SDN Multisite allows you to expand the capabilities of traditional SDN deployed at different physical locations. SDN Multisite enables native Layer 2 and Layer 3 connectivity across different physical locations for virtualized workloads. In this article, all references to sites mean physical locations.
 
-:::zone pivot="azure-stack-hci"
+:::zone pivot="azure-local"
 
 For information about how to manage SDN Multisite, see [Manage SDN Multisite for Azure Local](../manage/manage-sdn-multisite.md?pivot=azure-stack-hci).
 
@@ -55,9 +57,9 @@ The SDN Multisite feature currently has a few limitations:
 
 ## Multisite peering
 
-:::zone pivot="azure-stack-hci"
+:::zone pivot="azure-local"
 
-Multisite requires peering between sites, which is initiated like virtual network peering. A connection is automatically initiated on both sites via Windows Admin Center. Once a connection is established, peering becomes successful. For instructions about how to establish peering, see [Establish peering](../manage/manage-sdn-multisite.md?pivot=azure-stack-hci#establish-peering).  
+Multisite requires peering between sites, which is initiated like virtual network peering. A connection is automatically initiated on both sites via Windows Admin Center. After a connection is established, peering becomes successful. For instructions about how to establish peering, see [Establish peering](../manage/manage-sdn-multisite.md?pivot=azure-stack-hci#establish-peering).  
 
 ::: zone-end
 
@@ -95,7 +97,7 @@ In a multisite SDN environment, one site is designated as the primary and the ot
 
 When you enable SDN Multisite, not all resources from each site are synchronized across all sites. Here are the lists of resources that are synchronized and that remain unsynchronized.
 
-:::zone pivot="azure-stack-hci"
+:::zone pivot="azure-local"
 
 - **Synchronized resources**
 
@@ -184,14 +186,14 @@ SDN multisite doesn't sync local resources such as gateway connections across si
 
 ## Next steps
 
-:::zone pivot="azure-stack-hci"
+:::zone pivot="azure-local"
 
 [Manage SDN Multisite for Azure Local](../manage/manage-sdn-multisite.md?pivot=azure-stack-hci)
 
 ::: zone-end
 
 :::zone pivot="windows-server"
 
-[Manage SDN Multisite for Azure Local](../manage/manage-sdn-multisite.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking)Local
+[Manage SDN Multisite for Azure Local](../manage/manage-sdn-multisite.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking)
 
 ::: zone-end

azure-local/docfx.json

@@ -46,7 +46,8 @@
       "ms.service": "azure-stack-hci",
       "titleSuffix": "Azure Stack HCI",
       "feedback_product_url": "https://feedback.azure.com/d365community/forum/74a4b1b9-0725-ec11-b6e6-000d3a4f07b8",
-      "feedback_help_link_url": "https://learn.microsoft.com/answers/tags/6/azure-stack-hci"
+      "feedback_help_link_url": "https://learn.microsoft.com/answers/tags/6/azure-stack-hci",
+      "zone_pivot_group_filename": "../azure-stack/zone-pivot-groups.json"
     },
     "fileMetadata": {},
     "template": []

azure-stack/zone-pivot-groups.yml

@@ -78,8 +78,8 @@ groups:
   title: Products
   prompt: "Choose your product:"
   pivots:
-  - id: azure-stack-hci
-    title: Azure Stack HCI
+  - id: azure-local
+    title: Azure Local
   - id: windows-server
     title: Windows Server
 # BELOW: entries inherited from github.com/microsoftdocs/azure-docs-pr/articles/zone-pivot-groups.yml for reuse.