Microsoft Intune

Assign Apps to Groups in Microsoft Intune

7 August 2026Updated+6 / −4 lines

In brief

The documentation now explicitly states that Available assignments can target device groups for Win32 apps and apps targeting Android Enterprise fully managed (COBO) and corporate-owned personally enabled (COPE) devices. The documentation date changed from 12/03/2025 to 08/06/2026.

What Intune admins need to know

Administrators can use this clarification when choosing user or device groups for Available app assignments; it documents existing assignment guidance rather than announcing a new feature.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

Open full page diff →

The comparison below shows only the changed extract. Open the full-page diff for complete context.

title: Assign Apps to Groups in Microsoft Intune description: Learn how to assign an Intune app to groups of users or devices using Microsoft Intune. ms.date: ~~12/03/2025~~08/06/2026 ms.topic: how-to ms.collection:

M365-identity-device-management

After you add an app to Microsoft Intune, you can assign the app to users and devices. You can deploy an app to a device whether or not the device is managed by Intune.

Note
The Available for enrolled devices deployment intent is supported for user groups and device groups. This applies when targeting Android Enterprise fully managed devices (COBO) and Android Enterprise corporate-owned personally enabled (COPE) devices.

Options when assigning managed apps

Device users with devices that aren’t enrolled in Intune must open their organization’s Company Portal and install app updates manually.
For almost all app types and platforms, Available assignments are only valid when assigning to user groups, not device groups. Win32 apps can be assigned to either user or device groups.
If managed Google Play preproduction track apps are assigned as required on Android Enterprise personally owned work profile devices, they don't install on the device. To work around this issue, create two identical user groups. Assign the preproduction track as "available" to one group and "required" to the other group. The result is that the preproduction track successfully deploys to the device.

Options when assigning managed apps

Device users with devices that aren’t enrolled in Intune must open their organization’s Company Portal and install app updates manually.
For almost all app types and platforms, Available assignments are only valid when assigning to user groups, not device groups.
The exceptions to this rule are:
Win32 apps can be assigned to either user or device groups as Available.
Apps targeting Android Enterprise fully managed devices (COBO) and Android Enterprise corporate-owned personally enabled (COPE) can be assigned to either user or device groups as Available.
If managed Google Play preproduction track apps are assigned as required on Android Enterprise personally owned work profile devices, they don't install on the device. To work around this issue, create two identical user groups. Assign the preproduction track as "available" to one group and "required" to the other group. The result is that the preproduction track successfully deploys to the device.

@@ -1,7 +1,7 @@ --- title: Assign Apps to Groups in Microsoft Intune description: Learn how to assign an Intune app to groups of users or devices using Microsoft Intune.-ms.date: 12/03/2025+ms.date: 08/06/2026 ms.topic: how-to ms.collection: - M365-identity-device-management@@ -12,8 +12,6 @@ ms.collection:  After you [add an app](./index.md) to Microsoft Intune, you can assign the app to users and devices. You can deploy an app to a device whether or not the device is managed by Intune. -> [!NOTE]-> The **Available for enrolled devices** deployment intent is supported for **user groups** and **device groups**. This applies when targeting Android Enterprise fully managed devices (COBO) and Android Enterprise corporate-owned personally enabled (COPE) devices.  ## Options when assigning managed apps @@ -36,7 +34,11 @@ The following table lists the various options when *assigning* apps to users and > > Device users with devices that aren’t enrolled in Intune must open their organization’s Company Portal and install app updates manually. > -> For almost all app types and platforms, *Available assignments* are only valid when assigning to user groups, not device groups. Win32 apps can be assigned to either user or device groups.+> For almost all app types and platforms, *Available assignments* are only valid when assigning to user groups, not device groups.+> +> The exceptions to this rule are:+> 1. Win32 apps can be assigned to either user or device groups as *Available*.+> 2. Apps targeting Android Enterprise fully managed devices (COBO) and Android Enterprise corporate-owned personally enabled (COPE) can be assigned to either user or device groups as *Available*. > > If managed Google Play preproduction track apps are assigned as required on Android Enterprise personally owned work profile devices, they don't install on the device. To work around this issue, create two identical user groups. Assign the preproduction track as "available" to one group and "required" to the other group. The result is that the preproduction track successfully deploys to the device.