Azure Lab Services retires 2027-06-28. The hour quotas, the Teams roster and the pay-per-hour price do not come with you.

Lab Services was built for classes: pay for the hours students use, cap each student's hours, sync the roster from Teams or the LMS. The alternatives are built for employees. This page is about that gap, and it is written for the small training provider as much as the university.

The dates

• "Azure Lab Services will be retired on June 28, 2027 … After June 28, 2027, Azure Lab Services won't be supported, and you won't have access to your lab accounts, lab plans, or labs." (retirement guide)
• New customers have been blocked since 2024-07-15.

What is not carried over

Two source classes, never blurred: the vendor's own docs are authoritative; community reports are real, dated and linked, but not vendor-confirmed, and they are labelled that way.

From the vendor's published docs

• Teams: "although other solutions don't offer Teams integration, a comparable experience can be achieved by embedding a lab URL within a Teams channel" (source).
• Core limits: "your Azure subscription core limits can't be transferred" to the replacement.
• Tooling: "Partners might provide migration tooling to automatically migrate labs". Microsoft's own scripts are for clean-up.
• Images: "Azure Lab Services only exports specialized images", while Azure Virtual Desktop requires multi-session Marketplace images.

The price trap

• Lab Services bills by the hour, bundling "compute, IP, network, snapshots and disks costs", and a shut-down machine is not billed (pricing). Storage "is offered as a complimentary service".
• Windows 365 Enterprise, a named alternative, is flat per user: $41 per user per month (2 vCPU/8 GB) or $66 (4 vCPU/16 GB) (pricing). A learner who uses 10 hours a month now costs $41.
• Microsoft's own caution: "Dedicated virtual machines with persistent storage might not be as cost efficient with other lab solutions."

Reported by users, not confirmed by the vendor

• A small UK training provider was told, in effect, it is too small: "We have approached the Microsoft recommended partners, however they have all but said we are too small to be of commercial interest" (2026-03-05, unresolved).
• Teams integration broken for weeks, blocking a semester of labs (2026-01, unresolved).
• An exported lab VHD would not boot in Hyper-V during an attempt to move off (2025-12-11, unresolved).

Check your own setup

Zero dependencies and offline: it reads a Resource Graph export you produce. It never asks for, stores or transmits a credential: you run it with your own login, and nothing leaves your machine.

az graph query -q "resources | where type =~ 'microsoft.labservices/labs' | project name, resourceGroup, location, properties" --first 1000 -o json > labs.json
node check.js labs.json
node check.js --demo

The part nobody checks

A lab migration is judged on the first morning of term, not the day the new platform is created. Before cutover, a real learner account has to sign in, get the right image, hit its hour limit, and be stopped. The roster has to be right before class, not after the first complaint. Rehearse one full class week on the new platform with real accounts.

If you would rather not do it yourself

We take this on as fixed scope, and we will say plainly that you would be among our first customers for this particular engagement. What we bring is the breakage map above and a hard habit of proving the new setup works rather than assuming it.

• Lab exit plan, fixed price. Made for small providers as much as universities. We run the checker, price your real usage on the alternatives (Windows 365, Azure Virtual Desktop, DevTest Labs or a partner platform), and hand back a recommendation with the monthly cost, what replaces quotas and roster sync, and an image plan.
• Move and rehearse, fixed price. We build the new lab environment, rebuild images, quotas and rosters, and run a rehearsal class week with real accounts before term.