Visual Studio Online Gets a New Name: Visual Studio Codespaces

Microsoft just renamed one of its cloud products again, and this time the new name actually tells you something useful. Visual Studio Online — the cloud-hosted development environment service — is now Visual Studio Codespaces. If you’ve never heard of Visual Studio Online, don’t worry, you weren’t missing much attention from Microsoft’s marketing team either. The old name was easy to confuse with Azure DevOps (which used to be called Visual Studio Team Services, because naming things is apparently hard for everyone). Codespaces is a much clearer signal of what the product actually does.

So what is it? At its core, Visual Studio Codespaces spins up a full development environment in the cloud — compute, a configured container, your source, and an editor experience (either through the browser or hooked into a local VS Code install) — so you can start coding without setting up a machine first. Clone a repo, get a codespace, and you’re writing code in minutes instead of fighting with dependency installs, SDK versions, and “works on my machine” drift.

Why this matters more than a name change

On its own, a rename is a minor story. But it’s worth paying attention to because it tells you where Microsoft thinks development is heading. Local machine setup has always been one of the most annoying parts of onboarding onto a new project — different OS quirks, different toolchain versions, that one environment variable nobody documented. Pushing the entire dev environment into the cloud, provisioned from a config file checked into the repo, removes a huge amount of that friction. New teammate joins the project? They get a working environment in the time it takes to spin up a container, not the half-day it used to take to get their laptop configured.

There’s also an obvious play here around Microsoft’s broader cloud strategy. Every minute a developer spends coding in an Azure-hosted container is a minute of Azure consumption, and it deepens the tie between VS Code (already extremely popular) and Microsoft’s own infrastructure. That’s a smart, if unsurprising, business move.

The bigger question is whether cloud-hosted dev environments become a mainstream habit or stay a niche option for specific use cases — quick prototyping, ephemeral review environments, onboarding, working from underpowered hardware. Right now it still feels like a nice-to-have rather than a replacement for a local setup, especially for anyone doing heavy builds, GPU work, or anything latency-sensitive where a local machine still wins.

Still, this space is clearly heating up. The idea of “environment as code” — where your dev setup is defined declaratively and reproducible on demand — has been gaining traction for a while, and container-based tooling has made it much more practical than it used to be. I wouldn’t be surprised if this idea shows up in other developer tools before the year is out, especially anywhere that already leans on containers and repo-based configuration. For now, Codespaces is a decent name for a genuinely useful idea, even if most developers haven’t tried it yet.