I love Copilot Studio. I genuinely do. It's a powerful platform for building enterprise AI agents. But somewhere in Redmond, a pricing engineer woke up one morning and said, "What if we charged for thinking?" - and here we are.
Credits: The Currency of AI Cognition
Copilot Studio uses Copilot Credits as its billing unit. Every action your agent performs - returning a scripted response, generating an AI answer, calling an external system, running a workflow - consumes credits. Your agent doesn't just cost money to build. It costs money to exist and have opinions.
You can buy credits three ways:
| Model | Price | Per Credit |
|---|---|---|
| Prepaid pack | 25,000 credits for $200/month | ~$0.008 |
| Pay-as-you-go | No commitment | $0.01 |
| Pre-purchase plan | Annual commitment, volume discounts | ~$0.008–0.0095 |
Straightforward so far. Now let's see what happens when your agent actually does something.
"How Many Do We Have in Stock?"
A simple question. A human could check SAP in 30 seconds. Let's see what the agent needs:
- Invoke a Power Automate flow to query SAP → 5 credits
- Run the flow actions (authenticate, call API, parse response) → ~0.13 credits per action
- Generate an answer using AI → 2 credits
Total: ~7 credits to tell you there are 847 units of Product X in the warehouse.
At pay-as-you-go rates, that's $0.07 per inventory check. At 100 queries a day, you're looking at $7/day, $210/month - roughly the cost of the prepaid pack, which gives you 25,000 credits.
Not terrible. But we're just getting started.
"What Does This SharePoint Document Say?"
Your agent reads a file from SharePoint and summarizes it. Simple, right?
- Tenant graph grounding (accessing Microsoft Graph to find the document) → 10 credits
- Generative answer → 2 credits
Total: 12 credits to read a document that's sitting in your own tenant. Your own files. That you already pay to store. On infrastructure you already license.
However - and this is where it gets interesting - if the user has a Microsoft 365 Copilot licence and asks through Teams, these 12 credits cost exactly zero. The M365 Copilot subscription covers it.
So the cost of reading a SharePoint document ranges from $0.12 to free, depending on which licence the person asking happens to hold. Same question, same document, same agent, different price. Enterprise pricing is a beautiful thing.
The Upload Workaround
What if the user just uploads the file directly instead of reading it from SharePoint?
No graph grounding charge (the agent doesn't need Microsoft Graph), but you still pay:
- Agent action → 5 credits
- AI Tool processing (standard band) → ~1.5 credits
- Generative answer → 2 credits
Total: ~8.5 credits. You saved 3.5 credits by dragging and dropping instead of pointing at SharePoint. Somewhere, an optimization consultant just earned their fee.
The Licence Puzzle
Here's where my favorite part comes in:
- Users with M365 Copilot licences talking to agents inside Teams/SharePoint → credits are zero-rated for generative answers, graph grounding, and actions within M365
- Users without M365 Copilot licences → every interaction draws from your credit pool
- Guest users → not supported at all
So your agent's operating cost depends not on what it does, but on who's asking and where they're standing when they ask. The same "summarize this document" request costs 0 credits from Teams with an M365 licence, 12 credits from Teams without one, and is impossible if you're a guest. Schrödinger's pricing.
The Real Math
Let's say you have an agent handling 500 queries per day across your organization. Mix of SAP lookups (~7 credits each), document reads (~12 credits each), and simple Q&A (~2 credits each):
| Query Type | Daily Volume | Credits/Query | Daily Credits |
|---|---|---|---|
| SAP lookups | 150 | 7 | 1,050 |
| Document reads | 200 | 12 | 2,400 |
| Simple Q&A | 150 | 2 | 300 |
| Total | 500 | 3,750 |
That's 3,750 credits per day, or ~112,500 per month. You'd need about 4.5 prepaid packs ($900/month) or $1,125/month on pay-as-you-go.
Now subtract the interactions from M365 Copilot licensed users (zero-rated in Teams). If 60% of your users have the licence, your actual credit consumption drops significantly. But those M365 Copilot licences cost $30/user/month, so... you're paying somewhere regardless.
The Elephant in the Room: Why Not CrewAI?
At some point during the credit arithmetic, a voice in the back of your head whispers: "What if I just... didn't pay per thought?"
CrewAI is the open-source multi-agent framework by João Moura that lets you orchestrate AI agents with tool use, delegation, and memory - without a per-credit billing model. You bring your own LLM, you define your agents, and you run them wherever you want. There's a free tier. There's a managed enterprise tier. And at no point does anyone charge you 5 credits for the privilege of calling an API.
I've used CrewAI in several projects, and every time I do, I can practically see João's signature smile radiating through the documentation, gently saying "I told you so." The man built a framework that makes multi-agent orchestration feel natural, and the free tier is generous enough that you can ship real work before spending a cent.
So why use Copilot Studio at all? Because if you're already deep in Azure, M365, and Power Platform, the integration is genuinely unmatched. Your agents can access SharePoint, Teams, Dynamics, and SAP through pre-built connectors with enterprise-grade auth, compliance, and governance baked in. Building that plumbing yourself with CrewAI is absolutely possible - but it's weeks of work that Copilot Studio handles out of the box.
The trade-off is classic: convenience and integration vs. flexibility and cost control. Copilot Studio is the managed, vendor-locked, batteries-included path. CrewAI is the open, bring-your-own-everything path. Both are legitimate choices depending on where your organization sits.
Just know that every time you pay 7 credits to check SAP inventory, somewhere João is smiling.
Should You Care?
Honestly? For most enterprise use cases, these costs are reasonable. Seven cents to query SAP is far cheaper than the 15 minutes an employee spends navigating the SAP GUI. The ROI is there.
The complexity isn't in the price - it's in predicting the price. Your monthly bill depends on which users have which licences, which channels they use, whether they upload files or read from SharePoint, how many flow actions each query triggers, and whether Mercury is in retrograde.
My advice: start with pay-as-you-go, measure actual consumption for a month, then switch to prepaid packs when you understand your baseline. And maybe keep a spreadsheet to track it all. Just don't ask your Copilot agent to maintain that spreadsheet - it'll cost you 7 credits every time it updates.