Patch My PC Ideas & Feedback
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:
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:
To have the ability to mix assignment types within a single PatchMyPC Cloud deployment (e.g., “App without Assignment” & “App Update Only”). Specifically:
Create App Update Only assignments in Update Rings to pre-defined update groups (pilot → broad → final), managed in PatchMyPC Cloud.
Create App without Assignment for the base Install application in Intune in the final update ring. So that assignments, RBAC ownership, and scope tags are managed within Intune, and required application installs adhere to update ring delays.
Enabling a single application deployment that supports separation of duties: PatchMyPC Cloud owns update-ring automation, while Intune owns application assignment governance.
Why: the update rings can use consistent, pre-set groups. And the base application’s assignments could remain under Intune RBAC + scope tagging for affiliate / departmental ownership, while adhering to update ring schedules. All in a single application deployment.
Today, we can end up with one tool “owning” assignments when we actually want ownership split:
Update rings are most efficient when configured once (pilot/broad/final) and reused.
Base app assignment is often controlled by Intune RBAC, scope tags, and local app owners who should decide “who gets the app” independently of patch automation.
