Microsoft Viva Copilot Analytics is adding team-level spend visibility for Cowork and WorkIQ, and that matters because these services sit on usage-based billing. If you turn on agent-like AI without a cost view below the tenant level, you are basically waiting for a finance argument.
The roadmap item is straightforward: Viva Insights will show Copilot credit usage for Cowork and the Work IQ API at group or team level, both in a dashboard and in Advanced Insights. Access is scoped: managers need at least 5 direct reports, and Insights Analysts plus Global Administrators can also see the data. The dashboard is enabled by default. That last part is good, because cost reporting that requires extra setup is usually discovered after the first surprise bill, not before.
What is actually being added?
This is not a new billing model. It is better reporting for an existing one.
Microsoft’s official billing docs say usage-based billing currently applies to Copilot Cowork and Work IQ API. The same docs also point admins to the Microsoft 365 admin center Cost Management dashboard for budgets, alerts, limits, and hard caps. So this Viva addition is really a missing middle layer: tenant-level billing already exists, but now managers and analysts get a team view in Viva.
That is useful because central IT can see total spend, but team leads need to see whether one department is using AI heavily while another is barely touching it. Without that, showback and chargeback are mostly fiction.
For organizations building broader Microsoft Copilot and AI agents, this is one of the first signals that Microsoft knows FinOps for AI cannot stay trapped in the admin center.
How much does this cost?
What we can verify officially is the meter, not your eventual total.
For Microsoft 365 Copilot pay-as-you-go services, Microsoft documents the Copilot Studio meter at $0.01 per message for billed agent or custom Copilot usage. Microsoft also documents that billed amounts are updated daily, sometimes more frequently, and that some usage can take up to 24 hours to appear in Cost Management.
Here is the part I would not gloss over: once usage-based AI gets normalized inside teams, the person approving the tenant policy is often not the person creating day-to-day demand. That gap is where overspend happens. Dashboards help, but only if you also put budgets and ownership behind them.
A simple view of the pieces looks like this:
| Area | What Microsoft says |
|---|---|
| Billing model | Usage-based billing uses Copilot Credits |
| Services in scope here | Copilot Cowork and Work IQ API |
| Meter example | Copilot Studio meter: $0.01 per message |
| Cost controls | Budgets, alerts, limits, hard caps in Microsoft 365 admin center |
| Reporting access | Managers with 5 plus directs, Insights Analysts, Global Administrators |
What I’d watch before trusting this
The best part of this update is that it makes AI spend more visible to the people creating it. The weak part is access and governance are still split across multiple portals and roles.
Microsoft’s own docs recommend least-privilege roles, and they are right. An agent should not get a blank check to your tenant, and a manager does not need global visibility just to see team usage. But the roadmap item also says leader access to tenant-wide data is out of scope. For most orgs, that is fine. For larger federated environments, it means you may still need analysts to bridge the gap between local team visibility and enterprise allocation.
I would also verify whether your reporting story lines up across Viva, Cost Management, and any internal AI and automation audit process. If different stakeholders are looking at different numbers with different refresh times, you will spend more time debating the bill than governing it.
If you are already automating policy and spend controls with PowerShell, Azure Functions, Logic Apps, or ServiceNow, this update is worth watching. Not because it changes the fundamentals, but because it finally gives team-level accountability a place to land.
My take: this is a good and overdue addition, not a huge product moment. AI cost visibility should have been there from day one for metered experiences. Still, enabled-by-default team reporting is the right default, and if Microsoft expands this model consistently to more metered Copilot services, it becomes genuinely useful.
