How Cloud PCs are prepared before first sign-in
By the time you sign in to a Windows 365 Cloud PC using Image with Developer Configuration (preview), most of the work of setting up your development environment has already been completed.
Instead of relying on each developer to install tools and configure their workspace manually, organizations prepare Cloud PCs in advance using a combination of preconfigured environments, automated provisioning, and controlled customization.
This preparation ensures that every developer starts from a consistent environment.
Preconfigured environments
Development environments begin with a curated image that includes the tools, runtimes, and configurations your team relies on. These images ensure consistency across developers and eliminate the variability that often comes with manual setup.
One example of this approach is the Image with Developer Configuration (preview), which standardizes both tooling and system setup before the developer signs in. Instead of each developer configuring their own editor, CLI tools, runtime environments, and shell, these elements are preinstalled and aligned across the entire team.
Automated provisioning
Automated preparation processes apply applications, scripts, and configurations to the Cloud PC before the first user session. This means the environment isn't only complete but also aligned with organizational policies and standards from the start.
For example, an organization might automatically install additional tools, apply security policies, or configure access to internal repositories before the developer signs in.
Customization at scale
Although environments are standardized, they're not one-size-fits-all. Teams can tailor Cloud PCs to their needs by including:
- Required SDKs and development frameworks
- Command-line tools and packages
- Build tools and dependencies
- Project-specific repositories and workflows
For partners and organizations, this approach enables faster onboarding across teams while maintaining control over toolsets and reducing configuration drift between developers.
This customization happens within a controlled framework, allowing teams to adapt environments for different types of work while maintaining consistency and governance. For example, teams can extend this baseline by adding project-specific SDKs, repositories, or internal tools, while still preserving a consistent core environment across developers.
Key takeaway
The most important shift is this: environment setup happens before you arrive—not after you sign in.
Instead of spending time preparing your workstation, you begin with an environment that's aligned to your team, your tools, and your work.
In the next unit, you'll access your Cloud PC and experience this model firsthand by starting development work right away.