A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Increase the Maximum Supported File Count for Application Deployments
ncreasing the maximum number of files supported by the application beyond the current limit of 997 would improve usability, scalability, and operational efficiency. Several folders used for software packaging and deployment, such as Oracle-related...
MSP Customers: Allow user access with EntraID groups without connecting to Intune
Currently, the ability to grant access through Entra ID groups is only available when the Company is connected to an Intune tenant. As an MSP, I may want to create a Company in the Cloud Portal to manage my MSP child customers without connecting m...
Allow Custom Detection Scripts to be pasted in and edited from the cloud portal
Currently, when adding a custom detection script to an app, you must import a .ps1 file locally from the computer. Once added, it is read only and not editable from the portal. It would vastly speed up our workflow if custom detection scripts coul...
MacOS App Support for Patch My PC OnPrem Publisher
A lot of MEM customers are also using MacOS devices and Patch My PC has a MacOS Apps Support Feature in the Cloud product (in Public Preview). It would be great if this was also supported within Patch My PC's OnPrem Publisher Product. The way of p...
I'd like to suggest a Governance Policies feature within Advanced Insights that allows administrators to create compliance policies against any available data point collected by ConfigMgr and surfaced through Advanced Insights. Something which wou...
Add MSI/MSP installation timeout configuration to Patch My PC Cloud
Patch My PC Publisher allows customers to control how ScriptRunner handles MSI and MSP installations that run longer than expected. In Publisher, customers can enable a ScriptRunner-enforced MSI/MSP installation timeout. When enabled, ScriptRunner...
Sometimes different applications can share the same executable name. PMPC doesn't care where the process originates from when "name.exe" is specified in "Manage conflicting processes", it just wants to shutdown whatever application is running that...
In the pop-up messages for Conflicting Processes there should also be an estimate for the user so they know how long it'll take for each update to run.