Check device and source coverage
Confirm which devices and connected sources are current before interpreting Atlas trends.
Read the coverage cards
Open Data Health before interpreting trends. Fleet reports enrolled devices and devices needing attention. Attribution links activity to people. Thinking-token coverage reports sampled exchanges with reported thinking tokens; Coverage Claims lists supported capabilities separately from observed activity.
Missing attribution or freshness is unknown, not zero or proof of complete coverage.
Resolve a gap
| Signal | Next action |
|---|---|
| Device never reported | Check deployment and Defender sign-in. |
| Device stopped reporting | Follow Defender troubleshooting. |
| Source not configured | Find the exact supported-tool setup. |
| Browser missing, CLI works | Check routing and certificate trust. |
| Source needs authorization | Check Workplace connections. |
Resolve one source/device, send a new test, and find the matching tool, person and time in Atlas. If status fails to load, inspect Fleet or the relevant setup guide before interpreting it as empty.
Before comparing trends
Confirm expected devices, enabled capture paths and current app connections in both periods. Use consistent dates and visibility. A smaller total can mean less usage or less coverage.