Setting up a new developer's machine has always taken time — installing VS Code, Git, configuring WSL, getting Python and Node.js to the right versions, cloning the right repos. For organisations running cloud-first development, Microsoft announced at Build 2026 a new option that eliminates all of that: a Windows 11 developer configuration image for Windows 365, now in public preview. From the moment a developer signs in to their Cloud PC, the tools are already there.
What Comes Pre-installed
The Windows 11 developer configuration image for Windows 365 is a gallery image that includes the following tools, configured and ready to use from first sign-in:
Visual Studio Code
Ready to open, extensions installable
Git
Version control configured on Windows
GitHub CLI
gh commands available immediately
Python
Installed on both Windows and WSL
Node.js
Installed on both Windows and WSL
WSL (Ubuntu)
Windows Subsystem for Linux, configured
Developers can navigate across Windows and Linux via WSL, local and cloud, and AI workloads all from the same starting point. For teams building AI-powered applications, select language models can now run directly on the Windows 365 Cloud PC — extending the ready-to-code experience to AI workloads.
Why This Matters for IT and Engineering Teams
The developer configuration image solves three real problems that IT and engineering managers deal with regularly:
Onboarding time
New developers currently spend hours or days getting their environment to a working state. A pre-configured Cloud PC reduces that to the time it takes to provision a Windows 365 licence and sign in — measured in minutes, not days.
Environment consistency
Every developer starts from the same baseline. The "it works on my machine" problem does not go away entirely, but it starts from a consistent image rather than years of accumulated personal machine configuration.
Security and manageability
Code and repositories live on the Cloud PC, not on a personal laptop that could be lost, stolen, or compromised. The environment is managed by your organisation through Windows 365, Intune, and Entra ID — the same policies that govern your other Cloud PCs.
Availability and Requirements
The developer configuration image is available for:
- Windows 365 Enterprise
- Windows 365 Flex — Dedicated mode
It is not supported on 2 vCPU or GPU licences. The image requires nested virtualisation (needed for WSL), and those SKUs do not support it. Developers who need this image will need a 4 vCPU or higher Windows 365 licence.
Preview limitations to be aware of
- Not for production workloads — this is a public preview gallery image. Your organisation is responsible for managing third-party applications, monitoring for vulnerabilities, applying security updates, and ensuring compliance.
- Pre-installed apps are not Intune-manageable — the third-party developer tools (VS Code, Git, Node.js, Python, etc.) are not currently deployable or updateable via Intune as packaged applications. If you need Intune-based application lifecycle management for these tools, uninstall the pre-installed versions and redeploy them through Intune.
- Not supported on 2 vCPU or GPU licences — nested virtualisation required for WSL is not available on these SKU types.
Other Windows 365 Features Announced at Build 2026
The developer image was not the only Windows 365 announcement at Build 2026. Three other capabilities are worth noting:
Autopilot Device Preparation — now available for Windows 365
Automates app and script installation on Cloud PCs through Microsoft Intune before a user ever signs in — the same Autopilot workflow used for physical devices, now applied to Cloud PCs. Ensures a compliant, ready-to-use environment on first login without any manual setup.
Azure Compute Gallery support — generally available
Organisations can now store and manage custom images in Azure Compute Gallery and import them directly into Windows 365 to provision Cloud PCs. Useful for teams that have heavily customised images with internal tooling, line-of-business applications, or specific configurations not available in the gallery.
Context-based redirection — public preview (June)
Applies granular redirection policies based on contextual signals: device management status, user network, and location. For example, a managed device on the corporate network could have different redirection behaviour than an unmanaged device accessing from home. More precise data protection than blanket redirection rules.
Official Microsoft References
- Microsoft Tech Community — Made for Developers and Agents: Windows 365 at Build 2026
- Microsoft Learn — Device Images in Windows 365
- Microsoft Learn — What's New in Windows 365 Enterprise
- Microsoft Learn — Public Preview Overview in Windows 365
- Microsoft Tech Community — Windows News You Can Use: May 2026