Microsoft has officially documented support for nested virtualization on Windows 365 Cloud PCs, giving enterprise users the ability to run Windows Subsystem for Linux (WSL), Hyper-V, and Windows Sandbox directly within their cloud-hosted desktops. The move, which began as a roadmap entry in early 2022, has now materialized into production-ready guidance on Microsoft Learn, complete with SKU requirements, regional availability, and performance considerations. However, the original vision of also supporting Android apps via the Windows Subsystem for Android (WSA) has been derailed by Microsoft’s decision to deprecate WSA on Windows 11, leaving the Android story for Cloud PCs in limbo.

Nested Virtualization: What’s Officially Supported

Nested virtualization is the technology that allows a virtual machine to expose hardware virtualization extensions, enabling that VM to run its own hypervisor and host additional operating systems. On Windows 365 Cloud PCs, Microsoft currently lists three supported workloads that leverage nested virtualization:

  • Windows Subsystem for Linux (WSL): Run Linux distributions alongside Windows.
  • Windows Sandbox: A lightweight, isolated desktop environment for testing untrusted software.
  • Hyper-V: Create and manage additional virtual machines within the Cloud PC.

To enable these capabilities, the Cloud PC must meet strict requirements published on Microsoft Learn:

  • A minimum of 4 vCPUs. Downsizing to a 2 vCPU Cloud PC will automatically disable nested virtualization.
  • Provisioned in a supported region. Notably, South Africa North is excluded from nested virtualization support.
  • GPU Cloud PCs are expressly unsupported for nested virtualization workloads.

Microsoft also warns that users may experience performance degradation on 4 vCPU Cloud PCs when nested virtualization is active. For heavier workloads, many administrators have found 8 vCPU / 32 GB configurations to be more reliable, as echoed in community forums and third-party testing. Enabling these features typically involves activating the Hyper-V role and related Windows features on the Cloud PC, after which WSL2, Sandbox, and Hyper-V Manager become available for use.

The Linux Advantage: WSL on Cloud PCs

For developers and DevOps teams, the ability to run Linux distros inside a Cloud PC is a game-changer. Previously, cloud desktop environments forced a trade-off between centralized management and access to Linux-native tools. Now, with WSL support, an organization can provision a single Cloud PC image that includes a full Linux kernel and distribution, allowing developers to use familiar command-line tools, run containers via Docker (with the WSL2 backend), and build cross-platform applications without leaving the corporate-managed environment.

This capability is particularly valuable for enterprises adopting cloud-first development strategies. Instead of shipping high-end laptops with dual-boot or VM setups, IT departments can deliver a secure, consistent development platform through Endpoint Manager, while developers retain the flexibility to spin up WSL instances on demand. The result is faster onboarding, reduced hardware costs, and a unified security posture.

Hyper-V and Sandbox: Expanding Testing Capabilities

Beyond Linux, nested virtualization enables Hyper-V on Cloud PCs, which opens the door to running entire virtual machines for testing, training, or legacy application support. Windows Sandbox provides an ephemeral, clean environment ideal for testing untrusted downloads or running one-off experiments without risking the host system.

These features transform the Cloud PC from a simple remote desktop into a powerful, multi-layered testing and development sandbox. For security-conscious organizations, running these isolated environments in the cloud rather than on physical endpoints reduces the risk of malware escaping onto the corporate network. Additionally, Hyper-V on Cloud PCs can serve as a temporary staging ground for server roles or network configurations, all while keeping data within the Azure boundary.

The Android Conundrum: A Roadmap Promise Unraveled

When Microsoft first added nested virtualization to the Windows 365 roadmap in March 2022 (Feature ID 89004), the entry explicitly mentioned Windows Subsystem for Android (WSA) as a beneficiary. The logic was straightforward: if a Cloud PC could host a hypervisor, it could also host the Android runtime, allowing users to run Android apps streamed from the cloud.

Several independent outlets, including Neowin, reported on the roadmap at the time, noting a preview targeted for April 2022 and general availability later that year. Microsoft’s “What’s new” logs from April 2022 confirmed that a nested virtualization preview had begun, with WSL and WSA cited as key scenarios.

But in March 2024, Microsoft announced that it was deprecating WSA on Windows 11, with support ending in March 2025. The move effectively killed the native Android app experience on Windows that had been built around the Amazon Appstore partnership. With the underlying WSA runtime being phased out, the assumption that Cloud PCs would soon offer Android app support collapsed.

Today, Microsoft’s official nested virtualization documentation makes no mention of Android. The workloads listed are strictly WSL, Sandbox, and Hyper-V. While the underlying hypervisor technology might still technically permit an Android VM, there is no supported Microsoft-provided Android runtime for Cloud PCs, and no indication that one is in development post-WSA.

Timeline: From Roadmap to Reality

The path from roadmap promise to current capabilities is telling:

  • March 2022: Microsoft adds nested virtualization for Windows 365 to the public roadmap, highlighting WSL and WSA.
  • April 2022: Preview begins for selected SKUs and regions; documentation acknowledges nested virtualization (preview) in Windows 365 updates.
  • Late 2022: Several roadmap trackers suggest a general availability target of December 2022, but rollouts are phased and region-specific.
  • 2023–2024: Documentation matures, clearly defining requirements and supported workloads (WSL, Sandbox, Hyper-V). GPU Cloud PCs remain excluded.
  • March 2024: Microsoft announces deprecation of WSA on Windows 11, effective March 2025.
  • Present: Nested virtualization is a documented and supported feature on qualifying Cloud PCs, but Android support is not part of the official feature set.

This timeline underscores a common reality in cloud services: roadmap entries are intentions, not guarantees. The original scope included Android, but subsequent product lifecycle decisions altered the trajectory.

Performance and Constraints: What IT Admins Need to Know

Before enabling nested virtualization fleet-wide, IT administrators must understand the performance profile and constraints. Official Microsoft guidance and community testing point to several key factors:

  • SKU Sizing is Critical: The 4 vCPU minimum is just the entry point. Many workloads, especially those involving Docker builds or multiple nested VMs, will demand the 8 vCPU / 32 GB tier to avoid sluggishness. Microsoft’s documentation warns that performance may suffer on 4 vCPU Cloud PCs.
  • Resource Contention: Nested VMs consume CPU, memory, and I/O, which can lead to increased latency for the primary Windows session. In multi-tenant Azure environments, noisy neighbors might exacerbate performance variability.
  • Region and SKU Dependencies: Not all regions support nested virtualization, and the feature is available only on specific Windows 365 Enterprise SKUs. IT teams must verify compatibility for each deployment geography.
  • GPU Cloud PCs: Not an Option: Organizations that invested in GPU Cloud PCs for graphics-intensive work must accept that nested virtualization is incompatible with those configurations.
  • Downsizing Disables It: Moving a Cloud PC from a 4 vCPU or higher SKU to a 2 vCPU SKU will silently disable nested virtualization, potentially breaking dependent workflows.

Strategic Implications for Enterprise Adoption

The addition of nested virtualization significantly enhances the Cloud PC value proposition for development and testing. It brings Windows 365 closer to parity with physical developer workstations, making it easier for enterprises to adopt cloud desktops for technical staff. Key implications include:

  • Developer Productivity: Unifying the development stack inside a Cloud PC reduces onboarding time and eliminates the need for complex local VM setups.
  • Security and Compliance: All code, data, and testing environments remain within Azure, allowing centralized security monitoring and data loss prevention controls.
  • Hybrid Work Enablement: Remote developers can access their full development environment from any device, while IT maintains governance.
  • Android Uncertainty May Stall Some Use Cases: Organizations with mobile app testing requirements that were eyeing Cloud PCs as an Android emulation platform must pivot. The deprecation of WSA means that any Android-in-Cloud-PC scenario would require a third-party solution or a new Microsoft strategy, which does not exist today.

Practical Guidance: Getting Started with Nested Virtualization

For IT teams ready to explore nested virtualization, a methodical approach is recommended:

  1. Verify Eligibility: Ensure your Windows 365 licenses include the Enterprise plan, and your Cloud PCs are provisioned in supported regions (excluding South Africa North). Confirm SKU size is 4 vCPU or higher.
  2. Provision a Test Pool: Deploy a small set of Cloud PCs with 8 vCPU / 32 GB for initial testing. If budget is tight, start with 4 vCPU, but be prepared to scale up.
  3. Test Core Workloads: Install WSL2 distributions, spin up Hyper-V VMs, and measure performance during typical builds, container operations, and multi-tasking. Compare against local workstations.
  4. Monitor Resource Utilization: Use Azure Monitor and Windows Performance Monitor to track CPU, memory, and disk metrics. Identify any bottlenecks before broader rollout.
  5. Plan for Android Separately: For teams that need Android app testing, set up dedicated Android emulators on physical devices, use cloud-based device farms, or explore third-party alternatives. Do not assume Cloud PC Android support will arrive as originally envisioned.
  6. Educate Users: Inform developers and power users about the supported workloads and limitations. Provide clear guidelines on when to use nested virtualization versus other tools.

The Bottom Line

Windows 365 nested virtualization is a mature, documented feature that brings tangible benefits for Linux, Hyper-V, and Sandbox workloads inside Cloud PCs. It fulfills a long-standing request from the developer community and makes cloud desktops a more viable option for technical professionals.

The Android piece, however, remains an unfulfilled promise. Microsoft’s deprecation of WSA casts a shadow over any near-term Android integration, and enterprises should not include Cloud PC-based Android app support in their planning without official confirmation from Microsoft.

For now, the smart move is to capitalize on the Linux and Hyper-V capabilities, while maintaining flexibility and fallback plans for mobile development workflows. With nested virtualization finally here, the Cloud PC is no longer just a thin client to Windows—it’s a versatile, multi-OS development platform in the cloud.

This article draws on official Microsoft documentation, historical roadmap archives, independent reporting, and community insights. As with all cloud services, features and support status can evolve, so IT leaders should continuously consult the latest sources before making strategic decisions.