Meeting the developer onboarding challenge
When you sign in to a Windows 365 Cloud PC, you're stepping into a development environment that has already been assembled, configured, and aligned to your team's workflow.
Instead of starting with a blank system and deciding what to install, you begin with a standardized developer environment that reflects common development practices and organizational requirements.
Depending on configuration, a Cloud PC created from an Image with Developer Configuration (preview) commonly includes tools such as:
- Preinstalled development tools
- Visual Studio Code with extensions
- PowerShell 7, Python, Node.js, and .NET SDK
- Git, GitHub Copilot CLI, and Azure CLI
- Preconfigured development workflows
- Editors and terminals ready to use without extensive setup
- Command-line tools available and aligned across environments
- Consistent toolchain versions across developers
- System-level configuration applied in advance
- Taskbar, File Explorer, and Start menu settings optimized for development
- Services and features enabled to support development scenarios
- A dual Windows + Linux development environment
- Windows Subsystem for Linux (WSL) installed and configured
- Ubuntu environment ready to use from first sign-in
- Tools can be aligned across Windows and WSL environments where supported
Important
The Windows 365 Image with Developer Configuration is in preview and subject to change. Individual tools and services included in the image might require their own licenses to use.
This means that the decisions typically made during setup—what tools to install, how to configure them, and how to structure your environment—have already been handled for you.
Because your environment is already prepared, you can begin development tasks more quickly. This reduced setup time is especially valuable for teams that are distributed geographically or require frequent onboarding.