Be able to add uninstall-only scripts for discovered apps.

Option to remove devices from Radar Tracking groups when they get the latest version.

Support for users to define their own dependencies. Support for having dependencies be created as separate apps in Intune.

On-demand and periodically sent reports for app update and deployment information

Support categories, developer, other properties that exist in Intune but not in Robopack - and this support needs to exist for flows. Categories, minimum OS version, comments, developer…

Support analysis and deployment of ARM Windows apps.

Support the Intune features for specifying an App availability date and time, and an app installation deadline date and time.

US, Aus, etc - local copies of Robopack that ensures their data is only stored in their own region

We would like to be able to use the Test script function with different Custom app settings when using multiple tenants. Today it will only use the All tenants configuration.

More items for notifications, allow notifications for specific tenants

Support multifactor authentication for local Robopack accounts

Enhance Package Options so administrators can define precise device requirements before an application installation or update runs.

Key options are Configure additional requirement rules and Script-based requirement checks.

These should allow administrators to define custom logic that determines whether installation proceeds and better align with Intune UI and functionality.

Administrators can implement logic such as:

Install X only if Y is not already installed.

This prevents unintended downgrades or overwriting existing software and supports environments where different editions of the same application coexist (e.g., Reader vs. Pro).

When removing an App from a Patch Group or Patch Flow, the wizard asks to also remove the App from Intune. But it never removes the Entra Groups which were used for it (Available, Required and Uninstall). In some cases, this could be useful (and in others, the groups must be kept).

A toggle to also delete the corresponding groups would help and the admin can decide what to do. Naming the groups in the interface will help with that decision. 

Support for uploading new/multiple versions of custom apps, similar to the way that multiple versions are available for some Instant Apps.

Supporting French, German

Allow the upload of a newer MSI file for existing custom apps.

When a new app is published, Roboback will clone the existing wave assignments, but the old (superseded) app keeps the same group assigned, and this creates issues.

Superseded apps are NOT excluded from evaluation(according to Microsoft), so when we have a required app with 3 supersedence, all assigned, then IME will trigger evaluation for all 4 apps.

You can do the math for how many apps you have set as required and how many superseded versions set in Robopack will run simultaneous in background each hour.

Allow users to switch between tenants/Organisation that are registered with the same parent Organization.

This proposal suggests extending Robopack with a new capability that allows software to be installed simply by copying files, without requiring traditional installers (MSI, EXE, or scripted deployment). Many enterprise applications—especially portable tools—only require file placement and minimal configuration. Enabling Robopack to manage these “copy‑installations” would significantly simplify and speed up software distribution.

Ability to move licenses between organizations (MSP)

As an MSP, you might want to rebalance licenses between various organizations this requires manual intervention by Robopack support at the moment