M365 Changelog: Microsoft Copilot Dashboard: New usage intensity and retention insights – Jan 23, 2025

MC986522 – Microsoft Viva Insights will improve adoption insights for Microsoft 365 Copilot by enabling admins and leaders to view usage intensity and retention metrics in the Microsoft Copilot Dashboard. Admins and leaders will be able to explore Microsoft 365 Copilot usage frequency at various thresholds, compare top groups by usage intensity, and measure recurring usage of Copilot over time.

A Microsoft 365 Copilot license is not required to view the adoption insights in the Copilot Dashboard. The users included in the analysis population must have a Microsoft 365 Copilot license.

When this will happen:

General Availability (Worldwide): Microsoft will begin rolling out late January 2025 and expects to complete by late January 2025.

How this will affect your organization:

Admins and leaders with access to view Copilot dashboard will find these updates to the Adoption tab.

• New cards with highlights for usage intensity and retention with the option to click explore more for additional details.
• A new data visual to group the number of active users by number of actions taken.
• A new data visual to measure the number of weeks of consistent Copilot usage.
• A new data visual to measure the number of returning Copilot users over time.

In the Copilot Dashboard, admins and leaders can measure the frequency and consistency of Copilot usage:

The new features will be available by default.

What you need to do to prepare:

These existing admin controls will continue to be respected after the rollout:

• If an admin or leader has not been provided access to the Microsoft Copilot Dashboard, this feature will be unavailable to them. Learn more about providing access to Copilot Dashboard.
• Privacy thresholds set by the admin will continue to be respected with these insights.

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review and assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.