Patch Management
Run patching as a controlled lifecycle, not a one-off task.
Patch Management in Breeze turns endpoint updates into a governed, auditable lifecycle. Teams can move from discovery to approval, deployment, and rollback using the same operational surface.
Full Patch Lifecycle
Core workflows include:
- scanning for available updates
- approving, rejecting, or deferring patches
- deploying approved patches through job execution
- rolling back selected updates when required
Organization-Scoped Approval
Approval decisions are tenant-scoped, which is critical for MSP operations. A patch approved in one organization does not automatically propagate to another.
Patch Job Visibility
Patch jobs expose per-device outcomes and status progress, making it easier to identify affected cohorts and resolve failures quickly.
Compliance and Reporting
Patch posture can be summarized for operational review and customer reporting. This helps teams track patch hygiene as an ongoing service metric rather than a one-time action.
Why Teams Use It
Patch Management reduces operational risk by replacing ad-hoc update behavior with controlled approvals, traceable execution, and rollback paths.
Capabilities
Approval-First Lifecycle
Patches move through pending, approved, rejected, or deferred states before deployment.
Org-Scoped Decisions
Patch approval decisions are isolated per organization to support MSP multi-tenant operations.
Patch Job Progress
Job records track total, completed, failed, and pending device outcomes across each rollout.
Rollback and Audit Trail
Rollback workflows and patch actions are logged for change governance and investigation.