How do makers see agent credit cost before Finance sees the invoice?

You’re right to want the meter where the maker can see it — not only where the invoice lands. Silent test burn is still burn.

Here’s what’s going on. Learn’s Understand estimated credit usage (agents/workflows on the GitHub Copilot harness) puts near-real-time estimated Copilot Credits into Preview and Evaluate, with Monitor updating a few times a day as the authoritative billed figure once processing catches up. Estimates use runtime signals (models, tools/actions, harness/orchestration); the UI marks estimates so nobody mistakes them for the final bill. Roadmap 571194 (status In development, GA timing September CY2026 — verify for your cloud) is the same story for Preview Chat and History: makers see consumption while they test, iterate, and review conversations. Related roadmap items cover cost visibility in Evaluations and the Monitor tab. That is the maker lens. The admin lens is still Power Platform admin center: environment allocation, prepaid vs pay-as-you-go, Manage Agents monthly limits and hard stops, and downloadable consumption reporting — Learn’s governance guidance is explicit that consumption starts at design time, before publish, and that you should govern the environment, not just the agent. Public maker threads (r/copilotstudio and similar) keep asking for spend-per-agent and org-wide tracking; the product answer is layered: Preview/Evaluate/Monitor for the builder, PPAC (and M365 Cost Management for other metered Copilot experiences) for the estate. Note the harness caveat on Learn: GitHub Copilot harness usage is not “free because the user has a Microsoft 365 Copilot licence.”

Steady before scale puts Pane 06 Cost & Value in front of endless Preview chat. Schofield’s First Law (historically attributed): don’t put the organisation on a meter you can’t read back out — estimates in Preview plus Monitor plus PPAC reports are how you get the data out.

Options that actually work:

1. Limits first, visibility always. Classify environments (exploration / test / funded production), allocate prepaid or attach PAYG with an owner, set organisation-defined agent monthly limits on exploration agents, and teach makers to watch Preview estimates. Best Steady default.
2. Pilot maker visibility on one harness environment: require a screenshot or note of estimated credits in the publish checklist once 571194 / Learn UI is present. Good Wave 0 habit.
3. Wait for perfect org-wide dashboards before applying any limit. You’ll learn the cost from the invoice.
4. Assume Preview estimates replace PPAC reporting and spending policies. They don’t — estimates are planning; Monitor and admin reports are the bill story; M365 Cost Management covers a different metered surface.

12 Panes action / comms: Tell makers: Watch the credit estimate in Preview — testing counts. Tell FinOps: Environment allocation + agent hard stops; don’t rely on goodwill. PPAC admins: Turn off casual draw from tenant pool on exploration environments; inventory harness agents on a cadence. Leadership: Design-time cost is real cost after September 2026 developer/trial billing shifts — verify for your tenant.

Benefits / risks: Makers course-correct before Finance does; estimates ≠ final bill (reporting lag); harness-specific docs may not cover every agent type; Azure budgets alert but don’t stop Studio usage — agent hard stops do. Verify Learn, Message Centre, and which harness each agent uses.

I’d suggest this week: classify your Copilot Studio environments, put a monthly limit on exploration agents, point makers at Preview credit estimates (or Monitor once published), and put PPAC consumption on the FinOps weekly next to any M365 Cost Management policies. You’ll get Steady Cost without waiting for the surprise invoice to teach the lesson.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer