Deploy patches safely and at scale with Patch Management
We’re excited to introduce sequential patching in Patch Management, now available for both subscriber and multi-tenant MSP deployments. This new capability brings a phased, stage-based approach to patch deployment, allowing IT teams to validate updates in controlled environments before rolling them out more broadly.
What’s new?
Patch Management already automates patch deployment across endpoints, but sequential patching adds an extra layer of control by validating updates on staging machines before automatically promoting them into production.
With sequential patching, updates are first deployed to designated test machines, typically closer to IT teams for faster validation and monitoring. Once predefined success criteria are met, those exact same patches are automatically promoted to production environments.
Success criteria can be customized and include:
- Time elapsed since the patch release
- Minimum number of successful installations
- Maximum number of failed installations
- Minimum number of days since the first successful deployment
If a patch shows unexpected behavior at any stage, it can be quickly excluded from further deployment, helping teams prevent potential disruption before it spreads.
Why is this important?
Deploying patches across an entire environment in one go can be risky. A single faulty update can cause widespread outages, reduce productivity, and put pressure on IT teams to respond quickly.
Sequential patching eliminates that risk by giving you greater control and visibility throughout the rollout process. Test first, validate confidently, and deploy at scale to move faster without compromising stability. The result: fewer incidents, smoother operations, and a better end-user experience.
When does this happen?
Sequential patching is available:
- From April 1 for subscriber accounts
- From May 4 for MSPs in multi-tenant environments
For more details, visit our documentation.