Separate battery wear from workload-driven drain before replacement

Source facts

Endpoint analytics compares current full-charge capacity with design capacity. Its runtime estimate assumes usage comparable to plugged-in operation. Good capacity can coexist with short runtime because of demanding apps or a low-capacity battery design. App impact aggregates usage over 14 days across the app’s activities. Unavailable exported measurements appear as -1, not a measured negative result. Microsoft Learn.

Applicability

Use the battery-health report for a managed-device investigation after confirming its prerequisites. Identify the affected laptop, its model, the user’s actual work pattern, and which measurements are available.

DSE recommendation

Separate a capacity concern from a runtime complaint before proposing replacement. Review the application mix with the user and compare the affected device with an appropriate model cohort. Mark missing measurements explicitly in any exported analysis. Do not turn an app’s large share of battery use into a finding of inefficiency without examining what work it performed.

Verification

Ask for a controlled observation of the reported problem using an agreed, representative workload. Compare the resulting experience with the capacity and runtime trends, and document whether the evidence points toward wear, workload, or an unresolved cause. Have the hardware owner evaluate any proposed battery replacement against the actual device requirements. Preserve the measurement window and usage assumptions with the recommendation rather than promising a particular improvement.

Official references

Microsoft Learn: Battery Health Report in Endpoint Analytics.