Package Assignments
Assigning RealmJoin packages through managed groups such as Main (Required) and Available, how conflicting assignments are prioritized, and converting basic subscriptions to managed.
Assignments decide which users and devices receive a package and how. You manage them in the Assignments section on the Overview tab of the package details page. How you assign depends on whether the package was subscribed as managed or basic.
Managed Subscription
Packages subscribed as managed come with RealmJoin-managed Entra ID groups, one per assignment type. You assign users and devices by making them members of the group that fits your scenario. The groups can be managed from both the RealmJoin Portal and Microsoft Entra ID.

By default the groups are named app - <platform> - <app name> (e.g. app - Win - Igor Pavlov 7-Zip) for Main, with a suffix such as (preview), (available), (uninstall) or (update) for the other types. The naming scheme can be changed in the group naming settings.
Managed groups
Main (Required)
RealmJoin or Intune will automatically install the application. These applications are mandatory and both solutions will continuously attempt to install the application, if not found on the device.
Available
The application will appear in the RealmJoin Agent tray and will require the user to initiate the download and installation manually.

The application will appear in Company Portal -> Apps and will require the user to initiate the download and installation manually.

Preview
Users and devices in the Preview group receive a new version of the package before the other groups, see Staged updates with preview.
Uninstall
RealmJoin or Intune will uninstall the package from the assigned users and devices.
For RealmJoin deployment, only Choco packages get an Uninstall group; Craft packages have none.
An Uninstall assignment takes precedence over Main and Available assignments, no matter on which level it is made: a device in the Uninstall group leads to the package being uninstalled even if the signed-in user is in the Main group, and vice versa. Only an Exclude assignment ranks higher, see Assignment priority.
Update
The Update group is created on demand and automatically onboards loose installations of a software title into management, so that new versions — including security patches — also reach those devices. It is the mechanism that keeps Intune Available apps up to date, by temporarily assigning outdated devices as Required.
For details, see Update Group.
Exclude
Needs to be explicitly activated through More > Exclude assignments (see Enable additional and restore default groups). Users and devices in the specified group will be excluded from assignments all over the package and associated managed groups.
Usage
The Exclude assignment of groups is used to ensure that users in the assigned exclude group are not managed within the package managed groups. It will not remove users from managed groups within the same package. Instead, it makes sure that certain packages are never assigned to the same user simultaneously.
For example, you can use the Exclude function to prevent a user, assigned to a 64-bit Adobe Reader package group, from also receiving the 32-bit version. Assign the 64-bit package group as an Exclude group to the 32-bit package.
Exclude assignments for Intune apps
Intune apps can be excluded from groups as well. On the app's detail page, open "More" > "Exclude assignments" in the Direct groups list, choose the intent the group should be excluded from (Required, Available or Uninstall) and add the group. RealmJoin creates a native Intune exclusion, so the group shows up under Excluded groups of that intent in the Intune admin center as well. The option is available for every Intune app, whether it is subscribed as managed or not.
Exclusions are listed together with the other assignments in Direct groups. Removing an exclusion only removes it for that intent; exclusions of the same group for other intents stay in place. Adding and removing exclusions is recorded in the audit log.
Intune, not RealmJoin, evaluates these exclusions:
Per intent — an exclusion only applies to the intent it was created for. Excluding a group from Required does not hide the app from the Company Portal if the group is also assigned as Available.
Exclusion wins — within the same intent, an excluded group takes precedence over included groups, including All users and All devices assignments. A group cannot be included and excluded for the same intent at the same time, so the picker only lists groups that have no assignment for the selected intent yet.
Same group type — exclude user groups from user-targeted assignments and device groups from device-targeted assignments. Intune does not support excluding device groups from user assignments or vice versa.
No uninstall — an exclusion only stops the assignment. The app stays installed on devices that already have it; use an Uninstall assignment to remove it.
Main app only — exclusions are created on the main Intune app. During a managed update, the preview app keeps its own assignments.
Changes reach devices with their next Intune check-in. See the Microsoft documentation on app assignments for details.
Assignment priority and conflicts
Managed packages can be assigned to users (via user groups or directly) and to devices (via device groups, see Assign Packages to Devices). Because a device and its signed-in user can end up in different groups of the same package, the RealmJoin backend resolves conflicts deterministically when it renders the configuration for a device.
In managed packages, group management is handled by the RealmJoin Portal, which uses the GUID of each group after creation. This enables the portal to identify the provisioning type associated with each group and to prioritize between them. This ensures deterministic behavior in scenarios where a user or device is mistakenly assigned to multiple provisioning groups.
For each package, the assignments of the signed-in user, of the user's groups and of the device's groups are collected and evaluated in this order:
Exclude — if any of the collected assignments is an Exclude assignment, the package is dropped entirely. Nothing else is evaluated, including Uninstall.
Uninstall — if any of the remaining assignments is an Uninstall assignment, the package is uninstalled, regardless of whether it comes from a user group, a device group or a direct user assignment.
Direct user assignment — a package assigned directly to the user (not via a group) takes precedence over all group assignments, whether from user groups or device groups.
Group assignments — user groups and device groups are treated alike and ranked by their provisioning type (high to low): [Update] - Preview - Available - Required If the user's group and the device's group have the same provisioning type, the user's group assignment is used.
Effectively, the prioritization order is (high to low):
[Exclude] - Uninstall - [Update] - Preview - Available - Required
Managed and classic priority cascade
The order above is the default managed cascade, in which an Available assignment wins over a Main (Required) assignment. If you prefer the opposite — a user or device that is in both the Main and the Available group gets the package installed as mandatory — switch to the classic cascade:
Managed cascade (default): [Exclude] - Uninstall - [Update] - Preview - Available - Required
Classic cascade: [Exclude] - Uninstall - [Update] - Preview - Required - Available
The cascade can be set on two levels:
Tenant-wide — in Settings > General > App Config, enable Classic priority cascade for managed apps. Changing the switch asks for confirmation and takes effect immediately for every user and every package that has no per-package override. See Managed App Priority Cascade.
Per package — in the package's Expert Settings, the Priority cascade setting overrides the tenant default for that package only: Use tenant default (recommended), Managed cascade or Classic cascade.
The switch only affects managed packages and only the ranking of Main against Available. Exclude, Uninstall, Update and Preview keep their position, and Basic packages always install as mandatory when any of their assignments is Required.
Assign and move members
The Managed members list shows all users and devices in the package's managed groups, with the group they are in.

Assign adds users or devices to the Main group.
Move to: [main] [preview] [available] [uninstall] moves a member from its current group to the selected one.
The remove icon removes a member from its group.
Members of nested groups are shown as indirect (nested) and can only be changed in the nested group.
To copy many members at once, e.g. from an existing group, use More > Bulk Operations on the managed group's own page.
Enable additional and restore default groups

The More button of the Direct groups list offers:
Enable update group / Disable update group - See Update Group.
Exclude assignments - Assign an Exclude group.
Restore default groups - Recreate managed groups that were deleted.
Basic Subscription (Legacy)
Basic packages do not have any associated Microsoft Entra groups. Use Assign in the Direct groups or Direct users list to assign groups, devices or users manually.
New assignments of a Basic package are Available by default. Use the [settings] link of an assignment to change this, see Assignment settings.


Migrating from Basic to Managed
RealmJoin Basic packages can be converted to managed. The conversion is not available for Intune Basic packages and for packages marked as Pre-release.
Convert the package
Open the Basic RealmJoin package and select More > Convert to managed app in the Direct groups list. The conversion starts immediately.

RealmJoin then:
creates the default managed groups and applies your tenant's automation defaults,
nests the previously assigned groups into the matching managed group: Required groups into Main, Available into Available, Uninstall into Uninstall,
adds directly assigned users to the matching managed group.
Settings made to the Basic assignments are adopted by the managed groups.


Optional: pull members into the managed groups
To replace the nested groups with direct members, open a managed group and select More > Pull members up. Select the nested group, choose Remove assignment to remove the nested group afterwards or Keep assignment to keep it, and click Execute.

Assignment settings
Each assignment in the Direct groups and Direct users lists has a [settings] link. It opens the Assignment settings, which override the package's expert settings for this one assignment. Viewing them requires CanSeeAppAssignmentSettings, changing them CanChangeAppAssignmentSettings.

Hidden - Hides the package from the user's list.
Mandatory - Installs the package as Required instead of Available. Not available for managed packages, whose assignment type follows the managed group.
Auto upgrade, Only in VDI / Ignore in VDI, Only on hybrid-joined devices / Ignore on hybrid-joined devices, Ignore on private devices, Deployment rate, Main app restrictions and User part restrictions - Same as the expert settings of the package, for this assignment only. Settings left unset follow the package.
Arguments - Installation arguments for this assignment, e.g. a different language.
Mandatory - Assigns the app as Required instead of Available. Not available for managed packages.
Update priority - Android apps only. How Managed Google Play updates the app: Default, Postponed or Priority.
Last updated
Was this helpful?