Microsoft Kills Dev Box and Bets Everything on Windows 365

Microsoft is consolidating its cloud developer story around a single product. A new Windows 11 developer configuration image for Windows 365 is now in public preview, and it ships with the tools most engineers actually open on day one. At the same time, Microsoft Dev Box, the company's previous answer to ready-to-code cloud workstations, is being parked.

A Cloud PC that boots ready to commit

The pitch is simple. The Windows 11 developer configuration image delivers a preconfigured, ready-to-code environment with tools developers already use, including Visual Studio Code, Git, GitHub CLI, Python, Node.js, and Windows Subsystem for Linux (WSL), available from first sign-in. No setup script, no chasing installers, no afternoon lost to PATH issues before the first pull request.

The framing in Microsoft's announcement is one any engineering manager will recognize. Every developer knows the story of a new machine, a fresh image, and hours lost to setup before a single line of code gets written, and that friction repeats with every onboarding, project switch, and refresh. The developer image is meant to compress that loop to a single sign-in.

Dev Box is done shipping features

The bigger news under the surface is strategic. Dev Box is now in maintenance mode, with no additional features planned, and Microsoft's investments for developer cloud environments are focused on Windows 365. Existing deployments keep working, but no new features will ship, and previously planned capabilities won't proceed to general availability.

Several roadmap items have been explicitly cut. On-behalf creation for provisioning machines for teammates, Firewall Service Tags for configuring traffic rules, and automatic developer offboarding when users leave or switch teams are no longer being developed. If your platform team was waiting on any of those, the wait is over and the answer is no.

What replaces it in Windows 365

The Build 2026 update bundles several pieces meant to give Windows 365 feature parity with what Dev Box offered, plus more. Autopilot device preparation is now available for Windows 365, automating the installation of apps and scripts on Cloud PCs through Microsoft Intune before a user ever signs in, which helps ensure a ready-to-use, compliant environment without manual setup.

For teams that already maintain custom golden images, Azure Compute Gallery support is now generally available, enabling organizations to store and manage custom images in Azure Compute Gallery and import them into Windows 365 to create Cloud PCs. More granular control is on the way. An upcoming preview will introduce expanded customization that lets teams tailor Cloud PC environments to project needs, including configuring required SDKs, CLIs, packages, build tools, repositories, and onboarding workflows, all within enterprise guardrails.

There is also a nod to shared-use scenarios. Snapshot-based reset for Windows 365 Flex, now in public preview, automatically reverts shared Cloud PCs to a clean state after each user signs out, so every user starts with a clean machine. That maps well to interns, contractors, and lab environments.

The AI angle

Microsoft is also putting models on the Cloud PC itself. For developers building AI-powered apps, select language models now run directly on the Windows 365 Cloud PC. Combined with the separately announced Execution Containers, which provide a safe environment for running AI agents, the platform is being positioned as a place to both build and host agentic workloads without round-tripping every inference to a separate service.

What it costs

Windows 365 pricing remains a flat per-user monthly fee rather than usage-based billing. Windows 365 for Business offers three tiers: a Basic machine at $31 per month with two vCPUs and 4GB of memory, a Standard machine at $41 per month with 8GB of RAM, and a Premium tier at $66 per month with four vCPUs and 16GB of RAM. Enterprise SKUs scale up further, with configurations ranging from 1 vCPU to 8 vCPUs, between 2GB and 32GB of RAM, and 64GB to 512GB of storage. The developer image itself is a configuration option layered on top of an existing Windows 365 license, not a new product line.

How to try it

Provisioning happens through Intune. The flow is: navigate to Devices, then Manage Windows 365 Cloud PCs, then Provision Cloud PCs, create a provisioning policy that selects the Windows 11 Enterprise developer configuration image, and assign it to a user group with active Windows 365 Enterprise licenses. Each target user needs a Windows 365 Enterprise Cloud PC license assigned from the Microsoft 365 Admin Center before the policy can land. Users then connect from the Windows App on desktop, laptop, tablet, or phone.

Why this matters

Two practical takeaways stand out. First, if your organization standardized on Dev Box, you now have a migration project on your calendar. Microsoft says it understands the change affects planning and will provide guidance and resources to help evaluate and move to Windows 365, but the direction is clear and the timeline for new Dev Box capabilities is permanent zero.

Second, the bet behind the consolidation is that cloud workstations are about to become the default rather than the exception. Gartner has predicted that by 2027, 20 percent of workers will use a cloud PC as their main workspace, up from 10 percent in 2019. A preconfigured developer image, GA support for custom Azure Compute Gallery images, and on-device language models are all aimed at the same goal: making a Cloud PC a credible primary environment for engineers rather than a thin-client fallback.