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:
Add the option to configure a delay before Publisher updates an existing App or Update in Intune, similar to ConfigMgr apps.
What Patch My PC product is this new application request for?
Patch My PC Enterprise
ADMIN RESPONSE
Jul 7, 2026
The Publisher Dev. Team has started to analyze what will be required to bring this Feature to the Product and anticipates Delivery before Q4 '26.
Cody Mathis
Jul 10, 2026
Hi there, sorry for the delay. This will be in the next preview build of the Publisher and, of course, in the subsequent production releases.
It can be configured individually for Intune Apps and Intune Updates. The option is available globally in the Intune Options and can be overridden at the Vendor and Product level.
One of the core issue this feature will address is that while the phased deployment strategy for Intune Updates works well, problems arise when a new version of an application is published as an Intune App.
Currently, when a new version becomes available, localized admin teams in large organisations, spread across multiple countries, can add required assignments in the Intune Admin Center, particularly to support Autopilot scenarios. This bypasses the intended phased deployment process set out by the organisation and leads to new versions being installed on client devices before proper testing can be completed.
To address this, the request is to introduce a delay mechanism specifically for Intune apps, similar to the one already available for ConfigMgr apps in Publisher (Delay in-place upgrade of applications). This would allow larger customers with the complexity of localized IT teams to:-
Delay availability of the new Intune Apps (e.g. 9 days) while testing is completed and phased deployments have ruled out issues with the new version
Prevent localized teams from prematurely assigning new versions of Intune Apps as required before they are tested
Preserve the integrity of internal test and deployment schedules
Hi there, sorry for the delay. This will be in the next preview build of the Publisher and, of course, in the subsequent production releases.
It can be configured individually for Intune Apps and Intune Updates. The option is available globally in the Intune Options and can be overridden at the Vendor and Product level.
Good morning everyone,
can you explain, what the new status of "UNDER CONSIDERATION" means?
Is this a step forward or a step backward in your development process?
Best regards
Peter
Amazing, that you implement that now!
This will become a life saver and pushes once more the productivity of Intune Admins!
One of the core issue this feature will address is that while the phased deployment strategy for Intune Updates works well, problems arise when a new version of an application is published as an Intune App.
Currently, when a new version becomes available, localized admin teams in large organisations, spread across multiple countries, can add required assignments in the Intune Admin Center, particularly to support Autopilot scenarios. This bypasses the intended phased deployment process set out by the organisation and leads to new versions being installed on client devices before proper testing can be completed.
To address this, the request is to introduce a delay mechanism specifically for Intune apps, similar to the one already available for ConfigMgr apps in Publisher (Delay in-place upgrade of applications). This would allow larger customers with the complexity of localized IT teams to:-
Delay availability of the new Intune Apps (e.g. 9 days) while testing is completed and phased deployments have ruled out issues with the new version
Prevent localized teams from prematurely assigning new versions of Intune Apps as required before they are tested
Preserve the integrity of internal test and deployment schedules