Copilot Dashboard Identifiable Exports: Admin Controls, Privacy Risks and November 2026 GA Target

For IT, compliance and HR teams, this is a bigger shift than one more option on a download menu. Until now, the Copilot Dashboard export was built around anonymized IDs. An admin-controlled identifiable export changes the question from "how is the organization using Copilot?" to "how is this person using Copilot?" That raises governance issues worth settling before the feature arrives.

What the roadmap entry says​

According to the roadmap record, the feature is:

• Status: In development
• Product: Microsoft Viva
• Platform: Web
• Release rings: General Availability and Targeted Release
• Cloud instance: Worldwide (Standard Multi-Tenant)
• Estimated general availability: November 2026

Microsoft's roadmap page says its dates are estimates and that all information is subject to change. That warning applies here, because this item has already slipped once. Third-party roadmap trackers show that when the entry was first created in mid-June 2026, it listed Targeted Release, a release date of August CY2026, Web platform, Worldwide (Standard Multi-Tenant), created 2026-06-15. The DeltaPulse tracker also recorded an expected release of August 2026. The current November 2026 estimate is about a three-month delay. Admins should plan around it but not stake a governance deadline on it.

Section summary: Identifiable exports for the Copilot Dashboard are on the roadmap for November 2026. They're still in development and have already moved from an August target.

What changes: from anonymized IDs to named users​

The Copilot Dashboard already has a data export feature. Microsoft Learn says users can download user-level Microsoft Copilot metrics using the Copilot Dashboard's data export feature, either week-level metrics spanning the past six months, or day-level metrics spanning the past 28 days.

The important line is about identity. Personal identifiers are removed and replaced with anonymized IDs, unless your administrator has enabled identifiable export for you. And if your administrator has enabled identifiable export, the export also includes identifiable fields.

So roadmap item 562648 doesn't add a new export format. It adds an admin-controlled switch that puts identifiable fields into the export workflow that already exists. Microsoft hasn't published the exact names of those fields, so don't build Power BI models around column names you're guessing at.

Microsoft's broader identification guidance explains the purpose. It describes identification as the set of capabilities that moves an organization from anonymized metrics to known users, surfacing named employees when extra precision is needed and permitted. Microsoft's examples include:

• Finding champions and power users who already get value from Copilot
• Aiming training and change management at the specific teams and employees who need it most
• Linking Copilot usage to outcomes for named groups to judge the impact of a rollout

Preview status vs. the roadmap​

The documentation and the roadmap tell slightly different stories, and both need to be read in context. Microsoft Learn's identification article, last updated September 24, 2026, lists the features that support identification: Consumption Dashboard data export and Consumption Dashboard insights, Copilot Dashboard data export (Private Preview), and Agent Dashboard data export (Private Preview).

So identifiable Copilot Dashboard export currently exists only as a private preview, and the roadmap forecasts general availability in November. Most tenants won't see it until the broad rollout. A November estimate doesn't mean November delivery.

The base export article is also labeled preview. It warns that preview features may be incomplete, may change before broader release, and allow personal data processing under the "Previews" section of Microsoft's Data Protection Addendum.

Who controls identification​

Because identified outputs reveal named users, Microsoft classes identification as a sensitive capability. It's controlled by its own Viva Feature Access Management (VFAM) policy, separate from the general export setting.

The key rules from Microsoft Learn:

• Who can set the policy: Only a Microsoft 365 Global Administrator or an AI Administrator can create and manage identification access policies. Either role can do every step, in the admin center or in PowerShell.
• Admin center path: In the Microsoft 365 admin center, go to Settings > Viva > Feature access management. The same documentation also describes a no-code path through Settings > Org settings > Viva feature access: select Viva Insights, choose the identification feature, and add a policy.
• PowerShell: Scripted control uses the Exchange Online Management module's Add-VivaModuleFeaturePolicy cmdlet, which suits automated and repeatable rollouts.
• Shared policy store: Policies made in the admin center can be seen and managed in PowerShell, and the other way round.

Scoping limits​

Microsoft doesn't give a feature ID for Copilot Dashboard identifiable export in this guidance. Check the current VFAM feature list rather than reusing an ID from another Viva feature.

Don't confuse the two switches​

This is easy to get wrong. The general export feature and the identifiable export capability are controlled separately and have different defaults.

Microsoft Learn says the base export feature is on by default for eligible tenants and users. Global admins can turn it off or back on for the tenant or for specific groups through VFAM, and changes can take up to 24 hours to show up in the web app. One VFAM control covers both week-level and day-level exports.

The roadmap says the identifiable capability is something admins turn on. Microsoft hasn't spelled out its default state beyond that wording, but the separate VFAM identification policy means named-user exports shouldn't appear without an admin deciding to allow them.

Microsoft's other dashboards offer a useful comparison. The Agent Dashboard export, roadmap item 560538, is described as letting users export de-identified, row-level agent metrics and attributes from the Agent Dashboard. Message center coverage of MC1288531 notes that it's on by default but can be managed in VFAM. Microsoft's pattern looks consistent so far: de-identified exports are on by default, and identifiable outputs sit behind a separate, deliberate policy.

Section summary: Export access and identification are two separate VFAM decisions. Getting the first right doesn't mean you've handled the second.

Prerequisites and who can export​

Even with identification enabled, the existing export eligibility rules still apply, according to Microsoft Learn:

• Licensing: The tenant needs at least 50 Copilot or Viva Insights licenses assigned.
• Global dashboard access: Exporters need global access to the Copilot Dashboard. That covers senior leaders identified automatically from Entra ID data, users given global access by admins, delegates of users with global access, Viva Insights Analysts with global access, and Microsoft 365 Global Administrators.
• Managers with team-level views can't export.

Delegation needs attention. Microsoft's FAQ says delegates of users with global access automatically inherit data export access unless an admin policy turns it off. Map that inheritance chain before identification goes live. A chief of staff with a CSV of named employees' Copilot habits may be fine in your organization, or it may be a problem.

What's in the file​

The export spans a broad set of activity across Microsoft 365 apps:

• Copilot actions taken in Word, Excel, PowerPoint, Outlook, Teams, OneNote, Edge, the Microsoft Copilot app and Copilot Chat
• App-specific actions such as Excel formula creation, PowerPoint presentation creation, Outlook email drafting and Teams meeting summaries
• Copilot Chat usage by people without Copilot licenses, broken down by Edge, Teams, Outlook, Word, Excel, PowerPoint and the Copilot app
• Returning-user and usage-intensity metrics over consecutive 7- and 28-day windows

Things that trip up analysts:

• Day-level exports leave out five meeting metrics: meeting hours recapped by Copilot; meeting hours summarized by Copilot in Teams; meetings recapped by Copilot; total meeting hours summarized or recapped; and total meetings summarized or recapped.
• Copilot Chat (work) and Copilot Chat (web) were merged into one "Copilot Chat" metric. "Copilot Chat (legacy web)" still appears separately, and Microsoft expects its values to fall to zero over time.
• Zeros are normal. Licensed users show zero in the unlicensed Chat metrics, and unlicensed users show the reverse.
• Freshness differs. Week-level data can be up to six days old and includes completed weeks only. Day-level data can be up to three days old. Exports won't match dashboard totals when the dashboard includes a partial week.
• Downloaded files are static and don't update after export. Microsoft also says the exports can't be customized.
• HR attributes: The file includes Organization, taken from Entra ID or an uploaded org data file, and FunctionType (Job function), which is blank if the uploaded file doesn't include that field.
• Large files: Microsoft suggests Excel for smaller datasets and BI tools such as Power BI for big exports.

Analysis: useful, but think it through​

The benefit is real. Organization-wide averages don't tell a Copilot adoption lead which teams bought licenses and never used them, or who the internal power users are. Identifiable exports answer both questions directly, and that matters a lot while finance teams are looking hard at per-seat AI costs.

The risks are just as real. Once a named-user file leaves the Viva web app, VFAM can't protect it any more. It sits in Downloads folders, gets attached to emails, and ends up in SharePoint libraries. Add organization and job-function attributes, and the file becomes a fairly detailed record of individual work behavior. In regions with works councils or strict employee-monitoring rules, that may call for consultation before anyone flips the switch. Usage metrics also measure activity, not value. Fifty prompts a day doesn't mean someone is productive, and zero prompts doesn't mean they're failing. Are you ready to explain that to a manager holding a ranked spreadsheet?

The analysis above is based on general industry practice, not on Microsoft policy requirements.

Checklist for admins​

1. Audit global access: Review who has global Copilot Dashboard access, including automatically identified senior leaders and their delegates.
2. Decide on purpose: Write down why named-user data is needed: champion programs, targeted training or license reclamation.
3. Involve privacy, legal and HR early: Do this before GA, not after the first export lands in someone's inbox.
4. Pilot narrowly: Start with a group-scoped VFAM policy (up to 20 users/groups per policy) rather than a tenant-wide one.
5. Set handling rules: Decide where identifiable exports may be stored, who can see them and how long they're kept. Consider sensitivity labels and DLP for the resulting files.
6. Brief analysts: Make sure report users can tell whether a file is identifiable or anonymized, weekly or daily, and how fresh it is.
7. Watch the roadmap: Item 562648 has already moved from August to November, so check for message center posts that confirm the rollout.

The bottom line​

Identifiable export for the Copilot Dashboard turns Copilot adoption analytics from organization-wide trends into data about named people. Microsoft has kept it behind a dedicated VFAM identification policy, limited to Global and AI Administrators. That's a sensible design, but it only protects you if someone in your organization makes a deliberate decision about who gets access. The feature is still in private preview, still in development, and its estimated GA has already moved to November 2026, so admins have some time to prepare.