The Devices screen

Cross-check every device across your tools to catch agents that quietly stopped reporting and users who left but still cost you. Here's how to read it.

Device reconciliation lines up the same device across the tools that should all see it (your RMM, your security agent, your backup) and surfaces the ones that disagree. It's how you catch an agent that silently stopped reporting, or a person who left months ago but still holds licenses and agents you're paying for.

This is an optional capability. It reads nothing until you turn it on per connection (see Connect Microsoft 365), and it lives on its own surface: device findings never enter the Ledger or change your net-drift number. You can view devices per client, or org-wide, where every client's stale agents and coverage gaps roll up into one place.

What you're looking at

• Each row is a device, with who it belongs to and a badge for its overall state: Current when every tool has seen it recently, or a flag like Agent stalled or Offboarded.
• Each tool shows when it last saw the device, as plain text ("RMM 2h ago", "EDR 38d ago"), not a green or red light. A timestamp is honest; a status light would imply a judgment the raw data doesn't make. Times that are out of line read in red.
• The findings are what the timestamps add up to. One agent quiet while its siblings still see the box is a removed agent. Every tool quiet at once, for someone who left, is an offboarded user.

The kinds of finding

• Stale device and agent removed: a tool stopped reporting. These carry no dollar figure on their own; they're a coverage and security signal.
• Offboarded user: someone who left but still holds licenses. This one is priced, and the figure is always labeled approximate.
• Coverage gap: a device that isn't covered by a tool its class should run (for example, a workstation with no security agent). It's conversation-first and carries no dollars. Where a tool isn't connected at all, BillRecon says "can't verify" rather than inventing a gap.