Microsoft is preparing a new Copilot Dashboard feature that shifts the focus from who has a license to who actually uses Copilot daily — and it’s targeting a general release in August 2026. The "power user insights" capability, listed on the Microsoft 365 roadmap this week, aims to pinpoint employees who are building habitual, sustained usage patterns with the AI assistant. For IT teams, it promises a more nuanced view of adoption than raw license counts ever could.

The concrete details: what roadmap 560705 adds

The new feature appears as roadmap ID 560705, categorized under Microsoft Viva and Microsoft Copilot. Microsoft’s entry states it will "help organizations understand who is building a habit" with Copilot by surfacing insights into power users — people whose usage is regular enough to indicate ongoing adoption rather than one-off experimentation. The feature is marked "In development" and is planned for general availability in August 2026 for Microsoft’s worldwide standard multi-tenant cloud.

Two important caveats: first, the August 2026 date is an estimate. Microsoft’s roadmap explicitly warns that release timelines and feature scopes can change. Second, the roadmap listing is light on specifics. There are no published thresholds for what counts as a power user, no details on available filters, and no mention of how far back the dashboard will analyze usage data. It’s also unclear whether the new insights will replace or complement the existing Copilot Dashboard classification that groups users into power, habitual, novice, and non-Copilot buckets based on usage frequency and consistency. Administrators should not assume those existing categories will remain unchanged.

What this means for IT admins

For the people managing Microsoft 365 environments, power user insights are more than a new metric. They close a long-standing gap between knowing who has a Copilot license and knowing who actually integrates the tool into daily work. Here’s how that plays out in practice.

License ROI gets sharper. Many organizations assigned Copilot licenses in bulk, then struggled to measure whether the investment paid off. A dashboard that distinguishes casual dabblers from habitual users gives license managers a clearer signal. If hundreds of licenses are assigned but only a fraction of employees use Copilot several times a week, the financial argument for renewal weakens — or shifts toward targeted enablement for the groups that are lagging.

Adoption programs get a data backbone. Training teams can stop guessing who needs help. Power user lists become a source for identifying "champions" — people whose repeatable workflows are worth documenting, sharing, or turning into internal case studies. Conversely, groups with low habitual-use scores can receive targeted coaching or nudges inside Teams and Outlook.

Governance and policy questions arise. Any tool that classifies individual employees by behavior raises privacy and performance-review concerns. Microsoft has not said whether managers will see power user labels for direct reports, but admins should assume the feature will be visible to those with dashboard access. Without clear internal policies, there is a risk that "power user" becomes an unofficial performance metric — a dangerous shortcut that equates high click counts with high value. The dashboard tells you who is using Copilot a lot, not whether they are using it well.

What this means for business leaders and end users

For business decision-makers, the new insights can inform the next budget cycle. Instead of renewing a flat number of licenses, leaders can ask: are the right people using Copilot? Does habitual use correlate with outcome metrics the business cares about? The dashboard alone won’t answer those questions, but it will supply the raw data for internal analysis.

For employees who become power users, the label can be a double-edged sword. On the positive side, being recognized as a habitual Copilot user may open doors — invitations to beta programs, early access to new features, or leadership opportunities within adoption communities. On the flip side, an employee who uses Copilot heavily may feel pressured to maintain that pace, or may be stigmatized if they rely on the tool for tasks that peers complete without AI assistance. Internal communication plans should anticipate these reactions.

How we got here: a measured build-up to habit tracking

Microsoft’s approach to Copilot analytics has evolved in deliberate steps. When the Copilot Dashboard launched in the Microsoft 365 admin center, it focused on aggregate adoption metrics: how many licenses were assigned, how many users were active, and which apps saw the most Copilot usage. Soon after, the dashboard introduced a more granular breakdown, classifying users into segments like "power user" and "novice" based on their activity patterns. Viva Insights, which powers the dashboard’s analytics engine, tapped into Microsoft Graph signals to build those profiles.

Throughout 2025 and early 2026, Microsoft added dimensions such as meeting summaries generated, emails drafted, and chat assists — all aiming to capture the breadth of Copilot usage rather than its depth. The April 2026 Copilot wave, covered in the company’s tech community blog, brought improvements to prompt suggestion quality and expanded Copilot’s reach inside Loop and Whiteboard, but the dashboard remained largely unchanged.

The new power user insights item signals a shift in philosophy: from measuring "/if/ people use Copilot" to "/how/ they use it." It aligns with the broader industry push toward habit-based engagement metrics, borrowed from consumer apps. A one-time heavy user is less valuable than a daily lightweight user who integrates the tool into a routine. Microsoft’s roadmap suggests that defining and surfacing that routineness will be the dashboard’s next big leap.

What to do now: actionable steps before August 2026

No configuration changes are required yet, but proactive teams can start preparing. Here’s a checklist.

  1. Map who needs access. Decide which roles should see power user data: IT admins, helpdesk leads, adoption specialists, business unit heads, and HR or privacy stakeholders. Review existing Copilot Dashboard access controls — users need at least the Reports Reader role or a custom Viva Insights admin role to view certain analytics. Confirm that the right people have the right permissions before the feature lights up.

  2. Define success criteria internally. Don’t wait for Microsoft’s definitions. Convene a cross-functional group to agree on what a reusable, valuable Copilot workflow looks like in your organization. Is it generating first drafts of contracts? Summarizing long email threads? Building PowerPoint decks from prompts? Without internal definitions, the power user label will be hollow.

  3. Draft a responsible use policy. Anticipate that some managers may over-index on power user status as a performance indicator. Create a written policy that separates Copilot adoption metrics from employee evaluations. Include language that clarifies data is anonymized at the dashboard level (if it is) or that individual-level data must not be used punitively. Run it by legal and HR early.

  4. Set up a feedback loop. Identify potential power users — through existing dashboard segments or anecdotal feedback — and interview them. What works? What frustrates them? This qualitative data will be invaluable once the quantitative insights arrive, helping you separate signal from noise.

  5. Monitor roadmap updates. Microsoft may publish additional documentation or refine the feature description as the August 2026 window approaches. Check the Microsoft 365 roadmap and the Copilot release notes periodically for threshold details, API availability, or tenant configuration options.

Outlook: what to watch after the rollout

Once power user insights go live, expect Microsoft to tighten the connection between usage patterns and personalized Copilot experiences. The Copilot Dashboard could eventually surface tailored learning modules for users who are stuck in novice patterns, or prompt admins to enable advanced features for teams with proven high engagement. Privacy advocates, meanwhile, will scrutinize how user-level activity data is stored and shared. Admins who have clear internal policies by rollout day will be in a much better position to extract value from the new data without stepping on landmines.