Azure Lab Services is retiring: a calm plan, not a panic
The sky is not falling. You have time, and the model you are used to does not have to change.
If your course runs on Azure Lab Services, you have probably seen the retirement notice and felt a small jolt. The good news: this is a planned move with plenty of runway, and the thing you actually valued, giving a class their own machines without building a data centre, is not going anywhere.
What you are really migrating
Strip it back and Lab Services gave you three things: a way to template a machine, a way to hand copies to a class, and a way to keep a lid on cost. Any sensible replacement has to do the same three things without asking teachers to relearn their whole workflow.
A path that keeps the familiar parts
StudentLabs deliberately keeps the model you already know. You pick an image, set the class, and share a link. Students get their own machine. Underneath, it runs on your own Azure subscription, so your existing agreements, regions and controls carry straight over.
A sane migration looks like this:
- Pick one unit for next term as a pilot, not your whole catalogue at once.
- Rebuild its image as a reusable template, or bring the one you already have.
- Run the pilot, compare the bill and the teacher effort, then roll out from there.
Retirement deadlines feel urgent, but the worst migrations are the rushed ones. Pilot small, keep the parts that work, and move the rest on your own timetable.