Can MSPs Actually Bill for Copilot Cowork?

image

I’ve been mulling over a question that doesn’t get asked enough, and I think it deserves a hard look: when Copilot Cowork lands with pay-as-you-go billing, do small and midsize MSPs actually have the skills to handle it? Not the product. The billing. Because from where I sit, that’s the part most of us are least prepared for.

For years, the SMB MSP model has run on something beautifully predictable: per-seat licensing. A client has thirty users, you sell thirty licences, you mark them up, and everyone knows what next month’s invoice looks like before it arrives. That predictability is the whole foundation. It’s what lets you quote a managed services agreement with a straight face. Consumption billing pulls that foundation out from under you.

We’ve Never Had to Read This Kind of Meter

PAYG is a different animal. Usage goes up and down. Costs follow. Suddenly you’re not selling a fixed thing, you’re selling access to a meter that ticks based on what people actually do inside Copilot. And here’s the uncomfortable truth — most of us have never had to read a meter like this before. We don’t have the muscle for it.

Think about the questions a client will ask the moment their first variable bill arrives. Why was it higher this month? Which users drove that? Was it worth it? If your answer is a shrug and a forwarded Microsoft invoice, you’ve got a problem. You need to pull the usage data, make sense of it, and explain it in plain English. That’s not a skill most SMB MSPs have built, because we’ve never needed it.

Configuring It Is the Easy Part

Turning Copilot Cowork on through the admin centre isn’t the hard bit. Microsoft will make that straightforward enough. The hard bit is everything that wraps around it — setting spending limits so a client doesn’t get a nasty surprise, deciding who gets access, and putting guardrails in place before usage runs away from you.

Then comes reporting, which is where I think the real gap shows. Can you stand in front of a client at the monthly meeting and show them, clearly, what they consumed and what they got for it? You’ll be living in the Microsoft 365 admin centre and the usage reports, and you may well end up pulling that data into Excel — perhaps asking Copilot itself to summarise the month’s consumption into something a business owner can read in thirty seconds. If you can’t produce that story, the client will assume the worst.

This Is a Discipline We Have to Learn

What worries me isn’t the technology. It’s that consumption billing is a genuine discipline, and it’s one the SMB MSP world has largely skipped. The cloud providers have been doing variable billing for years. Most of us serving small business have not. We’ve been comfortable in fixed-price land, and Cowork is going to ask us to grow up fast.

So I’d put the question back to you honestly. Could your business take on a client with Copilot Cowork tomorrow, configure it sensibly, manage the spend, and report on it with confidence? If there’s hesitation in that answer, you’re not behind — you’re normal. But the MSPs who close that gap early, who learn to read the meter and tell the story, are the ones who’ll own this conversation. The rest will be forwarding invoices and hoping nobody asks why.

Need to Know podcast–Episode 367

This episode ultimately reflects on how organisations must adapt to an environment where solutions are no longer neatly balanced between simplicity and capability. Instead, businesses need to reassess priorities, stay informed, and make deliberate choices about which innovations deliver real value. For SMBs, the challenge is not just keeping up—but identifying what’s truly “good enough” in an increasingly complex cloud-first world.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-367-goldilocks-gone/

Subscribe via iTunes at:

https://itunes.apple.com/au/podcast/ciaops-need-to-know-podcasts/id406891445?mt=2

or Spotify:

https://open.spotify.com/show/7ejj00cOuw8977GnnE2lPb

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show

Resources

CIAOPS Need to Know podcast – CIAOPS – Need to Know podcasts | CIAOPS

X – https://www.twitter.com/directorcia

director@ciaops.com

CIAOPS Blog

Join my Teams Shared Channel – CIAOPS

CIAOPS Merch store – CIAOPS

Become a CIAOPS Patron

CIAOPS AI Dojo

CIAOPS weekly news update – CIA Brief – CIAOPS

CIAOPS Labs – The Special Activities Division of the CIAOPS

Support CIAOPS

Get your M365 questions answered via email

Join my email list

A special thanks to the CIAOPS Patron community for making this podcast possible. You can find the benefits of a subscription to the community and become a member at https://www.ciaopspatron.com

AutoJack: How a single page can RCE the host running your AI agent

Azure Sets a New Performance Record for LLM Training Benchmark at Extreme Scale

Forrester names Microsoft a Leader in the 2026 Extended Detection and Response Platforms Wave report

Copilot Cowork is now generally available

Microsoft Defender email security benchmarking: Key insights from one year of data

Stay productive in new Outlook for Windows with these 5 features

What’s new in Power Platform: June 2026 feature update

What’s New in Notebooks | June 2026

Mercedes-AMG PETRONAS F1 Team responds to the intensity of race weekends with Microsoft

AI brands as bait: How threat actors are using the AI hype in social engineering

AI Is Starting to Feel Like the Petrol Bowser

image

I filled up the car last weekend and did that thing we all do now — glanced at the price per litre, winced a little, and worked out whether to fill the tank or just put in enough to get me through the week. It struck me, standing there, that I’ve started having the exact same conversation about AI.

For a while, AI felt free. You paid your subscription, you used it, and the meter never seemed to run. That era is ending. Token prices, usage caps, premium request limits — the cost of running AI is becoming visible, metered, and impossible to ignore. For a small business, it’s shifting from a novelty into a line item. And like petrol, it’s no longer optional. You can’t really run the business without it, but you can’t ignore what it costs either.

A running cost, not a one-off

The mistake I keep seeing is treating AI like a piece of software you buy once and forget. It isn’t. It behaves far more like fuel or electricity — something you consume, in varying amounts, every single day. Some weeks you’ll barely touch it. Other weeks, when you’re deep in a proposal or cleaning up a quarter’s worth of numbers, you’ll burn through it.

That changes how you should think about it. A running cost needs watching. It needs a budget. And it needs someone, every so often, asking the plain question: are we actually getting value for what we’re spending here?

Spend where the work actually is

Here’s where it gets interesting for a small business. You haven’t got an unlimited tank, so you have to decide where AI earns its keep. For most of the small operations I work with, the answer isn’t exotic. It’s the boring, repetitive, time-sapping work — the email triage, the first draft of a report, the summary of a long meeting nobody wants to rewatch.

That’s exactly where Copilot inside Microsoft 365 pays for itself. Asking Copilot in Outlook to clear and draft replies to a morning’s backlog saves real hours. Having it summarise a Teams meeting you missed, or pull the key figures out of an Excel workbook, turns an afternoon into a few minutes. The trick is to point your spend at the tasks that are costing you time and money today — not the shiny demos that look clever but never touch your actual week.

Economise without going without

The same way you don’t leave the car idling in the driveway, you don’t want AI burning through your allowance on low-value busywork. Be deliberate. Use the everyday Copilot features that already come with your licence before you reach for premium-priced add-ons. Give your people a quick steer on what’s worth asking and what’s just noise. And look at the bill — actually check where the consumption is going, the way you’d question a sudden jump in the power account.

None of this is about spending less for its own sake. It’s about spending on purpose.

Where I’ve landed

Petrol taught small business owners to think in terms of value per trip, not just price per litre. AI is heading the same way. The ones who do well won’t be those who spend the most or the least — they’ll be the ones who know exactly what they’re buying and why. Watch your usage, back the work that matters, and treat AI like the utility it’s quietly becoming. The meter is running now. Best to know what it’s running on.

Your first Copilot Studio agent — and the bits the demo skips

MAI_111667a8d6c40e32

Everyone wants to build an agent right now.

It’s the demo that makes the room go quiet. You describe what you want in plain English, and thirty seconds later there’s a working assistant answering questions from your own documents.

Then the bill arrives. Or worse — it doesn’t, because nobody published the thing and it’s sitting in a maker’s personal environment doing nothing.

Here’s what I keep seeing. People treat an agent as a science project. They build one, screenshot it, post it on LinkedIn, and move on. The client never touches it.

That’s not a product. That’s a party trick.

If you’re an MSP, the agent isn’t the deliverable. The service around it is. Let me show you the bits people skip.

What is a Copilot Studio agent, really?

Strip away the marketing and an agent is three things: instructions, knowledge, and tools.

Instructions are the job description — what it does, the tone it takes, when to give up and send someone to a human. Knowledge is what it’s allowed to read: a SharePoint site, a public page, a handful of documents. Tools are the actions it can take, like logging a ticket or looking up an order.

That’s it. You’re not training a model. You’re scoping a very literal new hire.

And there are two doors into this. The Agent Builder baked into Microsoft 365 Copilot, and Copilot Studio proper. The choice between them comes down to audience and reach — a quick helper for your own Copilot chat, or a real one you publish out to Teams, a website, wherever your client’s people already work.

Step-by-Step: building your first agent

Portal only. No code.

Open the studio

Go to copilotstudio.microsoft.com and check the environment name in the top right. This matters more than it looks. Build in the wrong environment and you’ll be untangling it later. Pick the client’s environment deliberately, every time.

Describe what you want

You get a box. Type what the agent should do in your own words — that’s the whole guided, no-code start. Mine for a small-business help desk reads like this:

Help our staff with common IT questions — password resets,
VPN setup, who to call for hardware. Answer only from the
company IT knowledge base. If you're not sure, say so and point
them to the service desk. Don't guess.

Notice what’s missing? No model to pick. No temperature dial. No code. You’re writing a job description in plain English. And the load-bearing line is the last one: ask it once to admit when it doesn’t know. An agent that says “I’m not sure” beats one that bluffs with total confidence.

Add knowledge, narrowly

Point it at one good source first. The company FAQ. The IT policy site. Not everything you own — one trusted thing. Test it. Then add more. An agent fed the whole tenant on day one is an agent that confidently surfaces the wrong document.

Test like a real person

Use the test pane on the right. Ask the messy questions: “can’t log in”, “where’s the VPN guide”, “who do I call”. If it waffles, fix the instructions — not the model.

Publish it

This is the step everyone forgets. An agent does nothing until you hit Publish. And every change you make afterwards needs publishing again, or your users sit on the old version. Then add a channel — Teams and Microsoft 365 Copilot are the obvious two — and decide who’s allowed in.

By default it’s Authenticate with Microsoft, which means your tenant and no one else. Leave it there. “No authentication” hands a working link to the entire internet. For an internal SMB agent, that is never what you want.

The licensing question you answer first, not last

Here’s the bit the demos never mention.

Agents built in the Agent Builder inside Microsoft 365 Copilot ride along with the licence your client already pays for. The custom agents you build and publish in Copilot Studio consume Copilot Credits — and since September 2025 that’s the currency Microsoft meters them in. Pay-as-you-go, or prepaid packs.

“So I just describe it and it works?” Yes — and that’s exactly the trap. The describing is the easy part. The scoping, the publishing, and the consumption call are the actual job.

So before you build, settle one thing: is this an internal helper for a few Copilot users, or a published agent the whole company will hammer all day? The answer decides which door you walk through and whether there’s a consumption bill hanging off it.

Get that wrong and you’ve either over-built a toy or under-budgeted a product.

The point of an agent isn’t to look clever for ninety seconds in a demo.

It’s to take a repetitive question off a human’s desk and answer it the same way, every time, at 2am. A published agent earns its keep. An unpublished one is a screenshot.

Build one narrow agent, publish it properly, and put your name on the governance around it. If you’re not showing your clients this, someone else will — and they’ll be the ones charging for it.

The Hiring Shift Copilot Has Quietly Forced

image

A few weeks ago I watched someone forward a Copilot-drafted email to a client without really reading it. The tone was off. A figure was wrong. The client picked it up before they did. Nobody was being lazy — they were being efficient, in the exact way we’ve all been trained to be efficient. Get the task done. Move to the next one. That small moment has stuck with me, because I think it points at something much bigger that’s quietly reshaping how small businesses need to think about the people they hire, and the behaviours they reward.

For most of my working life, businesses hired people to do things. Send the email. Build the report. Process the invoice. Update the spreadsheet. Speed and responsiveness were the metrics that mattered most. If you could turn incoming requests into completed work quickly and reliably, you were valuable. That model held up because doing the thing was the hard part, and doing it well took real skill, attention and time.

The work that used to be hard isn’t hard anymore

Copilot has quietly upended a lot of that. Drop into Outlook and you can have a draft reply in seconds. Open Word with a half-formed idea and Copilot will hand you a structured first pass before your coffee has cooled. Excel will summarise a sheet, flag the anomalies, and suggest a formula it thinks you wanted. Teams will catch you up on the meeting you missed and tell you what was decided and who owns what. Every one of those tasks used to be where someone earned their keep. Now they’re table stakes.

What’s left isn’t the doing. It’s the deciding. Was that actually the right answer? Does the draft fit the specific client we’re dealing with, or the average client Copilot has imagined? Is the figure it pulled from SharePoint the current number, or one from two restructures ago that nobody got around to archiving? Should we even send this email, or is there a phone call hiding behind it?

We’ve been training people out of asking

Here’s the part I find uncomfortable. A lot of small businesses have spent years quietly training their people out of pausing. We rewarded responsiveness over reflection. Inbox zero over inbox thoughtful. Closing tickets over questioning whether the ticket made sense in the first place. Over time, some genuinely good people got very fast at moving work between systems without really engaging with any of it.

That worked when the slow, expensive part of the job was producing the output. It doesn’t work now. The slow part is the human bit — the read, the sense-check, the quiet moment of “this doesn’t sit right with me” that keeps a business out of trouble with a client, a regulator, or its own future self.

The maths has flipped

When output was expensive, mistakes were rare almost by accident. There was friction in the system, and friction gave people time to second-guess themselves. A bad proposal took half a day to write, so it usually got read twice before it left the building. A bad proposal now takes ninety seconds, and so do the next ten after it.

The businesses that come out of this next stretch in good shape won’t be the ones with the fastest Copilot adopters. They’ll be the ones that have quietly shifted what they recognise and reward — from doing the thing, to noticing when the thing isn’t right. That’s a hiring conversation, a performance review conversation, and most of all a culture conversation. And in most of the small businesses I see day to day, it’s well overdue.

Copilot Credit Pre-Purchase Plans

Ok, deep breath before we start. In. Out. Let’s start.

If you want to purchase Copilot Credits for use with Cowork you’’ll need access to https://admin.microsoft.com. Then you’ll need to navigate to Copilot | Cost Management | Configuration. You’ll then need to select Buy prepaid credits.  Then you need to select a Subscription, then How many credits you want from the table that displays.

Upon selection, you’ll be shown the price and then you can pay via the Checkout.

If you look closely you’ll also see this.

So, billing is measured in CCCUs. 1 x CCCU = 100 credits. CCCU means Copilot Credit Commit Unit.

Given that this PAYG style billing is applied against an existing Azure subscription, if you go into the Azure portal and locate Reservations you find another location where you can pay:

Again, here, we have Copilot Credit Pre-Purchase Plans measured in CCCUs.

At the lowest prepaid tier you get 5% discount and at the pre-paid top tier you get a 20% discount, with remaining tiers in between these two. Any overage returns to be being billed with no discount at the base rate.

If you now look at how usage is reported, you see it is reported in Copilot Credits, not CCCUs. So CCCUs appear to be a billing construct only.

Thus, if we focus on just the Copilot Credits (not CCCUs) we get the Microsoft quoted US$0.01 per Copilot Credit. Thus, the above consumption cost becomes 1,574 x US$0.01 = US$15.74 in real money.

Thus, to enable Copilot Cowork going forward you will need:

– M365 License (e.g. M365 Business Premium)

– M365 Copilot license (to enable premium Copilot capabilities like Cowork)

– An Azure subscription for Copilot Cowork to be billed against

– Cowork consumption and billing is tenant wide, not per user

That will bill Copilot Cowork at a PAYG rate of $0.01 per Copilot Credit. A simple average would be to assume each Cowork interaction will consume around 400 credits. That is, around US$4 every time ANY user uses Cowork. This is because Cowork interactions vary on how many credits they use based on their complexity of the request and actions taken.

You can pre-purchase Copilot Cowork credits at average discounted rates starting from US$0.0095 down to $0.0080 (i.e. 5 – 20% discount) for a fixed annual commitment.

Annual pre-paid Copilot Cowork credits are measured in Copilot Credit Commit Units (CCCUs) which have the ratio of 100 credits per 1 CCCU. The entry level CCCU is 3,000 which provides 300,000 credits across all users in the tenant.

These credits can be purchased from the M365 admin portal or the Azure portal (vis Reservations).

An administrator can restrict Copilot Cowork in various ways to control costs but that is the subject for additional post.

….. and we are done. Breath. In. Out.

The Sales Process That Stopped Feeling Like Selling

image

The best sales conversations I’ve watched in the MSP world don’t feel like sales conversations at all. They feel like someone helping someone else work out what’s actually going on. There’s a diagnosis. There’s a plan. And then, at the very end, there’s a quiet question: would you like a hand putting this in place? That’s the whole thing. No closing technique. No manufactured urgency. No script that leaves either side feeling slightly off afterwards. Just a useful hour and a natural offer at the end of it.

Help is the offer

A few of my clients have built their front door around a paid consult. Someone pays a modest fee, sits down for an hour, and walks out with a real read on what’s happening inside their tenant — security gaps, licence waste, the four Copilot use cases their team would actually adopt, the Conditional Access policy that’s been quietly broken for months. The deliverable isn’t a quote. It’s clarity.

That changes the dynamic. The buyer isn’t being sold to. They’re being helped. And by the time the hour is up, they already know whether the person across the table is worth working with, because they’ve seen them work.

This is where Copilot has quietly become a useful ally in those conversations. Rather than disappearing for a week to write up findings, the consultant pulls a draft summary together in Word with Copilot during or right after the session — referencing the discovery notes, the screenshots from the tenant review, the Secure Score export. The buyer leaves with something tangible the same day. The speed is part of the help.

The invitation writes itself

Here’s the bit most MSPs still miss. When you have genuinely helped someone — when they walk out the door clearer than they walked in — you don’t need a pitch. You need one sentence. Want us to do this for you?

That sentence works because the buyer has already done the qualifying themselves. They’ve seen your thinking. They trust the diagnosis. They want the plan executed. The proposal that follows is short, because the work has been pre-sold by the consult itself.

I’ve watched clients use Copilot in Outlook to turn the same notes into the follow-up email — the recap, the recommended next steps, the link to a SharePoint page with the proposed scope. It lands inside a few hours, while the conversation is still warm. Nothing about it feels like a chase. It feels like a continuation.

Why this beats the old playbook

Free discovery calls dressed up as consults don’t fool anyone anymore. Buyers have sat through enough of them to recognise when they’re being qualified rather than helped. The free version trains people to expect a pitch at the end. The paid version trains them to expect value — and a small amount of money on the table changes how seriously both sides show up.

For MSPs trying to move up the value chain, this is a quieter, more dignified way to do it. You stop hunting. You start advising. The right buyers — the ones who want a partner rather than a price — self-select towards it. The wrong ones fall away on their own. That filtering is worth the effort by itself.

The thing I keep coming back to is how much pressure this approach takes off both sides of the table. The buyer doesn’t have to fend off a pitch. The MSP doesn’t have to manufacture one. Helping first, then inviting, with Copilot doing the heavy lifting on the write-up, turns the sales process into something that actually resembles the work itself. Which, when I think about it, is probably the point.

Copilot in Word

MAI_d023a379a3a6732e

Most people meet Copilot in Word the same way. New blank document, click the icon, type “write me a proposal,” hit Generate.

Out comes 400 words of beige. Technically correct. Completely generic. The kind of thing that could be about your business or anyone else’s.

So they shrug, decide Copilot “isn’t that good,” and go back to writing from scratch.

Here’s the thing. They weren’t using Copilot wrong. They were using the worst part of it and ignoring the best part.

A blank page is the one thing Copilot is genuinely bad at. Give it nothing and it gives you nothing — just confident, well-punctuated filler. The magic isn’t in asking it to invent. It’s in pointing it at what you already have.

What is Copilot in Word, really?

Forget the demos where someone conjures a document from a one-line prompt. That’s the party trick, not the job.

What Copilot in Word actually does well is take your material — a file, an email, a meeting, a folder — and reshape it into something new. The official term Microsoft uses is grounding. The button you press is Reference a file.

That’s the whole ballgame. You’re not asking a stranger to guess what your last client proposal looked like. You’re handing it the last one and saying “another like this.”

So the question stops being “can Copilot write?” and becomes “what do I already have that Copilot can stand on?” For most SMBs, the answer is a lot. Years of proposals, reports, policies, and SOWs sitting in OneDrive, doing nothing.

Step-by-Step: drafting from something you already have

This is the workflow I show every client. It takes about ninety seconds.

Open a new document

Start a blank document in Word, then click the Copilot icon. You’ll get the Draft with Copilot box. Don’t type your prompt yet.

Reference the file first

Click Reference a file (the paperclip), and start typing the filename. Pick the document you want Copilot to learn from — an old proposal, a strong report, a policy you’re proud of. You can attach more than one. Microsoft has the full walkthrough in Draft and add content with Copilot in Word, and the Welcome to Copilot in Word page confirms it only ever looks at the files you choose — nothing else.

Write your prompt

Now tell it what you want, and point it back at what it’s holding:

Draft a one-page proposal for Acme Pty Ltd.
Reference: /Northwind-Proposal.docx /Acme-Discovery-Notes.docx
Match the structure and tone of the Northwind proposal.
Keep it under 400 words.

Notice what’s missing? Nowhere do I explain what a proposal is. I’m not teaching Copilot to write. I’m showing it how we write and telling it to do that again.

Keep, regenerate, or bin it

Copilot drops the draft in. Keep it, Regenerate for another go, or Discard. Then you edit like a human — because you still have to.

Why this actually changes behaviour

Before: “Copilot, write me a client report.” → generic mush you rewrite anyway. After: “Copilot, write this report the way I wrote the last three.” → a first draft that already sounds like the business.

That second one is the difference between a toy and a tool.

Here’s the real win for MSPs. Grounding turns your clients’ own document history into an asset they didn’t know they had. Every good proposal becomes a template. Every solid SOP becomes a pattern. The licence they’re already paying for suddenly does something a free chatbot never can — because the free chatbot can’t see their files.

And it’s not just drafting. Flip it around and Copilot becomes a reading tool. Open a long contract, type Summarize this document, and it’ll hand back the gist with citations back to the source — chat with Copilot about your Word document covers that side. Summarize before you read. Draft from what you’ve got. Same tool, both directions.

Don’t ask Copilot to know your business. Show it.

If you’re rolling Copilot out to clients and the first thing you teach them is “type a prompt on a blank page,” you’ve handed them the weakest trick in the box and you’ll get the predictable shrug.

Teach Reference a file first. That’s where the value lives, and it’s the bit nobody stumbles onto by accident.

Reference a file isn’t there to help you write faster. It’s there to make sure what gets written already sounds like you.