Feature Requests (Product)

In the On-Prem Publisher, the Intune Scan Wizard provides a clickable link under the Device Count column that reveals which devices have a specific app installed, along with the app version. It would be helpful to include this same functionality i...

Currently, ConfigMgr Apps made by Publisher have an administrative comment something like "Created by Patch My PC Version 2.1.99.0". This feature request is to provide the abiliy to customise this comment attribute via right-click option at the pr...

I am writing to propose the development of an integration between Patch My PC Cloud and ServiceNow. The goal of this integration is to automate the creation and closure of change tickets for application updates, thereby streamlining our update man...

When using Update Rings and especially when you have rings that have a significant number of days delay it would be really helpful to have some kind of easy-to-read indicator of the date & time of when each ring will take effect. Currently whe...

Similar to the On-Prem PatchMyPC Power BI Reporting, it would be valuable to have a similar feature - such as the example provided here: PatchMyPC Intune Power BI Reports. The goal is to provide a comprehensive, visual overview of patch compliance...

Currently, Patch My PC Cloud does not support creating update-only assignments for macOS deployments. This limitation is understood to stem from Microsoft Intune, which does not provide the same requirement rules that Patch My PC leverages for Win...

It would be helpful to be able to change the format of alerts, or provide a json formatted webhook for alerts in other platforms (eg ServiceNow)

Please add the future from scappman that you can deploy registry keys and values using patch my pc it deployes it just like an app

It would be nice to see how many apps/updates have been published, like the telemetry data in the on-premise publisher. It helps to give people a quick view on how beneficial the solution is

If a Windows Default template exists, the Conflicting Process behavior from that template is applied to all future deployments - even when the template has not changed this setting from its default value. Because the template’s values take precede...