A futuristic analytics dashboard displays cloud data, AI tools, charts, and a project timeline in a modern office.
Microsoft has put a new reporting interface for Copilot Studio usage data on its roadmap. It is called the PPAC Reporting API, and it is aimed at admins and finance teams who currently pull consumption data by hand or through workarounds. The roadmap entry (ID 579968) lists the feature as in development.

A futuristic analytics dashboard displays cloud data, AI tools, charts, and a project timeline in a modern office. What Microsoft says it is building​

The feature gives access to Copilot Credit usage from Copilot Studio through the Power Platform API, with insights by resource, environment, user and feature. The roadmap entry describes it as programmatic access to usage data from Microsoft's lakehouse. It says the data arrives as daily JSON, split by environment, user, agent and feature. Microsoft names three intended uses: dashboards, FinOps reporting and automated cost controls. It also says the API replaces older, unsupported methods of pulling consumption data.

The roadmap lists these milestones:

  • Status: In development.
  • Preview: November 2026.
  • General availability: January 2027.
  • Product and platform: Microsoft Copilot Studio, Web.
  • Cloud instance: Worldwide (Standard Multi-Tenant).

Microsoft's roadmap carries the usual caveat that dates and descriptions are estimates. I won't quote that line, because the roadmap's own wording says all information is subject to change. Treat the dates as planned milestones, not commitments.

Preview may already be open​

A Microsoft 365 admin news tracker, M365 Admin (handsontek.net), posted an item titled "Reporting API for Copilot Credits (preview)". It says the Reporting API for Copilot Credits in the Power Platform admin center is now in public preview. The same item describes the reports as read-only, usable alongside Power Platform API credit allocations to monitor and optimize resources and environments that consume Copilot Credits.

That matches the roadmap's description closely. It is a secondary source, though, so I can't confirm it is the same feature as roadmap ID 579968. I also haven't confirmed that it is live in your tenant. Check the Power Platform admin center message center and Microsoft Learn before you plan around it.

Why admins care​

Until now, getting Copilot Studio consumption data out of the admin center has been awkward. Several sources describe the situation:

  • Manual downloads: Reports could only be downloaded manually and mostly held the last 30 days of data, with Copilot Studio as the exception.
  • Community automation: Community author powertricks.io built a Power Automate-based extractor for this. Its author notes that it relies on a non-supported API. That is likely the kind of workaround the roadmap's "unsupported methods" wording refers to, though Microsoft does not name any method.
  • Breakage: The same author reports that the Copilot Studio message report API changed in Q1 2026 and temporarily broke the automation.
  • Partial supported coverage: A Microsoft-hosted GitHub project documents a Power Platform licensing API that returns tenant and per-agent consumption at a daily grain the CSV export lacks. The same documentation says PPAC is a CSV download surface for this data.

A supported, documented API means reporting pipelines no longer depend on an endpoint that can disappear without notice. The earlier breakage shows why that matters.

What the roadmap does not say​

The roadmap entry leaves many practical questions open:

  • Authentication and permissions: No roles, scopes or licensing prerequisites are given.
  • Schema: The roadmap doesn't say what "by user" means (end user, maker or another identity). It doesn't define "feature" either.
  • Data behavior: Nothing is said about when each day's data lands, whether late corrections are applied, or whether history is backfilled. Retention, paging and throttling limits are also unstated.
  • Billing reconciliation: It doesn't say whether the data will match invoices.
  • Cost controls: "Automated cost controls" is a use case Microsoft cites. The roadmap doesn't say the API will itself cap spending or stop agents. Any enforcement would be something your organization builds on top of the data.
  • Retirement of older methods: No older method is named, and no retirement date is given.
  • Sovereign clouds: Only Worldwide (Standard Multi-Tenant) is listed, so don't assume the API reaches sovereign or other specialized clouds.

Practical steps​

  1. Inventory current reporting. List every manual export, flow or script that pulls Copilot Studio consumption data, and note which ones depend on unsupported endpoints.
  2. Write your requirements. Decide which fields you need, such as environment, agent, user and feature, and what refresh cadence you need. Compare the documentation against that list when it appears.
  3. Check access. Once Microsoft documents the API, confirm which admin roles and tenant settings it requires.
  4. Pilot before migrating. If preview is available to you, run it in parallel with existing reports and compare totals before retiring anything.
  5. Hold off on automated enforcement. Don't wire cost-control automation to preview data until the schema and refresh behavior are documented and tested.

Bottom line​

This is a modest but useful item. It targets a real pain point, which is getting Copilot Studio consumption data out of the admin center on a schedule through a supported route. The roadmap entry is thin on technical detail, so the real test will be the documentation: schema, permissions and data freshness. Until that is published and you have access, use this for planning, not as a production integration guide.

 

References

  1. Microsoft Copilot Studio: PPAC Reporting API Microsoft 365 Roadmap 2026-11-18T18:32:08.027424Z
  2. Use the Power Platform API for Studio data on every path by Keithland89 · Pull Request #33 · microsoft/ConsumptionCentral-for-Microsoft-Copilot · GitHub github.com
  3. ConsumptionCentral-for-Microsoft-Copilot/docs/DATA-SOURCES.md at main · microsoft/ConsumptionCentral-for-Microsoft-Copilot · GitHub github.com