Merge pull request #271890 from sipastak/autoscale-hci-2

Autoscale for HCI PREVIEW

Author: prmerger-automator[bot]

articles/virtual-desktop/autoscale-create-assign-scaling-plan.md

@@ -3,7 +3,7 @@ title: Create and assign an autoscale scaling plan for Azure Virtual Desktop
 description: How to create and assign an autoscale scaling plan to optimize deployment costs.
 author: Heidilohr
 ms.topic: how-to
-ms.date: 02/28/2024
+ms.date: 04/11/2024
 ms.author: helohr
 manager: femila
 ms.custom: references_regions, devx-track-azurepowershell
@@ -16,9 +16,9 @@ To learn more about autoscale, see [Autoscale scaling plans and example scenario
 
 >[!NOTE]
 > - Azure Virtual Desktop (classic) doesn't support autoscale. 
-> - Autoscale doesn't support Azure Virtual Desktop for Azure Stack HCI.
 > - You can't use autoscale and [scale session hosts using Azure Automation and Azure Logic Apps](scaling-automation-logic-apps.md) on the same host pool. You must use one or the other.
 > - Autoscale is available in Azure and Azure Government.
+> - Autoscale support for Azure Stack HCI with Azure Virtual Desktop is currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 For best results, we recommend using autoscale with VMs you deployed with Azure Virtual Desktop Azure Resource Manager templates or first-party tools from Microsoft.
 

articles/virtual-desktop/azure-stack-hci-overview.md

@@ -4,7 +4,7 @@ description: Learn about using Azure Virtual Desktop with Azure Stack HCI, enabl
 ms.topic: conceptual
 author: dknappettmsft
 ms.author: daknappe
-ms.date: 01/24/2024
+ms.date: 04/11/2024
 ---
 
 # Azure Virtual Desktop with Azure Stack HCI
@@ -76,9 +76,7 @@ Azure Virtual Desktop with Azure Stack HCI has the following limitations:
 - You can't use some Azure Virtual Desktop features when session hosts running on Azure Stack HCI, such as:
 
     - [Azure Virtual Desktop Insights](insights.md)
-    - [Autoscale](autoscale-scaling-plan.md)
     - [Session host scaling with Azure Automation](set-up-scaling-script.md)
-    - [Start VM On Connect](start-virtual-machine-connect.md)
     - [Per-user access pricing](licensing.md)
 
 - Each host pool must only contain session hosts on Azure or on Azure Stack HCI. You can't mix session hosts on Azure and on Azure Stack HCI in the same host pool.

articles/virtual-desktop/start-virtual-machine-connect.md

@@ -3,15 +3,19 @@ title: Set up Start VM on Connect for Azure Virtual Desktop
 description: How to set up the Start VM on Connect feature for Azure Virtual Desktop to turn on session host virtual machines only when they're needed.
 author: Heidilohr
 ms.topic: how-to
-ms.date: 03/14/2023
+ms.date: 04/11/2024
 ms.author: helohr
 ms.custom: subject-rbac-steps
 ---
 # Set up Start VM on Connect
 
+> [!IMPORTANT]
+> Start VM on Connect for Azure Stack HCI with Azure Virtual Desktop is currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+
 Start VM On Connect lets you reduce costs by enabling end users to turn on their session host virtual machines (VMs) only when they need them. You can then turn off VMs when they're not needed.
 
-You can configure Start VM on Connect for personal or pooled host pools using the Azure portal or PowerShell. Start VM on Connect is a host pool setting.
+You can configure Start VM on Connect for session hosts on Azure and Azure Stack HCI in personal or pooled host pools using the Azure portal or PowerShell. Start VM on Connect is a host pool setting.
 
 For personal host pools, Start VM On Connect will only turn on an existing session host VM that has already been assigned or will be assigned to a user. For pooled host pools, Start VM On Connect will only turn on a session host VM when none are turned on and additional VMs will only be turned on when the first VM reaches the session limit.