Battery health report

The battery health report provides visibility into the health of batteries in your organization's devices and its influence on user experience.

The score helps you identify emerging hardware issues that might be impacting user productivity so you can proactively make improvements before users generate support tickets.

The insights show how much your score can improve by replacing batteries in affected devices. They also help you identify quickly failing batteries that can be replaced under warranty before they expire.

The battery health report can be used to:

• Plan battery replacements proactively to reduce downtime and improve user experience.
• Identify devices with poor battery still under warranty, and proactively repair/replace them.
• For devices with high battery capacity scores, review their associated resource performance report and consider extending their lifecycle usage to reduce costs.

Before you begin

Review the report

In the Microsoft Intune admin center, select Reports > Endpoint analytics > Battery health.

Battery health score

The battery health score provides an overview of laptop battery health. It's calculated as a weighted average of your organization's battery capacity score and battery runtime score, helping you identify batteries that need replacement.

The maximum capacity of a battery is the ratio of its full charge capacity against its design capacity. The full charge capacity shows the Watt-hours the battery can hold on a full charge now, while the design capacity shows the Watt-hours the battery could hold when it was new. For example, a maximum capacity of 50% on a battery with design capacity of 70 Watt-hours means that the battery now holds only 35 watt-hours on a full charge.

Battery capacity score

Based on the maximum capacities of batteries in your organization's devices, we create a score from 0 (poor) to 100 (exceptional). Your battery capacity score is the average for all devices.

The estimated device runtime is an estimate of the amount of time a device runs using a battery on full charge and assuming the system's usage pattern is comparable to when the device was plugged in. The Battery capacity score is calculated from the combined battery capacity and estimated battery drain rate.

Battery runtime score

Based on the estimated device runtimes for batteries in your organization's devices, we create a score from 0 (poor) to 100 (exceptional). Your battery runtime score is the average for all devices.

Insights and recommendations

The report provides a prioritized list of insights and recommendations to help improve your score:

Low battery capacity

These devices have batteries that hold less charge compared to what they were designed to hold. Devices with battery capacities below 60% are considered most impacted whereas devices with battery capacities between 60-80% are considered moderately impacted. The insights might contain one of these conditions independently or in combination with low runtimes.

For example, some devices might have batteries with below 60% capacity but still provide reasonable runtimes because their design capacities are high. Whereas other devices might have batteries with below 60% capacity and less than 3 hours of runtime, in which case they're a part of insights that highlight both gaps together.

Low estimated runtime

These devices result in poor user experience as they must be plugged in frequently. Devices with battery estimated runtimes below 3 hours are considered most impacted. Low runtimes are typically reported in combination with battery capacities.

Devices with less than 3 hours of runtime usually have poor maximum capacities and are included in insights that highlight both issues together. The exception is seen in the following scenario where even with high capacities, the batteries drain quickly because of power hungry apps. Either by design or because of poor energy usage efficiency.

Good battery capacity but poor runtime

Estimated runtimes might be low despite batteries having good maximum capacities. Low runtime is possible in two scenarios:

1. The device is running apps that drain the battery quickly. Users run applications that consume high power or inefficiently use power and need upgrading or replacing. Battery-powered devices can use the battery saver Windows feature to ensure that both user productivity and experience are protected.
2. The device has a battery that is designed to hold low charge. Procurement teams drive this decision.

Insights for this scenario highlight the devices for which the App Impact tab might provide more visibility into whether the user needs to use power hungry apps or whether the app's battery usage is unusually high due to inefficiency.

Report tabs

The report is organized into tabs, each providing a different view of related data and insights.

Device performance

Shows battery health metrics and a score for all battery-powered devices.

• Sort by a metric (for example, Max capacity) to identify devices with the lowest scores.
• Search for a device by name.
• Select a device to view its runtime trend, compare its score to the model's average in your organization, and see the top apps that consumed its battery in the last 14 days.
• Review the cycle count, which tracks how many times the battery discharges 100% of its capacity (not necessarily in one session). For example, if a battery discharges 50% on day 1, 30% on day 2, and 20% on day 3, the cycle count increases by 1.

Model performance

Displays battery health metrics and scores by device model to help identify issues specific to certain models.

OS performance

Shows battery health metrics and scores by operating system version, helping you determine if problems are tied to specific OS versions.

App impact

Summarizes cumulative battery usage per app over the last 14 days.

• View the number of devices affected and the percentage of total battery charge consumed by each app.
• Use this information to troubleshoot apps that may be draining battery excessively.

Battery information notes

• Estimated runtimes may be unavailable for battery-powered devices when there isn't enough data on battery drain.
• If the battery design doesn't report cycle count, that information won't appear in the report.
• For new batteries, limited data may result in a cycle count of 0* (zero with an asterisk).
• In rare cases, the battery count may exceed 2, which usually means the device is connected to a UPS or external batteries. Because this is unusual, an asterisk (*) is added when the count is greater than 2.

Limitations

• Some data points in the report may display Not available. When you export the report, unavailable data appears as -1 in the generated .csv file.
• Devices with batteries designed for low capacity (for example, those intended to hold a limited charge) will show low runtime. This behavior is by design. These devices appear under low-runtime insights, and the only way to improve runtime is to replace the battery with one that supports a higher capacity.