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:
It would be very good if new updates could be controlled separately via the sync schedule and the update rings. So that the new updates for the first ring are always distributed on day X of the month and then after X days for the remaining clients independently of the sync schedule.
Mitchell Coates
Jan 12, 2026
At present, we’re running a hybrid setup with an on‑premises Patch My PC publisher alongside the Patch My PC Cloud Portal integrated with Microsoft Intune. While the Cloud Portal simplifies management, it currently lacks some deployment controls available in the on‑prem publisher, particularly around scheduling update‑only applications.
Due to these limitations, deployments default to ASAP, which prevents us from aligning software updates with our established Patch Tuesday cadence. Although an update ring feature is in development, there are still constraints around minimum ring delays that make it unsuitable for our current deployment model.
Until these gaps are addressed, we’re unable to rely on the Cloud Publisher alone and will continue using the local publisher to meet our patching requirements.
We need to apply updates immediately after synchronization to a test group of users. Following this, we plan to roll out the updates to all other users five days later. Currently, we synchronize only once a month,
We need to be able to apply updates immediately after sync to a test group of user. Then, we push to everyone else 5 days after. We only sync once a month in parallel with MS patch Tuesday. Update rings are nice, but the 30 day gap between rings make where we can't do this type of scheduling.
At present, we’re running a hybrid setup with an on‑premises Patch My PC publisher alongside the Patch My PC Cloud Portal integrated with Microsoft Intune. While the Cloud Portal simplifies management, it currently lacks some deployment controls available in the on‑prem publisher, particularly around scheduling update‑only applications.
Due to these limitations, deployments default to ASAP, which prevents us from aligning software updates with our established Patch Tuesday cadence. Although an update ring feature is in development, there are still constraints around minimum ring delays that make it unsuitable for our current deployment model.
Until these gaps are addressed, we’re unable to rely on the Cloud Publisher alone and will continue using the local publisher to meet our patching requirements.
We need to apply updates immediately after synchronization to a test group of users. Following this, we plan to roll out the updates to all other users five days later. Currently, we synchronize only once a month,
We need to be able to apply updates immediately after sync to a test group of user. Then, we push to everyone else 5 days after. We only sync once a month in parallel with MS patch Tuesday. Update rings are nice, but the 30 day gap between rings make where we can't do this type of scheduling.
I would also like to be able to schedule updates for a particular day. Not just publishing date plus a set number of days
I need to schedule on a certain day and time per goup
Would be nice if there was progress on this.
Is there a schedule for when the feature will be released?