Skip to content

Commit 3cb5770

Browse files
authored
Merge pull request #202703 from webreidi/patch-2
Add notice
2 parents 4a2bca9 + f0457ca commit 3cb5770

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,13 @@ manager: femila
1212
>[!IMPORTANT]
1313
>This content applies to Azure Virtual Desktop (classic), which doesn't support Azure Resource Manager Azure Virtual Desktop objects.
1414
15+
>[!IMPORTANT]
16+
>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.
17+
>
18+
>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).
19+
>
20+
>Learn about how to create a host pool in Azure Virtual Desktop at [Tutorial: Create a host pool](../create-host-pools-azure-marketplace.md).
21+
1522
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 app groups that are used to publish remote desktop and remote application resources to users. With a tenant, you can build host pools, create app groups, assign users, and make connections through the service.
1623

1724
In this tutorial, learn how to:

0 commit comments

Comments
 (0)