updates

Author: sipastak

articles/virtual-desktop/TOC.yml

@@ -94,9 +94,9 @@
         - name: Bandwidth considerations
           displayName: network, throughput, latency
           href: rdp-bandwidth.md
-        - name: Azure Stack HCI
+        - name: Azure Local
           displayName: session hosts, virtual machines, vms, on-premises, on premises
-          href: azure-stack-hci-overview.md
+          href: azure-local-overview.md
         - name: Azure Extended Zones
           displayName: session hosts, virtual machines, vms, low latency
           href: azure-extended-zones.md
@@ -114,7 +114,7 @@
       displayName: standard, host pools, session host configuration, shc, shu
       href: host-pool-management-approaches.md
     - name: Deploy Azure Virtual Desktop
-      displayName: deploy, create, get started, quickstart, host pool, application group, workspace, assign users, azure stack hci, azure extended zones
+      displayName: deploy, create, get started, quickstart, host pool, application group, workspace, assign users, azure stack hci, azure local, azure extended zones
       href: deploy-azure-virtual-desktop.md
     - name: Quickstart
       displayName: deploy, create, get started, quickstart
@@ -219,7 +219,7 @@
                       displayName: languages, language packs
                       href: windows-11-language-packs.md
         - name: Add session hosts to a host pool
-          displayName: deploy, get started, virtual machines, vms, azure stack hci, azure extended zones
+          displayName: deploy, get started, virtual machines, vms, azure stack hci, azure local, azure extended zones
           href: add-session-hosts-host-pool.md
         - name: Multimedia redirection
           items:

articles/virtual-desktop/azure-stack-hci-overview.md renamed to articles/virtual-desktop/azure-local-overview.md

@@ -93,7 +93,7 @@ To access desktops and applications from your session hosts, your users need to
 You need to join session hosts that provide desktops and applications to the same Microsoft Entra tenant as your users, or an Active Directory domain (either AD DS or Microsoft Entra Domain Services).
 
 > [!NOTE]
-> For Azure Stack HCI, you can only join session hosts to an Active Directory Domain Services domain. You can only join session hosts on Azure Stack HCI to an Active Directory Domain Services (AD DS) domain. This includes using [Microsoft Entra hybrid join](/entra/identity/devices/concept-hybrid-join), where you can benefit from some of the functionality provided by Microsoft Entra ID.
+> For Azure Local, you can only join session hosts to an Active Directory Domain Services domain. You can only join session hosts on Azure Local to an Active Directory Domain Services (AD DS) domain. This includes using [Microsoft Entra hybrid join](/entra/identity/devices/concept-hybrid-join), where you can benefit from some of the functionality provided by Microsoft Entra ID.
 
 To join session hosts to Microsoft Entra ID or an Active Directory domain, you need the following permissions:
 
@@ -170,11 +170,11 @@ For Azure, you can use operating system images provided by Microsoft in the [Azu
 - [Store and share images in an Azure Compute Gallery](/azure/virtual-machines/shared-image-galleries).
 - [Create a managed image of a generalized VM in Azure](/azure/virtual-machines/windows/capture-image-resource).
 
-Alternatively, for Azure Stack HCI you can use operating system images from:
+Alternatively, for Azure Local you can use operating system images from:
 
-- Azure Marketplace. For more information, see [Create Azure Stack HCI VM image using Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace).
-- Azure Storage account. For more information, see [Create Azure Stack HCI VM image using image in Azure Storage account](/azure-stack/hci/manage/virtual-machine-image-storage-account).
-- A local share. For more information, see [Create Azure Stack HCI VM image using images in a local share](/azure-stack/hci/manage/virtual-machine-image-local-share).
+- Azure Marketplace. For more information, see [Create Azure Local VM image using Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace).
+- Azure Storage account. For more information, see [Create Azure Local VM image using image in Azure Storage account](/azure-stack/hci/manage/virtual-machine-image-storage-account).
+- A local share. For more information, see [Create Azure Local VM image using images in a local share](/azure-stack/hci/manage/virtual-machine-image-local-share).
 
 You can deploy a virtual machines (VMs) to be used as session hosts from these images with any of the following methods:
 
@@ -184,10 +184,10 @@ You can deploy a virtual machines (VMs) to be used as session hosts from these i
 
 If your license entitles you to use Azure Virtual Desktop, you don't need to install or apply a separate license, however if you're using per-user access pricing for external users, you need to [enroll an Azure Subscription](remote-app-streaming/per-user-access-pricing.md). You need to make sure the Windows license used on your session hosts is correctly assigned in Azure and the operating system is activated. For more information, see [Apply Windows license to session host virtual machines](apply-windows-license.md).
 
-For session hosts on Azure Stack HCI, you must license and activate the virtual machines you use before you use them with Azure Virtual Desktop. For activating Windows 10 and Windows 11 Enterprise multi-session, and Windows Server 2022 Datacenter: Azure Edition, use [Azure verification for VMs](/azure-stack/hci/deploy/azure-verification). For all other OS images (such as Windows 10 and Windows 11 Enterprise, and other editions of Windows Server), you should continue to use existing activation methods. For more information, see [Activate Windows Server VMs on Azure Stack HCI](/azure-stack/hci/manage/vm-activate).
+For session hosts on Azure Local, you must license and activate the virtual machines you use before you use them with Azure Virtual Desktop. For activating Windows 10 and Windows 11 Enterprise multi-session, and Windows Server 2022 Datacenter: Azure Edition, use [Azure verification for VMs](/azure-stack/hci/deploy/azure-verification). For all other OS images (such as Windows 10 and Windows 11 Enterprise, and other editions of Windows Server), you should continue to use existing activation methods. For more information, see [Activate Windows Server VMs on Azure Local](/azure-stack/hci/manage/vm-activate).
 
 > [!NOTE]
-> To ensure continued functionality with the latest security update, update your VMs on Azure Stack HCI to the latest cumulative update by June 17, 2024. This update is essential for VMs to continue using Azure benefits. For more information, see [Azure verification for VMs](/azure-stack/hci/deploy/azure-verification?tabs=wac#benefits-available-on-azure-stack-hci).
+> To ensure continued functionality with the latest security update, update your VMs on Azure Local to the latest cumulative update by June 17, 2024. This update is essential for VMs to continue using Azure benefits. For more information, see [Azure verification for VMs](/azure-stack/hci/deploy/azure-verification?tabs=wac#benefits-available-on-azure-stack-hci).
 
 > [!TIP]
 > To simplify user access rights during initial development and testing, Azure Virtual Desktop supports [Azure Dev/Test pricing](https://azure.microsoft.com/pricing/dev-test/). If you deploy Azure Virtual Desktop in an Azure Dev/Test subscription, end users may connect to that deployment without separate license entitlement in order to perform acceptance tests or provide feedback.
@@ -235,7 +235,7 @@ Consider the following points when managing session hosts:
 
 ## Azure regions
 
-You can deploy host pools, workspaces, and application groups in the following Azure regions. This list of regions is where the *metadata* for the host pool can be stored. However, session hosts for the user sessions can be located in any Azure region, and on-premises when using [Azure Virtual Desktop on Azure Stack HCI](azure-stack-hci-overview.md), enabling you to deploy compute resources close to your users. For more information about the types of data and locations, see [Data locations for Azure Virtual Desktop](data-locations.md).
+You can deploy host pools, workspaces, and application groups in the following Azure regions. This list of regions is where the *metadata* for the host pool can be stored. However, session hosts for the user sessions can be located in any Azure region, and on-premises when using [Azure Virtual Desktop on Azure Local](azure-stack-hci-overview.md), enabling you to deploy compute resources close to your users. For more information about the types of data and locations, see [Data locations for Azure Virtual Desktop](data-locations.md).
 
 :::row:::
     :::column:::

articles/virtual-desktop/prerequisites.md

@@ -489,6 +489,11 @@
             "source_path_from_root": "/articles/virtual-desktop/multimedia-redirection.md",
             "redirect_url": "/azure/virtual-desktop/multimedia-redirection-video-playback-calls",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/virtual-desktop/azure-stack-hci-overview.md",
+            "redirect_url": "/azure/virtual-desktop/azure-local-overview",
+            "redirect_document_id": true
         }
     ]
 }