Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Windows 365 Cloud Apps feature allows administrators to give users secure access to individual apps hosted on a Cloud PC, without requiring a dedicated Cloud PC for every user. Windows 365 Frontline licenses entitle organizations to stream Windows 365 Cloud Apps when operating Cloud PCs in shared mode.
This feature is in public preview.
Prerequisites
To create Cloud Apps, you need a Windows 365 Frontline license.
Create Cloud Apps
First, create a new Windows 365 provisioning policy, and complete the following steps:
On the General tab, for Experience, select "Access only apps." This selection defaults the License type to Frontline and Shared mode.
Optionally, in the Image tab, view the apps available on the image that you can publish after provisioning.
Once the policy is created, the Frontline Cloud PCs in Shared mode with experience type "Cloud App" begin provisioning in All Cloud PCs. After the first Cloud PC is provisioned, the apps available on the image will show as "Ready to publish" in All Cloud Apps.
In All Cloud Apps, you can publish, edit, reset, and unpublish Cloud Apps.
When you publish Cloud Apps, the app status changes from "Ready to publish" to "Publishing" to "Published." Publishing an app makes it available in Windows App to all users assigned to the provisioning policy.
- If the app status is "Failed," then try unpublishing and republishing again.
You can edit individual Cloud App details, including display name, description, command line, and icon path index. The Cloud App's scope tags and assignment are inherited from the provisioning policy. The edits are published immediately to Windows App.
You can reset the Cloud App's details to its original discovered state from the device image.
When you unpublish Cloud Apps, the app status changes from "Published" to "Ready to publish," and the app is no longer available in Windows App. App details are also reset.
To delete Cloud Apps, you need to delete the Cloud App provisioning policy assignment.
Note
Since Cloud Apps run on Frontline Cloud PCs in Shared mode, the same management and end-user experiences that apply to Frontline Shared Cloud PCs also apply to Cloud Apps.
The maximum number of active Windows 365 Cloud App sessions for a provisioning policy is equal to the number of Windows 365 Frontline licenses that you assign to that specific policy. You can monitor concurrency in the Connected Frontline Cloud PCs report.
All settings applied to the underlying Frontline Cloud PCs, such as redirection or idle timeout settings, also apply to Cloud Apps.
Access Cloud Apps
End-users access published apps through Windows App. Note that published apps can also open other apps that are on the Cloud PC. For example, Microsoft Outlook as a Cloud App can launch Microsoft Edge via embedded links in emails, even if Microsoft Edge isn't published as a Cloud App. To fully control access to apps, use Application Control for Windows.
If Cloud PCs are running supported versions of Windows (Windows 11 Enterprise, version 24H2, or version 22H2 or 23H2 with the 2024-07 Cumulative Update for Windows 11 (KB5040442) or later installed.), then Cloud Apps automatically launch OneDrive.
Known limitations
Cloud Apps only discover application executables in the Device image's start menu that aren't installed by Appx or MSIX packages. As a result, Cloud Apps doesn't currently support Microsoft Teams. In development: You'll be able to discover and publish Appx / MSIX apps as Cloud Apps.
In preview, you can't edit a Cloud App's icon path. In development: you'll be able to edit the icon path.
In preview, you can link an Autopilot Device Preparation Policy, but you can't publish Intune apps as Cloud Apps. In development: you'll be able to discover and publish apps installed by Intune that are included in the Autopilot Device Preparation Policy associated with the Cloud App provisioning policy.
In preview, if you want to publish applications that aren't pre-installed in Windows 365 gallery images, then you need to use a custom image.
When you upload a custom image, Windows 365 Cloud Apps uses a PowerShell script to scan the Start Menu for apps. However, if your tenant imposes security policies requiring extra authentication for PowerShell, then we can't discover apps. Additionally, if your custom image isn't supported, then we can't discover apps.