MPUG Editorial · August 21, 2026 · ~5 min read · Category: AI & Copilot

Tracking Copilot credit usage has been one of the more awkward gaps in enterprise AI adoption: teams were told to use the tools, but nobody could easily say what those tools cost. Microsoft’s August 11, 2026 Microsoft 365 Copilot release addresses this with a new Consumption Dashboard in Viva Insights that tracks Copilot credit usage across AI services and provides budget information to managers, analysts, and administrators. For anyone who has been asked “what’s our AI spend on this project?” and had to guess, this is the beginning of a real answer.

What the Consumption Dashboard actually does

According to Microsoft’s release notes, the dashboard shows Copilot credit consumption for Cowork and WorkIQ API services. It is enabled by default, but it requires usage-based billing to be set up via Cost Management in the Microsoft 365 admin center – so it is not entirely zero-configuration.

Access is deliberately scoped. Three groups can see it:

• Managers with at least five direct reports
• Insights analysts
• Global administrators

Tenant-wide leader access is explicitly not included in this release. That is a meaningful design choice: Microsoft is limiting who can see consumption data rather than making it broadly visible, which reduces the risk of team-level usage metrics being read as individual performance signals.

The release also adds a Cost Management query template for Insights analysts and Global administrators in Advanced Insights, for organizations that want to go beyond the dashboard view and run their own analysis. The change is tracked under Microsoft 365 roadmap ID 566302.

Why AI cost visibility became a project management problem

For the first wave of Copilot adoption, licensing was simple: a per-seat cost, provisioned by IT, absorbed into an overhead line. Credit-based consumption changes the shape of that. When cost scales with usage rather than headcount, spend becomes variable – and variable cost attached to project activity is, definitionally, something a project manager has to plan for.

This is the same transition IT organizations went through with cloud infrastructure. Fixed server budgets became elastic cloud bills, and an entire discipline (FinOps) emerged because nobody could forecast the new model with the old tools. AI credits are following the same curve, just faster.

The practical consequence is that “we’ll use AI to accelerate this” is no longer a free assumption in a project plan. If an agent is running recurring analysis on your project data, that has a cost, and estimating it is now part of the job.

Why it matters for project managers

Three concrete reasons this belongs on your radar.

Sponsors will start asking. Once finance can see AI consumption by team, the question “what is this project’s AI spend?” becomes answerable – which means it becomes askable. Being ahead of that question is considerably more comfortable than being behind it.

Business cases need real numbers. If you are justifying AI-assisted delivery, the benefit side of the case has always been easy to assert and hard to prove. Consumption data at least makes the cost side concrete, which turns a hand-wave into an actual comparison. MPUG’s on-demand class on governing AI-assisted delivery in the enterprise covers the surrounding governance questions in depth.

The access model matters for how you use it. Because visibility is scoped to managers with five or more direct reports, analysts, and admins, many project managers will not have direct access. If you need consumption data for a business case, expect to request it through a PMO analyst or admin rather than pulling it yourself. Plan the request into your reporting cycle instead of treating it as self-service.

There is also a governance dimension. Consumption data is workforce data. Even with Microsoft’s scoping, organizations should be explicit about whether this information is used for budgeting or for evaluating individuals — those are very different uses, and conflating them damages trust in the tooling.

What to do next

• Confirm whether it is switched on. The dashboard is enabled by default but depends on usage-based billing being configured in Cost Management. Ask your M365 admin whether that setup exists in your tenant.
• Find out who your data owner is. Identify the Insights analyst or Global administrator who can pull consumption figures, before you need them for a business case.
• Add an AI cost line to your project budget template. Even a placeholder forces the conversation during planning rather than at closeout.
• Set an internal rule on how the data is used. Agree in writing that consumption figures inform budgets, not performance reviews.
• Build the governance skills. MPUG’s master class library covers AI governance, business case development, and cost management, and members can claim PDUs for them via the PDU tracker. Business Acumen is one of the three PMI Talent Triangle areas you need PDUs in — AI cost management fits it neatly.
• Watch the release notes yourself. The Copilot release cadence is roughly biweekly; scanning Microsoft’s release notes is a low-cost habit, as is tracking MPUG’s upcoming live events for practitioner takes on what changed.

Frequently asked questions

Who can see the Copilot Consumption Dashboard? Access is scoped to managers with at least five direct reports, Insights analysts, and Global administrators. Tenant-wide leader access is not included in this release. Most individual contributors and many project managers will not have direct access.

What services does the Consumption Dashboard cover? In this release, it shows Copilot credit consumption for Cowork and WorkIQ API services. It requires usage-based billing to be configured through Cost Management in the Microsoft 365 admin center.

Do I need a separate licence for the Consumption Dashboard? The dashboard is described as enabled by default within Viva Insights, with the dependency being usage-based billing setup rather than a distinct add-on. Because licensing and tenant prerequisites vary, confirm your specific entitlements with your Microsoft 365 administrator or account team before planning around it.

The bottom line

The Consumption Dashboard is a small feature with an outsized signal attached to it: AI is becoming a metered, budgeted, reported cost rather than an experiment on someone else’s ledger. Project managers who start treating AI consumption as a planned line item — estimated, tracked, and defensible — will handle the coming sponsor questions considerably better than those who wait for the first surprise invoice to force the issue.

Source: Release notes for Microsoft 365 Copilot (August 11, 2026 update), Microsoft Learn. Rollout timing, licensing prerequisites, and tenant-specific availability change frequently — verify details for your own tenant against the primary Microsoft documentation and with your M365 administrator before acting on them.