The Azure Lab Services retirement takes effect on June 28, 2027, and after that date your lab accounts, lab plans, and labs are no longer accessible. Windows 365 and Azure Virtual Desktop can take over most Windows training labs, but several Lab Services features do not carry over, including per-student usage quotas, the Teams and Canvas integrations, and Linux desktops. This post covers what stops, what carries over, what needs a different service, and what your retirement plan should settle before the spring 2027 term.
What stops on the retirement date and what survives
The Azure Lab Services retirement applies to the entire service. Microsoft’s retirement guide states that it covers labs built on both lab accounts and lab plans, and that after June 28, 2027 “you won’t have access to your lab accounts, lab plans, or labs.” Saved Azure Compute Gallery images remain accessible, along with the gallery itself.
New customer sign-ups closed on July 15, 2024, and Microsoft states that “New lab accounts cannot be created.” Subscriptions active between July 2023 and July 2024 count as existing customers and can still create lab plans. Support continues until the retirement date, including fixes for blocking bugs and security issues, through a support request in the Azure portal or the Microsoft Q&A community forums.
Export the lab templates you intend to keep as Azure Compute Gallery images now, and ask students to keep their work outside the lab VMs. In most United States academic calendars, June 28 falls after the spring term, so spring 2027 is likely your last full term on Lab Services.
Where Microsoft points you instead
Microsoft’s current retirement guide names Azure Virtual Desktop and Windows 365 as the Microsoft replacements. Earlier versions also listed Azure DevTest Labs and Microsoft Dev Box, but the August 18, 2026 update dropped them.
Azure Virtual Desktop is a virtual desktop service for full desktop and app virtualization on your own Azure infrastructure, and Microsoft’s guide states that it supports Microsoft Entra ID joined CPU/GPU-based virtual machines, images from Azure Marketplace or an Azure Compute Gallery, management through Microsoft Intune, and multi-session. Windows 365 provides subscription-licensed Cloud PCs that are also Entra ID joined and Intune managed. Windows 365 Flex is the new name for Windows 365 Frontline, renamed in May 2026, and it runs in a Dedicated mode or a Shared mode. Microsoft states that both add browser-based web access and remote control access, with help through the usual Microsoft support channels.
The guide also lists Azure partner solutions, which it describes as education-focused solutions supporting large disks, cost controls, LMS integrations, over-the-shoulder monitoring, and student admin access, with region selection for low latency and data residency requirements. Partners also offer delivery through a REST API or shareable URLs, and publish transition guides. This post does not evaluate these non-Microsoft products.
What carries over and what needs rework
The features that do not carry over are mostly instructor-facing controls, so the gaps affect course delivery more than infrastructure. Microsoft’s guide acknowledges that some features “might require a paradigm shift.”
| Carries over to Windows 365 or Azure Virtual Desktop | Needs rework or a different service |
| Windows 10 and Windows 11 client labs | Linux desktop labs. Microsoft lists Windows operating systems only for both services. |
| GPU labs, using Windows 365 GPU Cloud PCs or GPU-based Azure Virtual Desktop VMs | Per-student usage quotas. Microsoft documents no learner hour limits for either service. |
| Schedules and idle shutdown through Azure Virtual Desktop autoscale, or Windows 365 Flex Dedicated, which powers off inactive Cloud PCs | Teams integration and the Canvas LMS integration. Microsoft suggests embedding a lab URL in a Teams channel, combined with auto-scaling or dynamic virtual machine creation. |
| Azure Compute Gallery as an image source | Lab templates as exported. Lab Services exports specialized images, and Windows 365 requires generalized images built on Generation 2. |
| Dedicated virtual machines with persistent storage (Windows 365 Enterprise, Flex Dedicated, Azure Virtual Desktop personal host pools) | Students signing in with personal accounts. Both services require a member or guest identity in your Microsoft Entra ID tenant. |
| Advanced networking to on-premises resources | Windows Server labs on Windows 365, which accepts Windows 10 and Windows 11 Enterprise images. |
| Multi-session sharing on Azure Virtual Desktop pooled host pools, which can reduce cores needed | Azure subscription core limits, which Microsoft states “can’t be transferred” and must be requested again. |
| Consumption-based compute billing on Azure Virtual Desktop | Storage that Lab Services includes at no charge under its consumption-based model, where you pay only for active usage. |
On a phone, scroll the table sideways to see both columns.
Images need the most planning. Microsoft recommends evaluating whether to recreate an image when you move to a Generation 2 VM image, set right-sized disks, generalize for Azure Virtual Desktop, or adopt a supported Azure Marketplace image. Windows 365 accepts custom images that are Windows 10 or Windows 11 Enterprise, Generation 2, generalized, and single-session. Based on those requirements, Windows Pro, Education, Generation 1, or Linux templates will need a rebuild. Microsoft notes that new labs are often more efficient, with options such as a lower storage tier giving cheaper storage when VMs are off.
Which of your labs carry over, and which need a rebuild or a different service?
We can inventory your Lab Services estate and map each lab to the service that fits, before spring 2027 scheduling begins.
Matching labs to services
Most Lab Services estates hold more than one kind of lab. The pairings below are WME’s reading of Microsoft’s documentation rather than Microsoft guidance.
Semester Windows courses. Azure Virtual Desktop pooled host pools fit where students hold eligible licenses, which Microsoft lists as including Microsoft 365 A3, A5, or Student Use Benefit. Personal host pools or Windows 365 Flex Dedicated suit courses needing a persistent desktop.
GPU courses. Windows 365 GPU Cloud PCs come in fixed sizes, while GPU-based Azure Virtual Desktop VMs let you choose the size. Microsoft states that GPU Cloud PCs don’t support nested virtualization.
Linux and Hyper-V bootcamps. Microsoft documents nested virtualization on Windows 365 Enterprise Cloud PCs with 4 vCPU or more, which supports the Windows Subsystem for Linux and Hyper-V for single-learner exercises. For full Linux desktops, evaluate Azure DevTest Labs, whose documentation covers training labs with Windows or Linux environments. The retirement guide no longer lists it, so confirm the fit first.
Where it breaks
Raise three limits with stakeholders before choosing a platform, because they change how courses run.
Learner hour limits are one. Lab Services gives each student a quota of lab hours, while Windows 365 Flex limits concurrent sessions, and Microsoft documents no per-student equivalent for either service. A Microsoft Q&A answer agrees, noting that DevTest Labs does not enforce hours per learner without custom scripts or automation. Agree with faculty whether schedules and auto-shutdown are acceptable substitutes.
Identity is another. Microsoft states that Azure Virtual Desktop doesn’t support personal Microsoft accounts. External identities are generally available for both, but each external user must be invited into your tenant, and hosts must run Windows 11 Enterprise 24H2 or later with the September 2025 cumulative update. For thousands of students on personal accounts, that is a policy decision for identity administrators as well as a technical change.
Migration is the third. Microsoft states that partners might provide migration tooling and documents no automatic migration of its own. Its Azure Lab Services Retirement Scripts repository provides automation scripts for bulk cleanup, and because core limits do not transfer, Microsoft advises you to request capacity early and incrementally.
Building the retirement plan
A Lab Services retirement plan is mostly an inventory, and each item carries lead time, so start before course scheduling.
Inventory existing labs and usage patterns. The Azure portal shows each lab’s region, operating system, VM count, size, and image source. Review lab usage trends before requesting the same core limits.
Decide on interim lab plans. Where you don’t need advanced networking, Microsoft recommends lab plans for faster VM start and creation times, a wider range of VM sizes, updated hardware, and more control over regions.
Settle identities and licensing. Confirm who holds eligible licenses and Entra ID accounts, and who needs a guest invitation.
Run a pilot course, then cut over. Use it to confirm images, sign-in, and shutdown behavior.
Delete unused Azure Lab Services resources. Microsoft notes that deprovisioning them frees cores, reduces costs from unexpected lab VMs running, and reduces security surface area. In advanced networking labs it also frees IP addresses and address space, and for domain-joined resources it cleans up orphaned entries in Active Directory.
WME assesses Lab Services estates against Windows 365, Azure Virtual Desktop, and other Microsoft options, and maps each lab to the service that fits. To have that inventory done before spring 2027 scheduling, request an assessment and we will scope it against what you run.
A Lab Services retirement plan is mostly an inventory.
Have it done before spring 2027 scheduling. We’ll scope the assessment against what you actually run.
