Microsoft Copilot for MSPs: The Licensing and Margin Math Before July 1

Microsoft Copilot Business has a date attached to it.
Through June 30, 2026, the promo price is $18 per user, per month. On July 1, it moves to $21. That is not a small pricing note for MSPs. It is a client conversation, a margin question, and a reason to review who actually benefits from the license before the deadline closes the window.
The quick version: if you manage SMB clients on Microsoft 365, this is one of those offers that can either become a clean upsell or a dead line item. The difference is whether you know who should buy it, what it stacks with, and what you make after channel math.
Quick answer: MSPs should recommend Microsoft Copilot Business to clients already using Business Standard or Business Premium, with people who draft, summarize, search, and live in Outlook, Teams, Word, or Excel, and with at least one internal champion who will actually use it. Hold off for tiny, high-turnover shops, low-adoption tenants, or clients who still treat M365 like a file cabinet.
What Copilot Business actually is
Microsoft 365 Copilot Business is the SMB version of Copilot. Microsoft’s pricing page says it is for organizations with up to 300 users, and it requires a qualifying Microsoft 365 plan. In practice, that means it is the add-on conversation MSPs have with Business Basic, Business Standard, and Business Premium customers.
It is not the same conversation as enterprise Copilot. Enterprise Copilot is a different licensing path and usually belongs in larger E3 or E5 environments. If a client is truly SMB, the business add-on is the thing to evaluate first.
The point of Copilot Business is simple. It puts AI inside the apps people already use:
- Outlook for email triage and drafting
- Word for first drafts and rewrites
- Excel for analysis and summaries
- PowerPoint for slide generation
- Teams for meeting follow-up and note cleanup
Microsoft also says the current business plan includes agents and Work IQ context, plus enterprise-grade security, privacy, and compliance controls. That matters, but only if the client actually uses the apps enough for the license to do anything useful.
The July 1 pricing reality
Here is the math MSPs should care about.
| SKU | Promo price through June 30 | Price from July 1 | Change |
|---|---|---|---|
| Copilot Business add-on | $18/user/month | $21/user/month | +$3 |
| Microsoft 365 Business Basic + Copilot Business | $27/user/month | $28/user/month | +$1 |
| Microsoft 365 Business Standard + Copilot Business | $22/user/month | $35/user/month | +$13 |
| Microsoft 365 Business Premium + Copilot Business | $32/user/month | $43/user/month | +$11 |
Microsoft’s own Tech Community post says the promotional pricing runs through June 30, 2026, and that pricing updates take effect July 1. The same post shows the Copilot add-on moving from $18 to $21, with bundle pricing rising too.
That is the actual deadline pressure. It is not just a Microsoft marketing moment. It is the last date to lock current pricing before the renewal math changes.
For a 25-seat client, the add-on difference alone is $75 per month, or $900 per year. If you are quoting the Business Standard bundle at the promo price, the jump to July 1 pricing is even larger. That is enough to matter in a QBR, especially if you are trying to get a client to commit before the price moves.
The margin math MSPs should actually use
The resale margin is not the big story. The service margin is.
If your channel margin on Copilot Business is 10%, then:
- 25 seats at $18 = $450/month in revenue, about $45/month in gross resale margin
- 25 seats at $21 = $525/month in revenue, about $52.50/month in gross resale margin
- Annual resale margin on 25 seats at 10% is $540 at the current promo price
That is not life-changing money by itself. It becomes meaningful when Copilot is part of a broader advisory motion:
- onboarding and adoption kickoff
- prompt library and workflow setup
- user training
- QBR review of usage and outcomes
- roadmap updates tied to actual productivity gains
That is where MSPs can charge real service fees. A $500 to $1,500 onboarding engagement plus a $15 to $25 per user monthly management layer is where the economics start to work. If you only resell the license, you are mostly making pocket change.
When to recommend it, and when to say not yet
Do not sell Copilot because it is new. Sell it because the client has a use case.
Recommend Copilot Business if:
- the client is already on Business Standard or Business Premium
- users spend real time in Outlook, Teams, Word, or Excel
- the client has knowledge workers doing drafting, summarizing, or document review
- there is one person inside the company who will drive adoption
- you can point to a clear before and after workflow
Say not yet if:
- the client is on Business Basic and mostly uses email plus light Teams
- fewer than 10 seats are involved and turnover is high
- M365 adoption is low enough that another license will just sit there
- nobody inside the client owns rollout or training
- they still need the basics fixed before AI makes sense
That last point matters. Copilot is not a substitute for a messy tenant, a broken process, or a half-adopted Microsoft 365 stack.
How to position Copilot in your stack
There are three sane ways MSPs can package this.
1. Standalone line item
Keep Copilot as a separate SKU. This is the cleanest way to test demand and explain the cost.
Use this when the client is curious but not ready to change the service bundle.
2. Bundled into vCIO
Treat Copilot as part of the advisory motion. You recommend it, roll it out, and review adoption as part of the roadmap.
Use this when you want to be the strategic partner, not just the reseller.
3. Upgrade-path driver
Use Copilot to move a client from Business Basic to Business Standard or from Standard to Premium.
That works when the use case justifies a bigger Microsoft 365 tier and Copilot is the nudge that makes the upgrade easy to explain.
Most MSPs should start with standalone, then move toward the bundled model once they have a repeatable adoption playbook.
The client conversation to have before July 1
This does not need to be theatrical. It needs to be direct.
Microsoft is changing Copilot Business pricing on July 1. We checked your current M365 tier, seat count, and likely usage. Based on what your team does today, here is whether Copilot makes sense, what it would cost, and what we would recommend before the promo window closes.
That message works because it is specific. It shows you looked at the account instead of forwarding a vendor announcement and calling it account management.
If the client is qualified, lock the current price before June 30 where it makes sense. If they are not, say no cleanly and move on.
Where Scopable fits
Scopable is useful here because this is the kind of decision that should come from the roadmap, not from a random sales email.
If a client is already using M365 heavily, the right question is not just "Should we buy Copilot?" It is "Which workflows are wasting time, and does this license change the roadmap enough to matter?"
That is the point of pulling real environment data into the conversation. The license is easy. The decision is the hard part.
If you want a broader pricing context for M365 changes this summer, the M365 July 2026 price increase playbook is the better companion read. And if you are still comparing how to package quoting and advisory work around it, best MSP quoting software in 2026 is the next stop.
Bottom line
Copilot Business is worth recommending when the client already lives in Microsoft 365 and can point to work that AI will actually speed up. It is not worth pushing just because the deadline is close.
The MSP win is not the license margin. It is knowing which clients will use it, locking the right price before July 1, and turning the rollout into a small advisory project instead of a one-off upsell.
If you want help turning license decisions into actual client roadmaps, join Scopable early access.


