Windows 365 Nested Virtualization: Linux WSL on Cloud PCs, Android Uncertain

Microsoft’s plan to add Linux and Android subsystem support to Windows 365 Cloud PCs — long visible on the Microsoft 365 roadmap — resurfaced in headlines recently, but the full story is more nuanced than a single preview date. Microsoft documented nested virtualization for Cloud PCs (the technical route that enables Windows Subsystem for Linux and the Windows Subsystem for Android to run inside a Cloud PC) as a roadmap item and began preview rollouts in 2022; more recent Microsoft documentation formalizes that virtualization-based workloads (including WSL and Hyper‑V) are supported on certain Cloud PC SKUs, but the Android story has diverged since the original roadmap entry. (neowin.net, learn.microsoft.com)

---

Background​

Since its 2021 launch, Windows 365 (the Cloud PC service) has aimed to give organizations a full Windows desktop streamed from Microsoft’s cloud to any device. The service is managed through Microsoft Endpoint Manager and is accessible from Windows, macOS, iOS, Android and web clients. Because Cloud PCs are virtual machines operating atop Azure infrastructure, some typical desktop features—especially those that require hardware virtualization or low-level kernel access—are only available when Microsoft enables nested virtualization on Cloud PC instances. (learn.microsoft.com)
In March–April 2022 Microsoft placed a roadmap entry (Feature ID 89004) announcing nested virtualization support for Windows 365 Cloud PCs, explicitly calling out Linux and Windows Subsystem for Android (WSA) as initial workloads that would benefit. That roadmap item showed a preview target in April and an initial general availability target later in the year. Multiple independent news sites and archive captures of the roadmap tracked that plan at the time. (neowin.net, app.cloudscout.one)
Fast forward: Microsoft has since published operational documentation that explains how to enable virtualization-based workloads on Cloud PCs and what SKU and configuration constraints apply. Meanwhile, the Android runtime story changed: Microsoft announced deprecation of the Windows Subsystem for Android on Windows 11, creating ambiguity about the future of Android support in Cloud PCs. This mix of roadmap history, documented capabilities, and product lifecycle changes is the context IT teams must evaluate. (learn.microsoft.com, theverge.com)

---

What Microsoft actually enabled (and when)​

Nested virtualization: the technical foundation​

Nested virtualization is the mechanism that exposes hardware virtualization features from the host to a VM, allowing that VM to host its own hypervisor and run additional guest OS instances. In Cloud PCs this is how you can run:

• Windows Subsystem for Linux (WSL) distributions that depend on virtualization features;
• Hyper‑V inside a Cloud PC to run additional VMs or containers;
• historically, Windows Subsystem for Android (WSA) in preview scenarios. (techcommunity.microsoft.com)

Microsoft’s Windows 365 “What’s new” log from April 2022 explicitly recorded a nested virtualization (preview) entry that enabled some Cloud PC SKUs to run virtualization-based developer workflows. That entry shows Microsoft moved from planning to preview activity in Spring 2022. Independent reporting at the time captured the roadmap details and planned dates. (learn.microsoft.com, neowin.net)

Current product documentation (what it requires today)​

Microsoft’s current Cloud PC guidance (updated and maintained on the Windows 365 documentation site) spells out practical requirements for nested virtualization:

• Cloud PC must be 4 vCPU or higher (downsizing to 2 vCPU disables nested virtualization).
• Some Cloud PC performance implications are possible on 4 vCPU SKUs; 8 vCPU / 32 GB SKUs were commonly recommended for heavier nested workloads in earlier guidance and third‑party writeups.
• GPU Cloud PCs do not support nested virtualization.
• Nested virtualization is regional and SKU dependent; earlier rollouts had limited-region restrictions that Microsoft expanded over time. (learn.microsoft.com, thewindowsclub.com)

These technical constraints matter: nested virtualization is not an on/off setting for all Cloud PCs. Administrators must evaluate license types, SKU sizes, and region availability before assuming WSL or Hyper‑V will work inside a Cloud PC.

---

Timeline recap and verification of the Mashdigi claim​

• March 2022: Roadmap entry created that tracked nested virtualization for Windows 365 with WSL and WSA mentioned among potential workloads (Feature ID 89004). Multiple independent trackers and technology news sites mirrored this roadmap entry. (neowin.net, app.cloudscout.one)
• April 2022: Microsoft recorded a “nested virtualization (preview)” item in its Windows 365 “What’s new” stream, and preview activity commenced for selected Cloud PC SKUs and regions. Vendor and community documentation from mid‑2022 shows administrators enabling nested virtualization on 8 vCPU Cloud PCs. (learn.microsoft.com, thewindowsclub.com)
• December 2022: Several roadmap records listed a general availability target around December CY2022; public rollout timing varied by region and SKU, as is typical for Microsoft 365 roadmap items. Archive captures and third‑party trackers show the December target, but rollouts tended to phase and adjust. (app.cloudscout.one)
• March 2024 – March 2025: Microsoft publicly announced the deprecation of Windows Subsystem for Android (WSA) on Windows 11, with support slated to end in March 2025. This announcement affects the broader availability of Microsoft’s WSA-based Android experience on Windows client platforms and clouds the earlier roadmap assumption that WSA would be a straightforward addition inside Cloud PCs. (theverge.com, windowscentral.com)

Bottom line: the Mashdigi report summarises roadmap changes that were publicly tracked in 2022 and reported by other outlets; the basic claim that Microsoft planned nested virtualization to enable Linux and Android subsystems on Windows 365 was accurate as a roadmap item. However, the Android runtime landscape shifted after that roadmap entry, and Microsoft’s later deprecation notice for WSA makes the Android piece much less certain. (neowin.net, theverge.com)

---

Why nested virtualization matters for enterprises and dev teams​

Nested virtualization on Cloud PCs changes the Cloud PC from a single OS stream into a potential development and testing platform. Key advantages include:

• Unified development environment: Developers can run WSL distributions inside an enterprise Cloud PC, bringing Linux toolchains, Docker (in some configurations), and other Linux-native workflows into the corporate-managed Cloud PC environment.
• Simpler device management: IT avoids provisioning physical developer workstations; images and access can be centrally managed while allowing developers to spin up internal VMs as needed.
• Faster onboarding: New hires get a preconfigured Cloud PC image where nested virtualization features are available, reducing setup time for cross-platform testing.
• Consistent security posture: Cloud-first execution keeps code and data within your Azure estate; corporate policies and endpoint controls remain in effect.

These benefits matter for organizations that want developer parity across local and cloud environments and for teams standardizing on Cloud PCs for remote or hybrid work.

---

Technical constraints, performance and compatibility risks​

Nested virtualization is powerful but comes with tradeoffs. Administrators and architects should consider the following constraints and risks before rolling it into production.

Requirements and performance​

• SKU sizing matters. Microsoft’s guidance requires at least 4 vCPU for nested virtualization, and many real‑world scenarios recommend 8 vCPU / 32 GB for reliable developer use. Downsizing to lower vCPU counts will disable nested virtualization, and resizing Cloud PCs is not always a trivial reprovision operation. (learn.microsoft.com, thewindowsclub.com)
• GPU Cloud PCs are not compatible with nested virtualization, which matters if GPU acceleration is required for containers or emulators.
• Performance variability. Running nested VMs increases CPU, memory and I/O demand; some regions and multi-tenant environments have exhibited uneven performance when nested workloads are enabled.

Compatibility considerations​

• Hypervisor compatibility. Nested virtualization on a Cloud PC is implemented to support Hyper‑V and Microsoft-backed virtualization paths; other third-party hypervisors or older hypervisor versions may not work inside a Cloud PC.
• Feature interactions. Certain host features (for example, virtualization-based security, dynamic memory features, or specific live‑migration options) may be incompatible with nested virtualization. Administrators must test their specific workloads in preview environments.
• Licensing and support scope. Nested virtualization may be exposed only to specific Windows 365 license types or SKUs; organizations should verify licensing entitlements and support boundaries before committing workloads to Cloud PCs. (thewindowsclub.com, app.cloudscout.one)

---

The Android question: promise, deprecation, and ambiguity​

The original roadmap entry referenced the Windows Subsystem for Android as part of the nested virtualization preview. The rationale was straightforward: if you can run Hyper‑V inside a Cloud PC, you can host the Android runtime there and stream or interact with Android apps from a Cloud PC session.
But the Android landscape shifted:

• Microsoft announced that the Windows Subsystem for Android (WSA) and the Amazon Appstore experience on Windows 11 would be deprecated, with support ending in March 2025. The deprecation removes the clear, Microsoft‑managed runtime that roadmap watchers once expected to appear in Cloud PCs. (theverge.com, windowscentral.com)
• That deprecation introduces real-world ambiguity about any Windows 365 plan to offer Android subsystem features integrated as a Microsoft‑managed Cloud PC capability. An earlier roadmap entry is not a guarantee of persistent product plans; product roadmaps evolve, and platform deprecations supersede earlier intentions.

What this means in practice:

• Organizations should consider the Linux/WSL value proposition from nested virtualization as a near-term, verifiable capability (WSL and nested Hyper‑V support are documented and supported on qualifying Cloud PCs). (learn.microsoft.com)
• Android workloads inside Cloud PCs are not a sure outcome. The WSA deprecation signals that Microsoft has deprioritized or is rearchitecting how Android will be supported on Windows client platforms; any Cloud PC Android experience would require a new Microsoft strategy or a partner solution, and it is not safe to assume parity with the WSA model that previously existed on Windows 11. (theverge.com)

---

Recommendations for IT and platform teams​

Given the capabilities and uncertainties, here are pragmatic steps IT leaders and platform teams should take.

• Evaluate immediate developer needs: if Linux toolchains and WSL are the primary requirement, plan Cloud PC SKUs for nested virtualization now (4 vCPU minimum, test with 8 vCPU/32GB for production dev workloads). Validate performance in the regions you plan to use. (learn.microsoft.com, thewindowsclub.com)
• Treat Android as an optional and instability-prone piece: do not bet migrations or critical business apps on a Cloud PC Android runtime until Microsoft publishes a definitive product roadmap that explicitly reconstructs Android support post‑WSA deprecation.
• Run proof-of-concept projects: deploy a small fleet of Cloud PCs with nested virtualization enabled and measure real workloads — container builds, VM spin-ups, and integrated CI tasks — to capture realistic CPU, memory, and I/O consumption.
• Harden security posture: nested virtualization increases attack surface complexity (multiple hypervisors, nested kernel surfaces). Ensure endpoint security, least privilege, and monitoring are extended to Cloud PCs with nested workloads.
• Plan for fallback: for Android-dependent workflows, identify alternatives (mobile device management, third‑party emulators, device farms, or dedicated Android development VMs) and create a migration/contingency plan in case Microsoft or app-store partners change support models. (theverge.com)

---

Strategic implications: what Microsoft’s roadmap moves mean for cloud desktop adoption​

• Greater developer parity: The availability of nested virtualization on Windows 365 aligns Cloud PCs more closely with traditional developer workstations. This reduces friction for teams that target both Windows and Linux ecosystems and accelerates the cloud-first development narrative.
• Cloud PC as a secure endpoint: By enabling virtualization-based workloads in the cloud, organizations can centralize control, reduce local data sprawl, and apply consistent security policies — desirable outcomes in regulated industries.
• Product uncertainty undermines some use cases: The deprecation of WSA highlights a broader reality: roadmap items can move; product lifecycle decisions can undo earlier plans. Organizations that depend on features still in early preview or roadmap status should weigh adoption risk and prepare contingency paths.
• Vendor dependency for platform runtimes: Android experiences on Windows historically depended on partnerships (e.g., Amazon Appstore) and runtime models that may not be portable. Microsoft’s deprecation of WSA underlines how platform vendor decisions can materially affect downstream enterprise capabilities.

---

What to test now (practical checklist)​

• Confirm the Cloud PC image and SKU in your tenant support nested virtualization.
• Provision a test Cloud PC with at least 4 vCPU, and evaluate with a representative dev workload; scale to 8 vCPU / 32 GB if results show resource contention.
• Verify that GPU Cloud PCs are excluded if your workload expects GPU passthrough.
• Validate WSL distro installation, Docker/container workflows, and Hyper‑V guest creation under your Cloud PC configuration.
• Document and quantify performance (build times, container start times, memory footprints) and compare to equivalent physical workstations.
• For Android-dependent workflows, maintain a separate evaluation track using dedicated Android emulators or device farms (do not rely on Cloud PC Android until Microsoft clarifies future plans). (learn.microsoft.com, thewindowsclub.com)

---

Strengths, weaknesses and final assessment​

• Strengths
• Microsoft enabling nested virtualization on Windows 365 is a clear win for developer productivity and centralized IT management; WSL inside Cloud PCs is now a supported path for many developer scenarios. The technical foundations and Microsoft documentation are in place to support practical deployments. (learn.microsoft.com)
• Cloud PC adoption benefits — centralized security, rapid provisioning, platform parity — are reinforced by nested virtualization capability.
• Weaknesses & Risks
• The Android subsystem promise is uncertain. Microsoft’s public deprecation of WSA on Windows 11 significantly complicates any expectation that a Cloud PC‑hosted Android experience will be supported in the same model going forward. Relying on WSA for critical business flows inside Cloud PCs would be imprudent. (theverge.com)
• Performance and SKU constraints mean nested virtualization is not a universal panacea; organizations must choose appropriate Cloud PC SKUs and plan for the increased resource and management overhead.
• Final assessment
• For Linux and WSL workloads, Windows 365 nested virtualization is a mature, supported option for many enterprise users and is worth testing and integrating into developer platform planning. For Android, treat the roadmap references as historical intent rather than an operational guarantee; plan alternative paths and watch Microsoft’s official channels for any renewed Android strategy for Cloud PCs.

---

Conclusion​

Microsoft’s roadmap and subsequent documentation show that Windows 365 can host virtualization‑based workloads — notably Windows Subsystem for Linux and Hyper‑V guests — on qualifying Cloud PCs, and those capabilities have moved from roadmap to preview and into supported documentation. The original roadmap also mentioned Android as a preview scenario, but Microsoft’s later deprecation of the Windows Subsystem for Android on Windows 11 introduces a significant caveat: Android support inside Cloud PCs is neither a guaranteed nor a current Microsoft‑backed outcome. Enterprises should adopt nested virtualization for Linux and developer workflows where it fits their needs, but treat Android as a conditional capability that requires careful vendor confirmation and contingency planning. (learn.microsoft.com, neowin.net, theverge.com)

---

Source: Mashdigi Microsoft will begin previewing Linux and Android subsystem features for Windows 4 services in April