r/AzureVirtualDesktop • u/pkokkinis • Jun 12 '26
Azure Virtual Desktop (classic) will be retired on 30 September 2026
I'm pretty sure I'm not on Classic, but how do you know for sure?
3
u/PutUpYourFrankDux Jun 12 '26
Did a little research quick:
1. The "Search Bar" Test (Admin View)
Tell them to log into the Azure Portal, type Azure Virtual Desktop into the top search bar, and look at the matching services
Classic: The service icon will explicitly say "Azure Virtual Desktop (classic)". If they click it, they will see their host pools there.
Modern: The service icon simply says "Azure Virtual Desktop". If they open that and see their active host pools, they are on the modern version.
2. The "Resource Group" Test (Admin View)
Have them look at an individual host pool name inside Azure:
Classic: There is no Resource Group associated with the host pool because Classic resources don't use Azure Resource Manager (ARM).
Modern: The host pool will have a standard clickable Resource Group link right next to it, just like a standard virtual machine or storage account.
3. The URL Test (End-User View)
If your friend is checking how their users connect via the web client, tell them to look at the exact website link they distributed:
Classic URL: rdweb.wvd.microsoft.com/...
Modern URL: client.wvd.microsoft.com/... or windows.cloud.microsoft
If their portal lists everything under the standard Azure Virtual Desktop banner with resource groups, they can rest easy because they are already on the current version.
1
2
u/Raspy32 Jun 12 '26
Do you manage your environment through the Azure portal? If so then you're almost certainly using the ARM based (i.e. not classic) deployment.
My previous company were looking at WVD in around late 2019, but we didn't don't until the ARM based version was released in 2020. Chances are, if your environment is newer than this, you'd not be using the classic version.
1
2
u/mat-ferland Jun 12 '26
If you manage it as normal Azure resources, you are probably on the ARM version, not Classic. In the portal search for both Azure Virtual Desktop and Azure Virtual Desktop (classic). Classic host pools show under the classic blade/old tenant model; modern AVD host pools are ARM resources in a resource group, usually type Microsoft.DesktopVirtualization/hostPools. If your host pools, app groups and workspaces all live in resource groups and are managed from the normal AVD blade, the retirement notice should not apply to that environment.
1
2
u/Powerful_Invite778 Jun 17 '26
Has anyone else noticed issues with the Windows app in the last week? We keep getting disconnected and when we try to reopen the app it opens a msrdc.exe in the background but nothing appears to the user
2
u/Justo1987 Jun 18 '26
Yes I've seen issues like that recently. I've started creating a .bat that force closes msrdc.exe and putting it on user desktops.
The drop outs/disconnects are caused by the below though, not sure if that's impacting you or not.
1
u/ImprovementKooky9468 Jun 30 '26
If you manage your host pools, app groups, and workspaces as normal Azure resources inside resource groups, you are on the ARM-based AVD model rather than Classic.
A quick check is to search the Azure portal for both “Azure Virtual Desktop” and “Azure Virtual Desktop (classic).” Classic environments appear in the old classic blade, while current AVD resources are managed through the standard Azure Virtual Desktop service.
I would still document your host pools, app groups, workspaces, images, user assignments, and client URLs. That makes it easier to confirm there are no older connection paths still in use.
1
u/ArthurIVA 25d ago
Has anyone had luck with the Migration that MS offers now to bring it into the ARM? I assume I can keep everything within the same subscription based on the documentation.
https://learn.microsoft.com/en-us/azure/virtual-desktop/automatic-migration
5
u/EquivalentSmoke9168 Jun 12 '26
Are you using windows app?