Merge pull request #247941 from dknappettmsft/dknappettmsft-patch-1

AVD classic remove statement about not being able to create tenants

Author: prmerger-automator[bot]

articles/virtual-desktop/virtual-desktop-fall-2019/tenant-setup-azure-active-directory.md

@@ -13,11 +13,9 @@ manager: femila
 >This content applies to Azure Virtual Desktop (classic), which doesn't support Azure Resource Manager Azure Virtual Desktop objects.
 
 >[!IMPORTANT]
->Starting July 28, 2022, you'll no longer be able to create new tenants in Azure Virtual Desktop (classic). You can still manage your existing Azure Virtual Desktop (classic) environments including adding new session hosts, but all new environments must be done in Azure Virtual Desktop.
->
 >You can find more information about how to migrate from Azure Virtual Desktop (classic) to Azure Virtual Desktop at [Migrate automatically from Azure Virtual Desktop (classic)](../automatic-migration.md). 
 >
->Learn about how to create a host pool in Azure Virtual Desktop at [Tutorial: Create a host pool](../create-host-pools-azure-marketplace.md).
+>Try Azure Virtual Desktop by following our [Tutorial: Create and connect to a Windows 11 desktop with Azure Virtual Desktop](../tutorial-create-connect-personal-desktop.md).
 
 Creating a tenant in Azure Virtual Desktop is the first step toward building your desktop virtualization solution. A tenant is a group of one or more host pools. Each host pool consists of multiple session hosts, running as virtual machines in Azure and registered to the Azure Virtual Desktop service. Each host pool also consists of one or more application groups that are used to publish desktop and application resources to users. With a tenant, you can build host pools, create application groups, assign users, and make connections through the service.