All ideas

Use this description for Intune updates like it shows in SCCM updates: Instead of generic application description used in the Intune updates today:

Currently the maximum of 14 days is less than our production release of patches. We need this increase to be able to match our production patching deadline. For us at least 30 is needed.

When you publish the initial app version, and a new version comes along. I might have the need to keep the older version for 1 or 2 iterations while the update package I most likely are only interested in keeping the latest version in Intune.

On devices running certain ConfigMgr roles, the $env:windir\ccm\logs folder is in a different location. it would be great if the ScriptRunner config could handle putting the default logs in the detected destination *\logs folder instead of creatin...

Change the save behavior to now show error "You haven't imported or generated" certificate.

Our developers mostly now use Java JDK 11.x.x (although it would be useful to also add 13.x.x and 14.x.x) I understand we need to download these manually and add them to the offline area, however only JDK 8 exists in the list of updates.

Service restart notification or status on Advanced Tab of Publisher will be helpful to see the state of the patch my pc service without having to go into the services.msc

Option to not append republished date text to name when republishing

Would like to add the Time Zone to the Teams/Slack webhook. Would be helpful to more easily identify when the reports complete since the message itself will show in the destination machine's

When the Code Signing certificate changes, all Applications should have their detection method updated using the new signing certificate. Since there is no way to "republish" an application, the only options currently are to wait until an app upda...