AVD classic migration tidy-up

Author: dknappettmsft

articles/virtual-desktop/agent-overview.md

@@ -17,7 +17,6 @@ This article will give you a brief overview of the agent installation and update
 >[!NOTE]
 >This documentation is not for the FSLogix agent or the Remote Desktop Client agent.
 
-
 ## Initial installation process
 
 The Azure Virtual Desktop agent is initially installed in one of two ways. If you provision virtual machines (VMs) in the Azure portal and Azure Marketplace, the agent and agent bootloader are automatically installed. If you provision VMs using PowerShell, you must manually download the agent and agent bootloader .msi files when [creating an Azure Virtual Desktop host pool with PowerShell](create-host-pools-powershell.md#register-the-virtual-machines-to-the-azure-virtual-desktop-host-pool). Once the agent is installed, it installs the Azure Virtual Desktop side-by-side stack and Geneva Monitoring agent. The side-by-side stack component is required for users to securely establish reverse server-to-client connections. The Geneva Monitoring agent monitors the health of the agent. All three of these components are essential for end-to-end user connectivity to function properly.
@@ -38,7 +37,7 @@ Other important things you should keep in mind:
 - When the Geneva Monitoring agent updates to the latest version, the old GenevaTask task is located and disabled before creating a new task for the new monitoring agent. The earlier version of the monitoring agent isn't deleted in case that the most recent version of the monitoring agent has a problem that requires reverting to the earlier version to fix. If the latest version has a problem, the old monitoring agent will be re-enabled to continue delivering monitoring data. All versions of the monitor that are earlier than the last one you installed before the update will be deleted from your VM.
 - Your VM keeps three versions of the agent and of the side-by-side stack at a time. This allows for quick recovery if something goes wrong with the update. The earliest version of the agent or stack is removed from the VM whenever the agent or stack updates. If you delete these components prematurely and the agent or stack has a failure, the agent or stack won't be able to roll back to an earlier version, which will put your VM in an unavailable state.
 
-The agent update normally lasts 2-3 minutes on a new VM and shouldn't cause your VM to lose connection or shut down. This update process applies to both Azure Virtual Desktop (classic) and the latest version of Azure Virtual Desktop with Azure Resource Manager.
+The agent update normally lasts 2-3 minutes on a new VM and shouldn't cause your VM to lose connection or shut down.
 
 ## Next steps
 

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

@@ -19,7 +19,6 @@ Autoscale lets you scale your session host virtual machines (VMs) in a host pool
 When using autoscale, you can choose from two different scaling methods: power management or dynamic. To learn more about autoscale, see [Autoscale scaling plans and example scenarios in Azure Virtual Desktop](autoscale-scenarios.md).
 
 > [!NOTE]
-> - Azure Virtual Desktop (classic) doesn't support autoscale. 
 > - 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.
 > - Power management autoscaling is available in Azure and Azure Government.
 > - Dynamic autoscaling is only available in Azure and isn't supported in Azure Government.

articles/virtual-desktop/autoscale-scenarios.md

@@ -15,7 +15,6 @@ ms.custom: references_regions, docs_inherited
 Autoscale lets you scale your session host virtual machines (VMs) in a host pool up or down according to schedule to optimize deployment costs.
 
 > [!NOTE]
-> - Azure Virtual Desktop (classic) doesn't support autoscale. 
 > - You can't use autoscale and [scale session hosts using Azure Automation](set-up-scaling-script.md) on the same host pool. You must use one or the other.
 > - Power management autoscaling is available in Azure and Azure Government in the same regions you can [create host pools](create-host-pools-azure-marketplace.md) in.
 > - Dynamic autoscaling is only available in Azure and isn't supported in Azure Government.

articles/virtual-desktop/azure-ad-joined-session-hosts.md

@@ -16,7 +16,6 @@ This article will walk you through the process of deploying and accessing Micros
 
 The following known limitations may affect access to your on-premises or Active Directory domain-joined resources and you should consider them when deciding whether Microsoft Entra joined VMs are right for your environment.
 
-- Azure Virtual Desktop (classic) doesn't support Microsoft Entra joined VMs.
 - Microsoft Entra joined VMs don't currently support external identities, such as Microsoft Entra Business-to-Business (B2B) and Microsoft Entra Business-to-Consumer (B2C).
 - Microsoft Entra joined VMs can only access [Azure Files shares](create-profile-container-azure-ad.yml) or [Azure NetApp Files shares](create-fslogix-profile-container.md) for hybrid users using Microsoft Entra Kerberos for FSLogix user profiles.
 - The [Remote Desktop Store app](users/connect-windows.md?pivots=rd-store) for Windows doesn't support Microsoft Entra joined VMs.

articles/virtual-desktop/configure-adfs-sso.md

@@ -4,16 +4,14 @@ description: How to configure single sign-on for an Azure Virtual Desktop enviro
 author: dknappettmsft
 ms.custom: devx-track-azurepowershell, docs_inherited
 ms.topic: how-to
-ms.date: 06/30/2021
+ms.date: 12/03/2024
 ms.author: daknappe
 ---
+
 # Configure single sign-on for Azure Virtual Desktop using AD FS
 
 This article will walk you through the process of configuring Active Directory Federation Service (AD FS) single sign-on (SSO) for Azure Virtual Desktop.
 
-> [!NOTE]
-> Azure Virtual Desktop (Classic) doesn't support this feature.
-
 ## Prerequisites
 
 Before configuring AD FS single sign-on, you must have the following setup running in your environment:

articles/virtual-desktop/configure-host-pool-personal-desktop-assignment-type.md

@@ -3,15 +3,12 @@ title: Configure personal desktop assignment in Azure Virtual Desktop  - Azure
 description: How to configure automatic or direct assignment for an Azure Virtual Desktop personal desktop host pool.
 author: dknappettmsft
 ms.topic: how-to
-ms.date: 01/31/2024
+ms.date: 12/03/2024
 ms.author: daknappe
 ms.custom: devx-track-azurepowershell, docs_inherited
 ---
 # Configure personal desktop assignment
 
->[!IMPORTANT]
->This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/configure-host-pool-personal-desktop-assignment-type-2019.md).
-
 A personal host pool is a type of host pool that has personal desktops. Personal desktops have one-to-one mapping, which means a single user can only be assigned to a single personal desktop. Every time the user signs in, their user session is directed to their assigned personal desktop session host. This host pool type is ideal for customers with resource-intensive workloads because user experience and session performance will improve if there's only one session on the session host. Another benefit of this host pool type is that user activities, files, and settings persist on the virtual machine operating system (VM OS) disk after the user signs out.
 
 Users must be assigned to a personal desktop to start their session. You can configure the assignment type of your personal desktop host pool to adjust your Azure Virtual Desktop environment to better suit your needs. In this topic, we'll show you how to configure automatic or direct assignment for your users.

articles/virtual-desktop/configure-validation-environment.md

@@ -3,47 +3,57 @@ title: Configure a host pool as a validation environment - Azure
 description: How to configure a host pool as a validation environment to test service updates before they roll out to production.
 author: dknappettmsft
 ms.topic: how-to
-ms.date: 03/01/2023
+ms.date: 12/03/2024
 ms.author: daknappe
 ms.custom: devx-track-azurecli, docs_inherited
 ---
-# Configure a host pool as a validation environment
 
->[!IMPORTANT]
->This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/create-validation-host-pool-2019.md).
+# Configure a host pool as a validation environment
 
-Host pools are a collection of one or more identical virtual machines within Azure Virtual Desktop environment. We highly recommend you create a validation host pool where service updates are applied first. Validation host pools let you monitor service updates before the service applies them to your standard or non-validation environment. Without a validation host pool, you may not discover changes that introduce errors, which could result in downtime for users in your standard environment.
+Validation host pools let you monitor service updates before the service applies them to your standard or non-validation environment. Without a validation host pool, you may not discover changes that introduce errors, which could result in downtime for users in your standard environment. We highly recommend you create a validation host pool where service updates are applied first.
 
 To ensure your apps work with the latest updates, the validation host pool should be as similar to host pools in your non-validation environment as possible. Users should connect as frequently to the validation host pool as they do to the standard host pool. If you have automated testing on your host pool, you should include automated testing on the validation host pool.
 
-You can debug issues in the validation host pool with either [the diagnostics feature](./troubleshoot-set-up-overview.md) or the [Azure Virtual Desktop troubleshooting articles](troubleshoot-set-up-overview.md).
+This article shows you how to configure a host pool as a validation environment using the Azure portal, Azure PowerShell, or Azure CLI.
+
+> [!NOTE]
+> - We recommend that you leave the validation host pool in place to test all future updates. Validation host pools should only be used for testing, and not in production environments.
+>
+> - To keep up to date with the latest updates, see [What's new in the Azure Virtual Desktop Agent](whats-new-agent.md).
+
+## Prerequisites
 
->[!NOTE]
-> We recommend that you leave the validation host pool in place to test all future updates. Validation host pools should only be used for testing, and not in production environments.
+Before you begin, make sure you have the following:
 
-## Create your host pool
+- An Azure Virtual Desktop host pool that you want to configure as a validation environment.
 
-You can configure any existing pooled or personal host pool to be a validation host pool. You can also create a new host pool to use for validation by following the instructions in any of these articles:
-- [Tutorial: Create a host pool with Azure Marketplace or the Azure CLI](create-host-pools-azure-marketplace.md)
-- [Create a host pool with PowerShell or the Azure CLI](create-host-pools-powershell.md)
+- As a minimum, the Azure account you use must have the [Desktop Virtualization Host Pool Contributor role](rbac.md#desktop-virtualization-host-pool-contributor) built-in role-based access control (RBAC) role assigned on the host pool.
 
 ## Define your host pool as a validation environment
 
-### [Azure portal](#tab/azure-portal)
+Select the relevant tab.
+
+#### [Azure portal](#tab/azure-portal)
 
 To use the Azure portal to configure your validation host pool:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Search for and select **Azure Virtual Desktop**.
-3. In the Azure Virtual Desktop page, select **Host pools**.
-4. Select the name of the host pool you want to edit.
-5. Select **Properties**.
-6. In the validation environment field, select **Yes** to enable the validation environment.
-7. Select **Save** to apply the new settings.
 
-### [Azure PowerShell](#tab/azure-powershell)
+1. Search for and select **Azure Virtual Desktop**.
+
+1. In the Azure Virtual Desktop page, select **Host pools**.
+
+1. Select the name of the host pool you want to edit.
+
+1. Select **Properties**.
 
-If you haven't already done so, follow the instructions in [Set up the Azure Virtual Desktop PowerShell module](powershell-module.md) to set up your PowerShell module and sign in to Azure.
+1. In the validation environment field, select **Yes** to enable the validation environment.
+
+1. Select **Save** to apply the new settings.
+
+#### [Azure PowerShell](#tab/azure-powershell)
+
+If you haven't already done so, follow the instructions in [Set up the Azure Virtual Desktop PowerShell module](powershell-module.md) and sign in to Azure.
 
 Run the following PowerShell cmdlets to define the new host pool as a validation host pool. Replace the values in brackets with the values relevant to your session:
 
@@ -70,7 +80,7 @@ The results from the cmdlet should look similar to this output:
     ValidationEnvironment : True
 ```
 
-### [Azure CLI](#tab/azure-cli)
+#### [Azure CLI](#tab/azure-cli)
 
 If you haven't already done so, prepare your environment for the Azure CLI and sign in.
 
@@ -92,15 +102,5 @@ az desktopvirtualization hostpool show --name "MyHostPool" \
 ```
 ---
 
-## Update schedule
-
-Service updates happen monthly. If there are major issues, critical updates will be provided at a more frequent pace.
-
-If there are any service updates, make sure you have at least a couple of users sign in each day to validate the environment. We recommend you regularly visit our [TechCommunity site](https://techcommunity.microsoft.com/t5/forums/searchpage/tab/message?filter=location&q=wvdupdate&location=forum-board:WindowsVirtualDesktop&sort_by=-topicPostDate&collapse_discussion=true) and follow any posts with WVDUPdate or AVDUpdate to stay informed about service updates.
-
-## Next steps
-
-Now that you've created a validation host pool, you can learn how to use Azure Service Health to monitor your Azure Virtual Desktop deployment.
+## Update information
 
-> [!div class="nextstepaction"]
-> [Set up service alerts](./set-up-service-alerts.md)

articles/virtual-desktop/delegated-access-virtual-desktop.md

@@ -9,9 +9,6 @@ ms.custom: devx-track-azurepowershell, docs_inherited
 ---
 # Delegated access in Azure Virtual Desktop
 
->[!IMPORTANT]
->This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/delegated-access-virtual-desktop-2019.md).
-
 Azure Virtual Desktop has a delegated access model that lets you define the amount of access a particular user is allowed to have by assigning them a role. A role assignment has three components: security principal, role definition, and scope. The Azure Virtual Desktop delegated access model is based on the Azure RBAC model. To learn more about specific role assignments and their components, see [the Azure role-based access control overview](../role-based-access-control/built-in-roles.md).
 
 Azure Virtual Desktop delegated access supports the following values for each element of the role assignment:

articles/virtual-desktop/diagnostics-log-analytics.md

@@ -10,9 +10,6 @@ ms.custom: docs_inherited
 
 # Send diagnostic data to Log Analytics for Azure Virtual Desktop
 
->[!IMPORTANT]
->This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/diagnostics-log-analytics-2019.md).
-
 Azure Virtual Desktop uses [Azure Monitor](/azure/azure-monitor/overview) for monitoring and alerts like many other Azure services. This lets admins identify issues through a single interface. The service creates activity logs for both user and administrative actions. Each activity log falls under the following categories:
 
 | Category | Description |

articles/virtual-desktop/index.yml

@@ -100,4 +100,4 @@ landingContent:
       - linkListType: overview
         links:
           - text: Azure Virtual Desktop (classic)
-            url: ./virtual-desktop-fall-2019/index.yml
+            url: /previous-versions/azure/virtual-desktop-classic/