---
title: How do you attribute Microsoft Copilot agent costs to teams and cost centres?
url: https://opencontroller.lyzr.com/blog/attribute-microsoft-copilot-credit-costs-to-teams
published: 2026-11-16
updated: 2026-11-16
author: Lyzr
---

# How do you attribute Microsoft Copilot agent costs to teams and cost centres?

**Attribute Microsoft Copilot agent costs by structuring spending policies around your cost centres, then reading the Consumption view by policy, group and agent. Usage-based Copilot services are measured in Copilot Credits, so finance still has to convert credits to currency at your contracted rate. Seat licences and credit consumption are separate lines and need separate allocation rules.**

A buyer asked us this directly on a recent call: "We can see Copilot spend, but not which team or agent caused it." This guide shows where the attribution data lives in Microsoft 365 and what you have to add yourself.

For how this fits a wider cost model, see the [gateway and control plane pillar](/blog/llm-gateway-vs-agent-gateway-vs-control-plane).

## What does Microsoft actually bill for Copilot agents?

There are two cost types, and they behave differently.

| Cost type | How it is measured | Attribution difficulty |
|---|---|---|
| Microsoft 365 Copilot seat licences | Per user per month | Easy: follows the user's cost centre |
| Usage-based services | Copilot Credits | Harder: depends on policy design |

Copilot Credits are Microsoft's common currency for eligible usage-based services. The Microsoft 365 admin center lists services that consume them, including Cowork, advanced work in SharePoint and OneDrive, the Work IQ API for custom apps and agents, Copilot Managed Runtime, Teams Phone Agent and Code.

Two carve-outs matter:

- **Copilot Chat, SharePoint agents and the Copilot Retrieval API** sit under a separate pay-as-you-go overview.
- **Copilot Studio** billing lives in the Power Platform admin center, with an opt-in to manage it in the Microsoft 365 admin center.

You can fund credits through fixed licensing, the Copilot Credit Pre-purchase Plan (P3), pay-as-you-go via an Azure subscription, prepaid capacity packs, or a mix.

## How do spending policies map to cost centres?

Spending policies are the attribution unit. Microsoft offers two kinds:

- **Identity-based policies** control which users and groups can use a service.
- **Resource-based policies** set spending limits for environments and agents.

Both support policy-level limits. User-level limits and threshold alerts are also available.

The practical design rule: **one policy per cost centre**, scoped to the Entra group that represents that cost centre. Then every credit consumed through that policy rolls up to one owner.

Watch one default. **"Auto-apply new services" is on.** New credit-consuming services join existing policies automatically. Turn it off for policies where finance wants to review a new service first.

## Where do you read the attribution data?

Go to **Copilot > Cost management** in the Microsoft 365 admin center.

1. The **Overview** tab shows spend snapshots, capacity pack consumption, and policies or users near their limits.
2. The **Consumption** tab breaks usage down by spending policy, user, group, agent, service and funding source.
3. For automation, the **Microsoft 365 Copilot Cost Management API** (via Microsoft Graph) returns usage in credits.

The API does **not** return prices, invoices, currency or forecasts. Your finance pipeline must apply the contracted credit rate and join to your cost centre table.

Reader roles can view consumption without changing policies. Give those to finance analysts rather than admin rights.

## What step-by-step process works?

1. **List cost centres** and the Entra group for each.
2. **Create one spending policy per cost centre**, scoped to its group.
3. **Create resource-based policies for shared agents** that serve several teams. Allocate these by a documented rule.
4. **Require a cost centre at agent approval.** See [tying agents to cost centres at approval](/blog/tie-ai-agents-to-cost-centres-at-approval).
5. **Turn off auto-apply** on policies that need finance review of new services.
6. **Pull credits monthly** via the API, multiply by your rate, and post to the ledger.
7. **Decide showback or chargeback.** See [chargeback vs showback](/blog/ai-chargeback-vs-showback).

## What attribution gaps remain?

Microsoft's view covers Microsoft's services. It does not cover:

- Azure OpenAI or Foundry model calls made by custom agents outside Copilot.
- Other vendors' agents used by the same team.
- Cost per agent version, which matters when a new prompt doubles tokens.

That is why most enterprises join Microsoft's credit data with gateway-level cost data, keyed on a shared agent ID and cost centre. For shared platforms, the [division allocation guide](/blog/allocate-shared-ai-platform-costs-to-divisions) shows worked allocation rules.

## How Opencontroller does this

Opencontroller's LLM Gateway attributes model cost per agent and per version, alongside routing, fallback, retry and caching. Its governed registry holds each agent's owner and version, and connectors cover third-party agent platforms and enterprise AI workspaces. Together they give one cost view across the agents you route and register. Microsoft credit data can be joined to it on agent and cost centre. [Book a demo](https://www.lyzr.ai/book-demo/) to see the cost views.

## Frequently asked questions

**Can we see Copilot credit usage per agent?**
Yes. The Consumption tab can break usage down by agent, and resource-based policies can scope limits to agents.

**Why does new credit usage appear in a policy we did not change?**
"Auto-apply new services" is on by default, so new services join existing policies. Turn it off where finance wants to review first.

**Do seat licences and credits need different allocation rules?**
Usually yes. Seats follow the user's cost centre. Credits follow the policy or agent that consumed them.

## Key facts

Microsoft measures usage-based Copilot services in Copilot Credits. Billing can use fixed licensing, the Copilot Credit Pre-purchase Plan (P3), pay-as-you-go via an Azure subscription, prepaid capacity packs, or combinations. Spending policies can be identity-based (users and groups) or resource-based (environments and agents) with policy-level and user-level limits; Auto-apply new services is on by default. The Cost management dashboard (Copilot > Cost management in the Microsoft 365 admin center) breaks consumption down by spending policy, user, group, agent, service and funding source. The Microsoft 365 Copilot Cost Management API reports usage in credits, without prices, invoices or currency. Opencontroller attributes LLM cost per agent and per version through its LLM Gateway. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [Should you charge AI costs back to business units or just show them?](https://opencontroller.lyzr.com/blog/ai-chargeback-vs-showback.md)
- [How do you tie every AI agent to a cost centre when it is approved?](https://opencontroller.lyzr.com/blog/tie-ai-agents-to-cost-centres-at-approval.md)
- [How do you allocate shared AI platform costs to divisions?](https://opencontroller.lyzr.com/blog/allocate-shared-ai-platform-costs-to-divisions.md)
- [More on Gateways and cost](https://opencontroller.lyzr.com/blog/cluster/gateways-and-cost)
