Why Your CFO Can't Explain the AI Bill: The Session Economics Gap
The CFO called again. The Microsoft 365 Copilot line item is 40% higher than last quarter. Nobody on the IT team can explain it. The licence count hasn't changed. The seat count is flat. But the invoice isn't.
The answer is not in the invoice. It never was.
The four bills hiding inside one AI invoice
Microsoft's AI cost structure in 2026 has four layers. Each arrives on a different invoice, in a different format, attributed to a different cost centre.
Layer one is the M365 Copilot licence — $30 per seat per month, flat and predictable. This is what finance sees and what IT manages. It is also the smallest part of the picture for any organisation that has deployed Copilot Studio agents.
Layer two is Copilot Studio credits. Every autonomous agent trigger — an agent that fires itself without a user initiating it — costs 25 credits at $0.01 each. Every Microsoft Graph query the agent makes costs 10 more credits on top of that. A single agent interaction involving Graph grounding and two automated actions costs 45 credits before the session is done. An agent running 200 autonomous triggers a month costs $50 in Studio credits alone, billed separately from the M365 licence, invisible in the seat count.
Layer three is Azure OpenAI token consumption for anything beyond what Studio credits cover. This arrives on the Azure subscription invoice, not the M365 invoice. Finance sees two line items and cannot connect them.
Layer four is Dataverse storage. Copilot Studio requires Dataverse. The default 15GB is usually sufficient, but high-volume agent deployments push past it. That cost appears on a fourth invoice.
The CFO is not confused because AI is complex. The CFO is confused because the same AI workload is generating four invoices, none of which tell the same story.
Why sessions explain what seats cannot
Enterprise AI costs grew 483% between 2024 and 2026. Seat counts did not grow 483%. The delta is the agentic multiplier.
A Copilot Studio autonomous agent running in the background is not a seat. It does not log in. It does not have a utilisation score. It runs when triggered, consumes credits per action, and generates cost that has no seat-level attribution in any Microsoft dashboard today.
The session is the unit that explains the bill. Not the seat.
An interactive Copilot chat session — a user asking a question in Teams — costs a fraction of a cent in practice. An autonomous Copilot Studio agent executing a multi-step workflow involving Graph queries, external API calls, and document generation can cost $0.43 per execution. Run that agent 200 times a month and the monthly cost is $86, attributed to no seat, appearing on no single dashboard.
What PromptKing's Agentic Cost Panel shows
The Agentic Cost Panel is the session-level view of your AI spend that the vendor invoice cannot provide.
It classifies every session by execution type — Interactive, Scheduled, Background, or Agentic — and shows cost per execution for each type. It surfaces the agents driving the most spend in a ranked leaderboard. It shows the 14-day trend so finance can see whether agentic spend is growing or stable.
It does not promise outcome attribution yet. Outcome measurement requires connecting execution cost to business result — a ticket resolved, a report generated, a workflow completed. That comes next. What the panel delivers today is execution economics: what ran, how much it cost, and which agents are responsible.
For the Monday morning CFO conversation, that is the answer that has been missing.
See your organization's AI spend data
PromptKing connects to your AI vendors and surfaces exactly this analysis — for your seats, your vendors, your budget.