Copilot credits: understand usage before estimating cost

Credits measure consumption

Copilot Credits measure usage rather than simply counting people or conversations. A single interaction can consume multiple capabilities. In Microsoft’s standard-harness rate table checked on 12 September 2026, a classic answer uses 1 credit, a generative answer 2 and an agent action 5. These are usage rates, not Australian dollar prices, and not a complete bill.

Know the billing model first

Microsoft also documents a separate GitHub Copilot harness experience. Its usage-based charges can include building, testing and evaluating, as well as running agents and workflows. Do not apply the standard rate table to that experience. Identify the product experience, model choices and billing plan before using any estimate, including one from an older tutorial.

An illustrative calculation, not a quote

Suppose a standard-harness pilot produces 200 billable generative answers and uses no other chargeable features. At 2 credits each, that component totals 400 credits. Tool use, grounding, reasoning, other services and actual traffic can change the total. Some authenticated employee scenarios have Microsoft 365 Copilot inclusions with conditions; Business Basic alone should not be treated as that licence, and public website visitors should not be assumed covered.

Budget from observed behaviour

Choose representative tasks and measure actual consumption during a limited pilot. Separate development usage from live traffic, then document expected volume and a higher-demand case. Have an administrator review environment allocations and the usage reports. Use the current licensing guide and your purchase terms for pricing, currency and tax. Recheck these sources before procurement: this article is a dated introduction, not a promise of fixed rates.

Microsoft sources and further reading

• Microsoft Learn: standard-harness billing rates and inclusions
• Microsoft Learn: GitHub Copilot harness usage-based billing
• Microsoft Learn: credit capacity management