One change, big ripple: the Copilot Dashboard’s adoption landing page will now default to showing all Copilot users — both Microsoft 365 Copilot (licensed) and Copilot Chat (unlicensed). For anyone tracking rollout or ROI, your topline adoption numbers are about to move.
Core point: the default adoption view will count unlicensed Copilot Chat alongside licensed M365 Copilot usage, with a License filter to switch between All, Licensed only, or Copilot Chat (unlicensed).
What’s actually changing
Per the Microsoft 365 roadmap, the Viva Insights Copilot Dashboard adoption page is being updated to present a unified “All” view. A new License filter lets you pivot between:
- All (licensed + Copilot Chat)
- M365 Copilot (licensed)
- Copilot Chat (unlicensed)
This builds on existing Copilot Dashboard behavior documented by Microsoft: tenants with at least one Copilot license can see adoption insights for licensed users and Copilot Chat usage by users without a Copilot license, with license-type filtering available.
How it works and constraints to know
- Availability: The Copilot Dashboard in Viva Insights can be accessed by Microsoft 365/Office 365 business or enterprise customers with Exchange Online. A separate Viva Insights or M365 Copilot license is not required just to view the dashboard. Feature depth still depends on your tenant’s licensing.
- Scope: “Active Copilot users” are those who performed at least one Copilot activity in the last 28 days. Privacy rules (minimum group sizes) still apply to breakdowns.
- Data freshness: The dashboard refreshes daily and shows a rolling, previous 28-day window; expect a lag of up to about six days, and an additional delay (up to a week) before newly licensed users appear.
Why engineers and leads should care
If you’ve been reporting adoption against paid Copilot licenses, the new default can inflate topline usage if unlicensed Copilot Chat is substantial in your org. That’s not wrong — it’s a real signal of organic AI usage — but it will muddy like-for-like comparisons unless you standardize which License filter is in play.
In practice, this changes a few things:
- Reporting: Align on definitions. For paid-rollout KPIs, use the “M365 Copilot (licensed)” filter. For org-wide AI behavior, use “All.” Mixing these will break trend lines and ROI narratives.
- License planning: The “All” view will surface where Copilot Chat is doing the work. Useful for identifying cohorts to prioritize for licensing — or where Copilot Chat suffices.
- Benchmarks and targets: If you’re benchmarking adoption or setting quarterly targets, freeze the filter choice now and communicate it. I’d be surprised if leadership decks don’t see a jump simply due to the default changing.
- Training and change management: Different usage patterns between licensed apps (Word, Outlook, Teams) and Copilot Chat may call for different enablement. Split your programs accordingly.
What I’d watch
- Audit your existing dashboards and executive reports: confirm the License filter and restate baselines with a clear definition.
- Monitor the data lag: the 28-day window with a few days of delay can mask fast changes post-rollout or training pushes.
- Access and segmentation: if you rely on org/job-function filters, ensure your Entra or uploaded org data is accurate; privacy thresholds will still hide small groups.
The practical takeaway: decide now whether adoption means “licensed M365 Copilot” or “all Copilot usage.” Set the License filter to match, lock it for reporting, and annotate any historical comparisons. That’s the difference between a clean ROI story and a data reconciliation exercise next QBR.