The roadmap entry, updated on September 15, 2026, describes “a day level Copilot adoption Power BI report reflecting the most recent copilot activity & freshest insights.” It applies to Microsoft Viva and Microsoft 365 Copilot on the web, with both Preview and General Availability release phases listed for worldwide standard multi-tenant tenants. Microsoft’s wording is sparse, but its current Viva Insights documentation fills in an important boundary: fresh does not mean same-day.
Microsoft says its day-level Copilot metrics are refreshed daily and can include activity through three days before the export date. That is an improvement over week-level data, which can be up to six days old, and over the standard Copilot Dashboard’s previous-28-day view, which Microsoft says may also carry up to a six-day delay. For organizations watching whether a rollout is gaining traction after license assignments, training sessions, or a departmental deployment, cutting that delay roughly in half is useful. It is not real-time monitoring.
Roadmap 561325 closes a reporting gap, rather than adding a new Copilot control
Viva Insights already offered several ways to measure Microsoft 365 Copilot use: the Microsoft 365 admin center’s readiness and adoption reports, the Viva Insights Copilot Dashboard, analyst-led Advanced Reporting, and exportable dashboard metrics. Roadmap 561325 sits in the Advanced Reporting/Power BI corner of that stack, where organizations can investigate a deployment rather than simply view Microsoft’s fixed dashboard.
Microsoft’s Copilot Analytics documentation says Advanced Reporting can use preconfigured Power BI templates and customized queries across more than 100 Copilot metrics. The new roadmap item’s value is therefore not a new usage signal by itself; it is a Power BI reporting view intended to make recent, day-by-day adoption behavior easier to analyze.
That distinction is important for IT teams. The standard Copilot Dashboard is designed for leaders and managers reviewing readiness, adoption, impact, and sentiment over a rolling 28-day period. A daily snapshot is more suited to answering operational questions: whether a new cohort began using Copilot after receiving licenses, whether usage changed following internal training, or whether an application-specific enablement push moved activity during a particular week.
Microsoft has not published a fuller public product announcement for roadmap item 561325, a report name, screenshots, or a list of its individual visualizations. It also has not stated whether every existing Advanced Reporting customer will see the report automatically or whether an Insights Analyst must create it from a template. Admins should treat the roadmap’s “Launched” status as confirmation that the capability is released, but verify its appearance in their own Viva Insights analyst experience before promising a reporting cadence to leadership.
The “freshest insights” are still up to three days behind
The strongest qualification comes from Microsoft’s own export documentation. Day-level Copilot data covers the most recent 28 days and is refreshed daily, but Microsoft says it can be up to three days old. The company gives a simple example: an export run on October 31 containing data through October 28 is behaving as designed.
This means the new Power BI snapshot is useful for trend analysis, not for investigating events that happened this morning. A security or service-management team looking for an immediate answer to “who used Copilot after an outage?” or “did yesterday’s policy change stop usage?” will still need another telemetry source, and Microsoft has not positioned Viva Insights as an incident-response tool.
There is a second timing issue for new deployments. Microsoft says normal Copilot Analytics processing can take up to seven days after a Copilot license is assigned. Day-level data can be more current, but license assignments or removals made within the preceding two days may not yet be reflected. In other words, a daily report may show recent activity sooner than the legacy dashboard, while still being a poor instrument for judging the first 48 hours of a license rollout.
That makes the report most reliable after an initial settling period. Organizations should avoid declaring a pilot unsuccessful on day one, or interpreting a sudden apparent drop immediately after reclaiming and reallocating licenses. The reporting delay and license-processing window can create a false narrative if the date of the administrative change is not recorded beside the adoption chart.
Access is narrower than the word “Power BI” suggests
Microsoft’s documentation does not describe day-level Copilot usage data as a broadly available tenant export for every manager. Exporting detailed Copilot Dashboard metrics requires global access to the Copilot Dashboard. Microsoft lists senior leaders with qualifying automatic access, users granted global access by administrators, delegates of those users, Viva Insights Analysts with global access, and Microsoft 365 Global Administrators among the eligible groups.
Managers with team-level dashboard access cannot use the export capability. That limitation should matter to organizations trying to decentralize AI-adoption measurement: a business-unit manager may be able to see their team’s dashboard insights but still need an approved analyst or global-access user to generate the detailed day-level data.
The feature is enabled by default for eligible users, according to Microsoft, but global administrators can disable it for a tenant or specific groups through Viva Feature Access Management in the Microsoft 365 admin center. Changes can take up to 24 hours to appear in the Viva Insights web app.
For a governed deployment, that default deserves an explicit review. A day-level report is less delayed and therefore more revealing of short-term behavior, even though Microsoft says user-level exports remove personal identifiers by default. Administrators can enable identifiable fields, and access delegation can extend dashboard access to other staff. Teams should decide in advance whether their Copilot measurement program needs anonymized trend analysis, identifiable user-level records, or both—and make that choice through policy rather than leaving it to whoever first builds a Power BI report.
The daily view trades history for speed
Microsoft’s currently documented day-level export includes 28 days of data. Its week-level counterpart provides six months of data, refreshed weekly. The new Power BI snapshot is therefore likely to be most useful alongside—not instead of—the longer trend report.
A 28-day daily series can expose short-lived changes that a weekly rollup hides. For example, it can show whether adoption rose immediately after a training event and faded a week later, or whether weekday usage concentrates in a specific application. It cannot establish a durable adoption trajectory by itself. A large organization comparing one department’s September usage with its spring rollout will still need weekly history, a customized Advanced Reporting query, or a retained internal data model.
Microsoft also documents five Teams meeting-related measures that are excluded from the day-level export: 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. That omission means an analyst should not assume a daily report represents every Copilot action available in the longer weekly dataset.
The limitation is easy to miss because Microsoft describes the day-level option as containing the same metrics as the week-level export except for those meeting measures. For reporting owners, the safer approach is to label any daily Power BI page clearly as a 28-day, up-to-three-day-lag view, then pair it with a weekly historical page when reporting adoption and impact to executives.
What IT should check before using the report
The report will be most valuable when its numbers are connected to concrete rollout events, not treated as a scorecard on their own. Microsoft’s Copilot Dashboard counts usage across Microsoft 365 applications and applies privacy thresholds and filters that can produce different totals from the Microsoft 365 admin center’s usage reports or from analyst-built Power BI templates.
Before distributing the new snapshot, administrators should confirm four points:
- Ensure the intended analyst has the Viva Insights Analyst role and the necessary global partition or dashboard access, rather than assuming a Power BI author role alone is sufficient.
- Check whether Viva Feature Access Management permits the relevant users or groups to export and work with Copilot metrics.
- Document license-assignment dates, training dates, policy changes, and major service interruptions beside the report so a reporting delay is not mistaken for a behavioral change.
- Retain a weekly, longer-horizon view for executive reporting, because the daily dataset’s 28-day window is too short to establish sustained adoption.
Microsoft’s September launch changes the timing of Copilot adoption analysis, not the fundamental limits of that analysis. Viva Insights can show that users took Copilot actions; it cannot, on its own, prove that those actions improved a business process, reduced cycle time, or produced higher-quality work. The new day-level Power BI report gives IT teams a faster feedback loop after a Copilot rollout. The useful next step is to use that loop to test specific enablement decisions while keeping the three-day data lag, 28-day history limit, and access controls visible in every report.