Warranty Tracking

The Warranty feature on a configuration policy controls when Breeze raises an alert as a device’s manufacturer warranty approaches expiry. You set two thresholds — a warning window and a closer urgent window (both in days) — and Breeze evaluates each device’s known warranty end date against them, opening an alert when the device falls inside a window.

Warranty alerting is opt-in. A device with no assigned, active warranty policy is never alerted, even if Breeze knows its warranty date. You turn it on by adding a Warranty feature to a policy and assigning that policy to the devices you care about.

Where warranty dates come from

Breeze stores one warranty record per device (device_warranty) with the manufacturer, serial number, coverage status, and start/end dates. A background worker runs every 6 hours and re-checks each device about once every 7 days (50 devices per run), looking the serial number up against the vendor providers your instance has configured — Dell (official API credentials) and Lenovo (official API ClientID and/or the credential-free opt-in); Apple/AppleCare coverage is reported by the macOS agent. HP has no lookup yet, so HP devices stay unknown. Vendor configuration is described under Environment → Warranty lookups. The Warranty tab does not set warranty dates — it only configures the alert thresholds evaluated against whatever dates the sync has discovered. Devices whose warranty status is still unknown, or that have no end date, are skipped.

Note

Devices on an active AppleCare subscription are never alerted. The reported “end date” for a recurring subscription is the next renewal date, not a true expiry, so it perpetually rolls forward — Breeze treats it as covered and clears any stale expiry alert.

Configure in a policy

1. Open Fleet Management → Config Policies and select (or create) a policy, then open its Warranty tab.

2. Toggle Enable warranty expiry alerts on.

3. Set the Warning threshold (days) — Breeze raises an info-severity alert once a device’s warranty is this many days or fewer from expiring. Default 90 (range 1–365).

4. Set the Urgent threshold (days) — inside this closer window Breeze raises a low-severity alert instead, and once the warranty has expired, a medium-severity one. Default 30 (range 1–365). (The API and AI tools still call this field criticalDays.)

5. Save, then assign the policy to the scope you want covered (partner, organization, site, device group, or device).

The settings are stored inline on the policy’s Warranty feature link. Resolution follows the standard closest-wins hierarchy — a device-level policy overrides group, site, organization, and partner. A policy created partner-wide (all organizations) applies these thresholds across every organization you manage, so you can define one warranty standard for your whole fleet. See Configuration Policies for ownership and assignment details.

What alerts fire

Warranty expiry is a date-driven lifecycle notice, not a device fault, so it never raises a critical or high alert — it stays out of active-critical counts and severity-keyed escalation rules. Breeze picks a single severity per device based on days remaining until the warranty end date:

Condition	Severity	Alert
Warranty already expired (0 days or past)	medium	“Warranty expired: device”
Within the urgent threshold	low	“Warranty expires in N days: device”
Within the warning threshold	info	“Warranty expires in N days: device”
Outside both thresholds	—	No alert (any existing one is auto-resolved)

Each alert carries the manufacturer, serial number, end date, and days remaining. Only one open warranty alert exists per device at a time — Breeze won’t create a duplicate while one is active, acknowledged, or suppressed. Instead, each warranty evaluation re-grades that open alert in place to the severity in the table above, so it steps from info to low to medium as the expiry date approaches (alerts raised under the older high/critical grading are corrected the same way). A re-grade updates the alert’s title and severity, records the previous severity on the alert and in the audit log, and sends no new notification; lowering the severity also cancels any escalation step still pending from the old grade. When a device moves back outside the thresholds (or becomes an AppleCare subscription), Breeze auto-resolves the open alert. A warranty alert a user has dismissed stays dismissed for that end date and won’t be recreated; if the warranty is later renewed to a new end date and approaches expiry again, alerting resumes.

Related

• Configuration Policies — how to create, own, and assign policies
• Alerts — reviewing, acknowledging, and resolving the alerts this feature raises
• Devices — where a device’s warranty status is shown