|
| 1 | +--- |
| 2 | +title: Azure Virtual Desktop (classic) product support - Azure |
| 3 | +description: An overview for Azure Virtual Desktop (classic) product support. |
| 4 | +author: msft-jasonparker |
| 5 | +ms.topic: troubleshooting |
| 6 | +ms.date: 09/15/2023 |
| 7 | +ms.author: japarker |
| 8 | +manager: femila |
| 9 | +--- |
| 10 | +# Azure Virtual Desktop (classic) product support |
| 11 | + |
| 12 | +>[!IMPORTANT] |
| 13 | +>This content applies to Azure Virtual Desktop (classic), which doesn't support Azure Resource Manager Azure Virtual Desktop objects. If you're trying to manage Azure Resource Manager Azure Virtual Desktop objects, see [this article](../troubleshoot-set-up-overview.md). |
| 14 | +
|
| 15 | +This article provides an overview of the product support for Azure Virtual Desktop (classic). |
| 16 | + |
| 17 | +## Retirement Announcement |
| 18 | + |
| 19 | +Azure Virtual Desktop (classic) will retire on September 30th, 2026 and it is recommended to transition to Azure Virtual Desktop by that date. |
| 20 | + |
| 21 | +Azure Virtual Desktop fully replaces Azure Virtual Desktop (classic). Azure Virtual Desktop includes, but isn’t limited to, the following benefits: |
| 22 | +- Deployments via Azure Resource Manager |
| 23 | +- Unified resource management |
| 24 | +- Improved networking and security |
| 25 | +- Scaling and automation features |
| 26 | +- Feature availability and updates |
| 27 | + |
| 28 | +### Retirement timeline |
| 29 | + |
| 30 | +Beginning September 30th 2023, customers will no longer be able to create new Azure Virtual Desktop (classic) tenants. Existing Azure Virtual Desktop (classic) resources can still be managed, migrated, and supported through September 30th 2026. |
| 31 | + |
| 32 | +> [!IMPORTANT] |
| 33 | +> Customers who have more than 500 application groups or manage multi-tenant (B2B) environments can request an exception (outlined at the end of this message). |
| 34 | +
|
| 35 | +### Required action |
| 36 | + |
| 37 | +To avoid service disruptions, please follow our instructions to migrate to Azure Virtual Desktop by September 30th 2026. |
| 38 | +- [Migrate manually from Azure Virtual Desktop (classic)](../manual-migration.md) |
| 39 | +- [Migrate automatically from Azure Virtual Desktop (classic)](../automated-migration.md) |
| 40 | + |
| 41 | +### Help and support |
| 42 | + |
| 43 | +If you have questions, get answers from community experts in [Azure Virtual Desktop - Microsoft Q&A](https://learn.microsoft.com/en-us/answers/tags/221/azure-virtual-desktop). If you have a support plan and you need technical help, please create a support request. |
| 44 | + |
| 45 | +> [!div class="nextstepaction"] |
| 46 | +> |
| 47 | +> [Create Support Request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) |
| 48 | +
|
| 49 | +1. For _Issue type_, select **Technical**. |
| 50 | +2. For _Subscription_, select your subscription. |
| 51 | +3. For _Service_, select **My services**, then select **Azure Virtual Desktop**. |
| 52 | +4. For _Summary_, type a description of your issue. |
| 53 | +5. For _Problem type_, select **Issues configuring Azure Virtual Desktop (classic)**. |
| 54 | +6. For _Problem subtype_, select the item which most describes your issue. |
| 55 | + |
| 56 | +### Exemption process |
| 57 | + |
| 58 | +> [!div class="nextstepaction"] |
| 59 | +> |
| 60 | +> [Create Support Request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) |
| 61 | +
|
| 62 | +1. For _Issue type,_ select **Technical**. |
| 63 | +2. For _Subscription_, select your subscription. |
| 64 | +3. For _Service_, select **My services**, then select **Azure Virtual Desktop**. |
| 65 | +4. For _Summary_, type **Exemption for AVD classic tenant creation**. |
| 66 | +5. For _Problem type_, select **Issues configuring Azure Virtual Desktop (classic)**. |
| 67 | +6. For _Problem subtype_, select **Tenant creation exemption request**. |
0 commit comments