Microsoft Dev Box, the managed cloud developer-workstation service, is in maintenance mode and will be retired on 18 September 2028; the closing-down process begins 14 September 2026 and Microsoft points developer cloud environments to Windows 365

Microsoft has placed Microsoft Dev Box — its managed, cloud-hosted developer-workstation service — into maintenance mode and set a retirement date of 18 September 2028. The closing-down process begins on 14 September 2026. This is a long-runway deprecation, not an imminent shutoff: existing usage remains supported through the transition period. But the signal is unambiguous — no new feature development is planned, and Microsoft says its investment in developer cloud environments is now focused on Windows 365.

Where this hurts

Dev Box gives developers on-demand, preconfigured cloud workstations, provisioned by platform teams through dev centers, projects, pools and custom images and consumed through a self-service “create a dev box” flow. All of that has an end date now. Nothing stops working on 14 September 2026 — that date starts the closing-down process — but from here on the service only receives maintenance, so building new developer onboarding or scaling existing Dev Box usage is building on a platform that will be gone in 2028.

The practical trap is treating “September 2028” as far enough away to ignore. It is far away, which is exactly why Microsoft frames this as a plan your migration now notice: the identity, networking, image and licensing work to move a developer-workstation estate to a different platform is not a weekend task.

What to do

Microsoft’s recommended path is Windows 365 (Cloud PC) for virtualized developer environments. A sensible sequence:

• Inventory your Dev Box footprint — dev centers, projects, pools, custom images, and the developer workflows built on them.
• Map each scenario to Windows 365, separating the ones that transition directly from the ones that need rework.
• Validate the things Microsoft explicitly flags as different: identity, device management, networking, image, and licensing requirements for the future-state environment.
• Test replacement workflows early to reduce risk well before the 2028 retirement.

Windows 365 is positioned as the successor for virtualized developer workstations, but it is not a drop-in clone of every Dev Box concept — confirm each capability you rely on rather than assuming parity. If your workflows don’t fit Windows 365, broader options include Azure Virtual Desktop, GitHub Codespaces, or self-managed developer VMs, depending on what your developers actually need.