SeatReaper
Entrar

Retired devices still billing: finding dead endpoints in RMM, EDR and backup

Por SeatReaper · 14 de novembro de 2026 · 4 min de leitura

Os artigos do blog são em inglês.

When a person leaves a client, someone usually opens a ticket. When a laptop dies, gets replaced or ends up in a drawer, nobody does. The machine stops checking in, but it stays in the RMM, the EDR console and the backup portal, and each of those tools keeps counting it toward the monthly bill.

One dead laptop might be three or four line items: an RMM agent, an EDR endpoint, a backup seat and sometimes an antivirus license. Across a few dozen clients, retired devices add up as quickly as unused Microsoft 365 licenses, and they are easier to miss, because no offboarding checklist covers them.

Why dead devices linger

  • Hardware fails before anyone uninstalls anything. A laptop with a dead motherboard cannot run an uninstaller, so its agents are never removed.
  • A reimaged machine comes back as a new device. The old record stays behind next to the new one, with the same name and an old last check-in.
  • Offline is not removed. Most consoles keep an offline device listed, and many keep billing for it, until someone deletes it.
  • Every console keeps its own list. Removing a device from the RMM does nothing in the EDR or backup console, and the reverse.

Where to look, tool by tool

  • RMM: sort devices by last check-in. Anything that has not checked in for weeks is a candidate, unless it is a seasonal machine or a spare.
  • EDR and antivirus: sort endpoints by last seen. A device the EDR has not seen in two months is not protected anyway.
  • Backup: look at the date of the last successful backup, not the last attempt. A device whose backups stopped a month ago is either retired or a backup problem, and both need a decision.
  • Intune and Entra ID: these are not usually billed per device, but they are where you confirm whether a machine is really gone.

Intune can tidy up on its own with device cleanup rules, which take a value between 30 and 270 days since last check-in. Note what they do: they hide stale devices from Intune, they do not wipe or retire them, and "devices hidden from Intune aren't removed from Microsoft Entra ID." A hidden device can also reappear if it checks in again.

Entra ID has its own guidance for stale devices: a device is stale when its activity timestamp is older than the timeframe you choose. The routine Microsoft describes is to disable the device first, wait a grace period, then delete it. Deletion cannot be undone, and it also deletes the BitLocker recovery keys stored with the device, so back those up first.

Dead in one tool is not dead everywhere

Before removing anything, compare the tools against each other. A device the RMM has not seen in 60 days but whose backups ran last night is not retired: its RMM agent is broken. A device that checks in to the RMM every day but has not backed up in a month has a backup problem, not a billing one.

Only a device that every tool agrees is gone is safe to remove. That cross-check is also what makes a cleanup easy to explain to a client: you are not guessing, every console says the same thing.

A safe cleanup routine

  1. Pick your thresholds. No check-in for 60 days in the RMM or EDR, and no successful backup for 30 days, are reasonable starting points. Shorten them for servers, lengthen them for clients with seasonal staff.
  2. Cross-check every candidate across the RMM, EDR, backup and Intune, matching by device name.
  3. Ask the client about anything that might be a spare, a loaner or a laptop someone took home. A one-line list with names and last-seen dates is usually enough.
  4. Keep what retention requires. Before removing a backup device, check how long its data must be kept and whether removal deletes it.
  5. Remove the device from each console, then disable it in Entra ID and delete it after your grace period.
  6. Check the next invoice. The saving is only real once the next bill or sync shows the device gone.

It is a security task too

Dead device records are not only a cost. They hide real gaps: a machine that dropped off the EDR but is still somewhere on the network looks exactly like one that was retired. The CIS Controls start with the asset inventory, asking organizations to review and update it "bi-annually, or more frequently", and to address unauthorized assets weekly. A monthly device cleanup covers both and gives you evidence for cyber insurance questionnaires.

How SeatReaper helps

SeatReaper reads the RMM, EDR and backup tools MSPs already run, including N-central, Datto RMM, NinjaOne, CrowdStrike, SentinelOne, Huntress, Sophos, Webroot, Cove and Acronis, and flags a dead device still billing only when every connected tool agrees it is gone. A device that checks in to Intune or any other tool is left alone.

Each dead device becomes one item in the queue, listing every tool still billing for it, the last check-in or backup in each, and the monthly cost from your price book. Owners can change the 60 and 30 day thresholds under Settings > Price book. When the next sync shows the device is gone, the saving counts as verified.

For the people side of the same problem, see the MSP offboarding checklist.

SeatReaper is free for up to 3 client tenants. Create an account to see which of your clients' devices are still billing.