|
| 1 | +--- |
| 2 | +title: Azure Virtual Desktop (classic) retirement - Azure |
| 3 | +description: Information about the retirement of Azure Virtual Desktop (classic). |
| 4 | +ms.topic: conceptual |
| 5 | +author: msft-jasonparker |
| 6 | +ms.author: japarker |
| 7 | +ms.date: 09/27/2023 |
| 8 | +--- |
| 9 | + |
| 10 | +# Azure Virtual Desktop (classic) retirement |
| 11 | + |
| 12 | +> [!IMPORTANT] |
| 13 | +> This content applies to Azure Virtual Desktop (classic), which doesn't support Azure Resource Manager Azure Virtual Desktop objects. |
| 14 | +
|
| 15 | +Azure Virtual Desktop (classic) will retire on **September 30, 2026**. You should transition to Azure Virtual Desktop before that date. |
| 16 | + |
| 17 | +[Azure Virtual Desktop](../overview.md) replaces Azure Virtual Desktop (classic). Here are some of the benefits of using Azure Virtual Desktop instead of Azure Virtual Desktop (classic): |
| 18 | + |
| 19 | +- Deployments via Azure Resource Manager (ARM) |
| 20 | +- Unified resource management |
| 21 | +- Improved networking and security |
| 22 | +- Scaling and automation features |
| 23 | +- Feature availability and updates |
| 24 | + |
| 25 | +## Retirement timeline |
| 26 | + |
| 27 | +Beginning **September 30, 2023**, you'll no longer be able to create new Azure Virtual Desktop (classic) tenants. Existing Azure Virtual Desktop (classic) resources can still be managed, migrated, and are supported through **September 30, 2026**. |
| 28 | + |
| 29 | +> [!IMPORTANT] |
| 30 | +> If you have more than 500 application groups or manage multi-tenant environments, you can [request an exemption](#exemption-process). |
| 31 | +
|
| 32 | +## Required action |
| 33 | + |
| 34 | +To avoid service disruptions, migrate to Azure Virtual Desktop before September 30, 2026. Here are some articles to help you migrate: |
| 35 | + |
| 36 | +- [Migrate manually from Azure Virtual Desktop (classic)](../manual-migration.md) |
| 37 | +- [Migrate automatically from Azure Virtual Desktop (classic)](../automatic-migration.md) |
| 38 | + |
| 39 | +## Exemption process |
| 40 | + |
| 41 | +To be able to continue creating tenants in Azure Virtual Desktop (classic), you need to create an exemption. An exemption is available if you have more than 500 application groups or manage multitenant environments. To create an exemption: |
| 42 | + |
| 43 | +1. Browse to [New support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal. |
| 44 | + |
| 45 | +1. On the **Problem description** tab, complete the following information: |
| 46 | + |
| 47 | + | Parameter | Value/Description | |
| 48 | + |--|--| |
| 49 | + | Issue type | Select **Technical** from the drop-down list | |
| 50 | + | Subscription | Select a subscription containing Azure Virtual Desktop (classic) resources from the drop-down list. | |
| 51 | + | Service | Select **My services**. | |
| 52 | + | Service type | Select **Azure Virtual Desktop** from the drop-down list | |
| 53 | + | Resource | Select an Azure Virtual Desktop (classic) resource from the drop-down list. | |
| 54 | + | Summary | Enter a description of your issue. | |
| 55 | + | Problem type | Select **Issues configuring Azure Virtual Desktop (classic)** from the drop-down list. | |
| 56 | + | Problem subtype | Select **Tenant creation exemption request** from the drop-down list. | |
| 57 | + |
| 58 | +1. Complete the remaining tabs and select **Create**. |
| 59 | + |
| 60 | +## Help and support |
| 61 | + |
| 62 | +If you have a support plan and you need technical help, see [Azure Virtual Desktop (classic) troubleshooting overview, feedback, and support](troubleshoot-set-up-overview-2019.md#create-a-support-request) for information on how to create a support request. You can also ask community experts questions at [Azure Virtual Desktop - Microsoft Q&A](/answers/tags/221/azure-virtual-desktop). |
0 commit comments