Microsoft released Windows 365 Cloud Apps as a public preview in mid-September 2025, letting IT administrators publish individual applications—Outlook, Word, OneDrive, Edge, PowerPoint and line-of-business apps—without ever provisioning a full Cloud PC for every user. The feature streams only the app window from a shared Windows 11 host, marking the first time Windows 365 decouples app delivery from the full desktop experience for task-based workers.

The app-only streaming model explained

Windows 365 Cloud Apps is not a new protocol or separate OS. It layers an app-publishing model on top of existing Windows 365 Frontline Cloud PCs. When an admin creates a provisioning policy with the “Access only apps” experience type, the service deploys a shared Cloud PC running a Windows 11 Enterprise image. A discovery script scans that image’s Start Menu for eligible executables and surfaces them as publishable applications. When an assigned user launches a Cloud App, the streaming broker delivers only the application window—no desktop, no Start Menu, just the app.

Sessions inherit the same security and management posture as the underlying Cloud PC, including Conditional Access, Intune policies, and device compliance checks. That means a frontline worker streams Word the same way they would from a dedicated Cloud PC, but without the overhead of managing a full virtual desktop.

Key technical limits in the preview

  • App discovery is Start Menu-only. The discovery process looks for traditional executables listed in the Start Menu. Apps installed via Appx, MSIX, or other modern packaging formats are not discovered. Microsoft Teams (desktop) is explicitly unsupported as a Cloud App.
  • Host OS requirements are strict. Cloud Apps require Cloud PCs running supported Windows 11 builds. Examples cited by Microsoft include Windows 11 Enterprise 24H2, or 22H2/23H2 with a specific cumulative update. Once those conditions are met, OneDrive can launch automatically alongside the streamed app.
  • No imageless deployment yet. You must still maintain a Cloud PC gallery or custom image with pre-installed apps. The long-term roadmap promises Intune integration so that Intune-delivered apps can be published without custom images, but that capability is not available in the preview.

What this means for you

For IT administrators

Cloud Apps reduce the need to manage dozens of specialized images just to deliver a single line-of-business app to shift workers. You can now build one shared image, publish discovered apps to user groups, and let Microsoft Entra ID and Intune handle access. The operational simplification is real, but three new responsibilities appear:

  • Concurrency planning replaces headcount. Windows 365 Frontline licenses allow multiple named users per Cloud PC, but only one active session per license at a time. You must size licenses against peak concurrent usage across shifts, not total staff. Under-provision licenses and users will hit “all seats occupied” errors during busy periods.
  • Discovery script fragility. If security baselines block PowerShell execution or custom images deviate from expected Start Menu layouts, the discovery script may fail silently. You’ll likely need an image-validation step in your pipeline until Intune-driven publishing arrives.
  • App compatibility audit. Catalog your environment now: any app packaged via Appx or MSIX, or any Teams desktop scenario, will remain out of scope for Cloud Apps during the preview. Teams web and PWAs are the recommended fallback.

For frontline employees

Users see a cleaner workflow. Cloud Apps appear in the Windows App alongside locally installed applications, and the Windows 365 web portal filters to show only published Cloud Apps. Clicking one opens a single application window; OneDrive can auto-launch if the host meets build requirements. There’s no full desktop to navigate, which cuts sign-in time and eliminates context switching for task workers who only ever use one or two apps.

For business decision-makers

Frontline shared licensing aligns cost more closely with actual use. Instead of procuring a dedicated Cloud PC for everyone, you pay for concurrency. For organizations with predictable shift patterns—retail stores, call centers, hospital check-in desks—the license savings can be substantial. However, the preview’s app compatibility gaps mean you’ll still need dedicated Cloud PCs or alternative delivery for roles that require modern packaged apps or Teams desktop, so treat this as a complement, not a full replacement.

How we got here

Windows 365 launched in 2021 as Microsoft’s managed Cloud PC service, offering per-user Azure-hosted Windows instances. While it solved centralization for hybrid work, it forced a full-desktop paradigm even for employees who only needed one application. Frontline licensing, introduced later, allowed multiple named users on one Cloud PC but still delivered a full desktop. The gap remained: many task workers needed an app, not a desktop.

The private preview of Cloud Apps, announced earlier in 2025, tested the core streaming model. The public preview, as first reported by Neowin and confirmed by Microsoft’s documentation, expands on that with admin UX improvements—auto-OneDrive launch, automatic filtering in the Windows App, and a clearer provisioning policy flow. The feature explicitly targets retail, hospitality, healthcare, call centers, and kiosk scenarios, where one shared host can serve many users in sequence.

What to do now: a pilot checklist

If you’re considering Windows 365 Cloud Apps, a controlled pilot will surface most risks before you commit. Here’s a step-by-step approach:

  1. Confirm licensing. Purchase Windows 365 Frontline licenses; these behave differently in admin consoles than user-based licenses. Verify that the “shared mode” capability is enabled in your tenant.
  2. Build a compatible image. Create a shared Cloud PC image that includes the necessary line-of-business apps with traditional Start Menu shortcuts. Avoid relying on Appx or MSIX in this image. Validate that the OS build meets Microsoft’s documented requirements (Windows 11 Enterprise 24H2 is a safe baseline).
  3. Create a provisioning policy. In the Windows 365 admin center, select “Access only apps” as the experience type. Assign the image and policy to a small test group.
  4. Run discovery and publish. Let the discovery script scan the image, then publish the discovered apps to Entra ID groups. Check for failures: if the script doesn’t run, temporarily adjust PowerShell execution policies or security baselines to unblock it.
  5. Test concurrency behavior. Have your pilot users log in simultaneously during simulated peak shifts. Monitor whether any user sees a “no available license” error and adjust license counts accordingly.
  6. Gather telemetry. Use Windows 365 monitoring to track session concurrency, app launch times, and network latency. These metrics will inform scaling decisions before a broader rollout.
  7. Prepare fallbacks. For unsupported apps, set up alternatives: Teams web, PWAs for internal tools, or keep a small pool of dedicated Cloud PCs for those roles.

Outlook

Microsoft hasn’t announced a general availability date. The public preview documentation calls out known limits and says Intune integration will eventually remove the custom image requirement, but no timeline is provided. Regional availability may also be limited during preview. IT teams should expect at least one more iteration before GA, with app compatibility likely expanding—especially for MSIX-packaged apps—as the Intune delivery path matures.

For now, Windows 365 Cloud Apps is a pragmatic tool for a specific job: delivering a handful of apps to shift workers without the weight of a full desktop. The cost and management benefits are real if you plan concurrency carefully and validate your image thoroughly. It won’t replace your entire Cloud PC estate overnight, but it’s a clear signal that Microsoft is breaking the Windows 365 experience into more granular, role-specific pieces.