Back to Cheat Sheets
Copilot Strategy · Copilot Studio commercial model

Copilot Licensing and Credits

Use this when explaining how Copilot Studio agent capabilities and consumption choices relate to Microsoft 365 Copilot, credits, prepaid capacity, and Azure billing.

Copilot Licensing and Credits

Text version

Everything on the sheet above as text, so you can search it, copy from it or read it with a screen reader.

Copilot agent licensing: creation access and Copilot Credits explained.

Common misconception

"If 5,000 employees use a Copilot Studio agent, the organisation needs 5,000 Copilot licences."

Not necessarily. Published agent users do not need a special licence. Consumption is billed through Copilot Credits.

1. Maker access: who builds and manages the agent

  • Makers need supported creation access in Copilot Studio to design agents, configure tools and manage solutions.
  • A Microsoft 365 Copilot licence lets you use Copilot Studio to extend Microsoft 365 Copilot with agents.
  • Other maker access options include a Copilot Studio user licence, the Copilot Studio authors role, or trial access.

2. Agent consumption: how end-user interactions are billed

  • Users chat with the published agent.
  • Users of your agents do not need a special licence.
  • Copilot Credits are the common currency across Copilot Studio capabilities.
  • Consumption can be covered by prepaid Copilot Credit capacity or pay-as-you-go via Azure.

A simple example

  1. 10 makers build an HR agent.
  2. 5,000 employees use it.
  3. You do not need 5,000 creator licences.
  4. You need maker access plus Copilot Credits.

Key takeaways

  • Maker access is for builders.
  • Published agent users need access, not per-user creator licensing.
  • Agent usage is billed in Copilot Credits.
  • Plan capacity and billing early.

Build once, scale smart: that is the licensing model many teams miss. To estimate the credits an agent will use, try the Copilot Studio Credit Calculator.