Microsoft has outlined how Windows 10 ESUs (Extended Security Updates) apply to Windows 365: existing Windows 10 22H2 Cloud PCs get ESUs at no extra cost with updates delivered automatically, while new provisioning must move off gallery images removed on October 14, 2025 and shift to custom images by April 14, 2026 or to Windows 11 for full support and security posture. Microsoft 365 Apps on Windows 10 will keep receiving security updates through October 10, 2028, but feature updates end earlier by channel, reinforcing the recommendation to migrate to Windows 11. ICYMI, Windows 10 ESUs for personal devices also start today.
Windows 10 reached end of support on October 14, 2025, and Microsoft detailed the Windows 365 implications across image availability, ESU coverage, and support expectations to help admins plan next steps. The guidance covers existing Cloud PCs, provisioning with Windows 10 after EOS, custom images with ESUs, physical PC entitlements, Microsoft 365 Apps timelines, and how support cases will be handled.
Existing Cloud PCs get ESUs free
Cloud PCs running Windows 10 22H2 in Azure receive Extended Security Updates at no additional cost, enabling continued delivery of critical and important security fixes after EOS. ESUs will flow automatically via Windows Update or Autopatch based on each Cloud PC’s update configuration, with no extra admin action required.
New and reprovisioned Cloud PCs
Starting October 14, 2025, Windows 10 gallery images were removed and cannot be used to create new provisioning policies; existing policies referencing Windows 10 22H2 images continue to work only until April 14, 2026. After April 14, 2026, those images are retired, provisioning attempts fail with an out‑of‑support status, and admins should update to supported images or transition to Windows 11 to maintain security and supportability.
Image and update timing
The final monthly refresh of Windows 365’s Windows 10 gallery images is the October 2025 update, and Cloud PCs created between October 2025 and April 2026 will need ESUs installed to stay current. A Windows 10 22H2 image with the October 2025 update remains published in Azure Marketplace, aligned with Volume Licensing and Visual Studio downloads and without Windows 365 or Microsoft 365 App customizations.
Create a Windows 10 custom image with ESUs
Admins who still need Windows 10 after April 2026 must build and import a custom image for Windows 365 using the October 2025 Windows 10 22H2 base and then apply ESUs and any allowed apps or configurations. Follow Microsoft’s device image requirements and Intune import process for Windows 365 custom images to validate and publish the image across required regions.
-
Create an Azure VM from the Windows 10 22H2 Azure Marketplace image; note the last available image is October 2025.
-
Run Windows Update repeatedly until the latest ESUs are installed, allowing for multiple reboots to complete security baselining.
-
Review Microsoft 365 Apps support considerations on Windows 10 before installing Office apps, then capture and import the generalized image into Windows 365 per Microsoft’s custom image docs.
Physical PCs connecting to Cloud PCs
Intune‑managed Windows 10 physical PCs used to connect to Windows 365 are automatically entitled to Windows 10 ESUs to extend the life of devices that don’t meet Windows 11 hardware requirements. Devices connecting to Windows 365 Frontline Shared or Windows 365 Reserve Cloud PCs aren’t eligible for this free ESU benefit, and admins should plan upgrades or alternative access strategies accordingly.
Microsoft 365 Apps timelines
Microsoft 365 Apps on Windows 10 receive security updates for three years after Windows 10 EOS, ending October 10, 2028, to help organizations transition safely. Feature updates continue until Version 2608 on the following schedules: August 2026 (Current Channel), October 13, 2026 (Monthly Enterprise Channel), and January 12, 2027 (Semi‑Annual Enterprise Channel), after which devices receive only security updates until October 10, 2028.
If an issue is determined to be with Windows 365, Microsoft will support it as usual; if it’s an OS issue, support may request reproduction on a currently supported Windows 11 version and proceed if reproducible there. If a Windows 11 resolution doesn’t remediate Windows 10, the recommendation is to upgrade to Windows 11 since Windows 10 is no longer supported.
- Audit provisioning policies that reference Windows 10 22H2 images and plan to switch to Windows 11 or a compliant custom image before April 14, 2026.
- Build a compliant Windows 10 22H2 October 2025 custom image, install ESUs via Windows Update, and import it to Windows 365 if Windows 10 is still required.
- Ensure Intune‑managed connecting PCs understand ESU entitlements and verify eligibility for scenarios outside Frontline Shared and Reserve.
- Communicate Microsoft 365 Apps timelines and lock in a Windows 11 migration path to maintain both feature and security update cadence.
Treat Windows 10 in Windows 365 as a short‑term bridge: rely on free ESUs for existing 22H2 Cloud PCs now, while shifting provisioning to Windows 11 or a compliant Windows 10 custom image before gallery images retire on April 14, 2026.
Prioritize two parallel tracks—update provisioning policies and build/validate a Windows 10 22H2 (October 2025) custom image with ESUs where absolutely necessary, and ensure Intune‑managed Windows 10 devices that connect to Cloud PCs are properly entitled to ESUs in eligible scenarios.
Plan application continuity with the understanding that Microsoft 365 Apps on Windows 10 will receive security updates through October 10, 2028, but feature updates stop earlier by channel, so full feature cadence and long‑term supportability require Windows 11.
Because Windows 10 is already out of support, the strategic move is to accelerate a Windows 11 migration and treat ESUs as a temporary safety net to manage risk during the transition.
If Windows 10 must persist for limited cases, freeze on the October 2025 22H2 base, apply ESUs via Windows Update, import a compliant custom image into Windows 365, and set a firm timeline to complete the cutover to Windows 11.
About The Author
Discover more from Microsoft News Now
Subscribe to get the latest posts sent to your email.
