Name the device cohort before sharing endpoint analytics results

Source facts

Endpoint analytics custom device scopes filter supported reports using one scope tag. They start disabled, can need up to 24 hours after activation, and require at least ten devices. A selected scope persists across supported report pages. Deleting its underlying tag breaks the scope. The supported reports listed are startup, work-from-anywhere, application reliability, and battery health. Microsoft Learn.

Applicability

Identify the audience for the report and the actual tag membership. Check report support explicitly rather than assuming every analytics page can use the same saved cohort.

DSE recommendation

Name the scope after its intended population and record the underlying tag identifier. Have the endpoint owner review membership before activating it. Include the selected scope in screenshots, exports, and discussions so an audience-specific score is not presented as the whole organization. Coordinate tag cleanup with report owners rather than treating the tag as an unused label.

Verification

After processing, compare a known included device and an excluded device with the intended population. Move between supported reports and confirm that the selected scope remains the expected one. When returning to an organization-wide review, explicitly choose All Devices and verify the change. Record processing or insufficient-data states separately from a measured poor result. Preserve the scope definition with the analysis so later readers can explain which endpoints the conclusion represents.

Official references

Microsoft Learn: Device Scopes.