Recently I set up Azure Virtual Desktop on Windows LTSC to support a small set of older applications we still need from time to time. It was the kind of project that looks, at first glance, like a straightforward compatibility exercise, but in practice it turned into a useful reminder of how much institutional computing is really about continuity.
The problem was familiar enough. We have a few applications that are still needed for specific workflows, but which do not fit neatly into the present-day desktop environment. They are not important enough to justify a full modernization project, but they are also not obsolete enough to disappear. They occupy that awkward middle ground familiar to anyone who works in higher-ed IT: software that is technically legacy, operationally necessary, and politically difficult to retire.
Azure Virtual Desktop turned out to be a good fit because it let us isolate that old software from the main environment without abandoning it entirely. Windows LTSC made sense for the same reason. It is not a platform choice driven by novelty or elegance. It is a stability choice. When your goal is to keep a few older applications available without dragging the rest of the environment backward with them, boring is a feature.
What I found interesting about the project was how much of the work had very little to do with the applications themselves. The real work was in deciding what needed to be preserved, what could be contained, and what could be allowed to remain a little out of sight. There is always a temptation in infrastructure work to treat old software as a temporary embarrassment, something to be hidden until the institution finally upgrades. But the truth is that many organizations rely on a long tail of tools that are not going away on any reasonable schedule. The right response is not denial; it is containment.
That is where virtual desktops become more than a convenience. They become an architectural way of acknowledging the past without letting it spread. You create a controlled environment for the things that still matter, give them a bounded place to live, and keep the main system cleaner as a result. In that sense, virtualization is not just about efficiency. It is about narrative management. It says: this still exists, but it no longer defines the whole desktop.
There is also a quieter operational benefit. When older software is forced into the same space as the rest of the modern environment, it often creates a constant low-level tax: compatibility exceptions, documentation gaps, user confusion, and support ambiguity. Moving it into a dedicated virtual environment reduces that friction. It also makes the support story simpler, which is often the difference between something being sustainable and something being tolerated.
I like projects like this because they are honest about the reality of institutional IT. Not every problem gets solved by replacement. Sometimes the best move is to create a stable bridge between what an institution still needs and what it is otherwise trying to become. That is less dramatic than a full migration, but usually more useful.
In the end, the value of the Azure Virtual Desktop setup was not just that the old applications kept running. It was that they kept running in a way that did not require the rest of the environment to pretend it was still 2012.