Exercise—Validate your development environment
In the previous exercises, you accessed a Windows 365 Cloud PC and began working with code—without installing tools or configuring your environment.
In this final readiness check, you'll confirm that your Cloud PC isn't just accessible, but fully capable of supporting real development work.
Validation scenario
You're continuing your first day on a new development team. After signing in and starting work, you need to ensure your environment is reliable and ready for ongoing use.
Your goal is to verify that your Cloud PC can function as your primary development workstation.
Validation checklist
Use the following checklist to confirm your environment is ready:
- Edit and manage code
- Open files in your editor
- Make and save changes
- Run development workflows
- Build, run, or test your application
- Execute commands using the terminal or CLI tools
- Access required tools
- Confirm that key tools and dependencies are available
- Verify that no extra installation is required
- Confirm that your development tools aren't only installed, but also configured consistently (for example, editor extensions, CLI tools, or WSL environments that match your team's standards)
- Work across environments (if applicable)
- Use Windows and Linux workflows as needed
- Switch between tools without reconfiguration
- If tools fail to launch, required dependencies are missing, or workflows can't run without extra setup, the environment might require further configuration
Expected result
By completing this validation, you should be confident that:
- Your environment is fully functional
- Your tools are ready and available
- Your workflows run with minimal setup or interruption
Most importantly, you've confirmed that your Cloud PC can support real development work—not just initial access.
Why this matters
This step proves the core promise of the experience: you can rely on your Cloud PC as your developer workstation faster.
Your environment is ready—and stays ready—as you continue building.