Microsoft didn’t announce the death of the resale model. They just changed the math.

Partners who pay attention to numbers rather than press releases have seen it coming for a while. The 2026 CSP restructuring is moving in one clear direction: standalone transactional license margins are getting squeezed, while services, managed work, and Copilot adoption support are where Microsoft is pointing its incentive dollars. The trend is confirmed by Microsoft’s own Partner Center announcements and multiple partner briefings. The exact percentages being reported in the channel press — figures like 15-20% margin reduction on license resale, 30% managed services incentive increases — are sourced from analyst summaries rather than official Microsoft documentation, and the specifics may shift as the program rolls out. What isn’t in dispute: the direction.

That’s not a gentle nudge. That’s an engine pulling away from the platform while you stand on it.

The Actual Math

Let’s work through what margin compression on license resale means in practice — even if the exact percentage won’t be the same for every partner or every tier.

If you’re running a $2M ARR Microsoft book and 60% of that is transactional licensing, you have $1.2M in license revenue. Any meaningful margin compression — Microsoft has been reducing margins on standalone license sales for several years, with partner briefings pointing to accelerating changes in 2026 — costs you real gross profit dollars. That doesn’t evaporate. But it doesn’t replace itself automatically either. You have to earn it somewhere else, specifically in services, adoption support, and Copilot implementations where Microsoft is actively pointing incentive dollars.

The math works for partners who make the transition. It doesn’t work for partners who try to hold the old model together with margin compression on one side and no service revenue growth on the other.

Microsoft knows this. It’s deliberate. They’re not trying to destroy resellers. They’re trying to force a capability upgrade across their channel because the product has outgrown the old distribution model.

The Certification Trap (And the Opportunity Hiding Inside It)

The new CSP tiers require certified staff across six solution areas: Modern Work, Security, Azure Infrastructure, Azure Data & AI, Business Applications, and Digital & App Innovation. Partners who don’t meet these requirements face reduced margins and potential program suspension.

Here’s what most partners are going to do with this information: panic. They’ll look at six certification tracks, calculate the training hours, and conclude they can’t get there.

That’s the wrong read. You don’t need all six. You need the ones relevant to your client base.

Most SMB-focused MSPs can build a defensible position in Modern Work, Security, and Azure Infrastructure. That’s three of six. Pick the two that match your largest revenue concentration and build from there. The partners who get into trouble are the ones trying to maintain a generalist presence across all six without depth in any of them — which is exactly what Jaxon wrote about back in January when the generalist VAR model was already dying.

The certification requirement is painful in the short term. In the medium term, it’s a moat. Once you’ve built a certified practice in two or three areas, the uncertified competitor across the street can’t just show up and undercut your Copilot implementation quote. They don’t have the credentials or the methodology.

That’s not a small thing.

The Copilot Mandate Is Real

Microsoft is making “Copilot Expert” certification worth 25% higher margins on Copilot-related services and priority access to Microsoft’s own technical specialists. They’re restricting Copilot Studio customization tools and APIs to top-tier certified partners only.

That last piece deserves attention.

API access for Copilot Studio customization — the capability that lets you build industry-specific Copilot implementations — is gated by certification level. If you’re not certified, you can’t build the differentiated product. And if you can’t build the differentiated product, you’re competing on price against everyone else running the default implementation.

That’s a race to zero. Partners have run that race before with hardware, with commodity cloud storage, with basic M365 licensing. You know how it ends.

The Copilot mandate isn’t about becoming a Microsoft marketing vehicle. It’s about getting access to the tools that let you build something clients can’t easily commoditize. Microsoft’s partner briefings frame this as a “Copilot readiness, implementation, and optimization” service trio — assessment first, deployment second, ongoing adoption third. Each stage is billable. None of it is automated.

That’s where the margin went. It’s not gone. It just requires more skill to capture now.

The Dead Playbook

There’s a version of this article I could write that’s softer — that says Microsoft is “evolving” its channel and “creating opportunities” for partners who “embrace transformation.” That version is useless.

Here’s the direct version.

If your Microsoft revenue in 2026 still looks like it did in 2023 — primarily transactional, primarily volume-driven, with limited services attachment — you’re running on borrowed time and borrowed margin. The compression is already built into the new program structure. You’re not going to negotiate your way out of it. The program doesn’t have a grandfathering clause for partners who prefer the old model.

The transition Microsoft is forcing is uncomfortable because it requires investment before the returns arrive. You have to pay for certifications, train staff, build service methodologies, and run Copilot implementations at a loss or near-zero margin while you’re figuring out the delivery model. Most of that costs money now for revenue that lands 12-18 months later.

That’s the actual barrier. Not the certifications themselves, not the Copilot product, not the six solution areas. It’s that the transition has a cash curve that small MSPs find hard to absorb.

There are a few ways to get through it. Build the certifications incrementally — one area at a time, starting with the one closest to your existing revenue concentration. Partner with someone who already has the credentials you lack while you build yours. Find two or three anchor clients willing to be early adopters on Copilot and use their implementations to fund the practice build.

The alternative is watching margin compress until the business doesn’t work. That’s the same math that killed dozens of hardware-focused VARs when cloud ate the hardware refresh cycle. The channel has been through this movie. Most people know how it ends.

Microsoft gave you a detailed roadmap this year. Use it.


Have you started the Copilot certification process? Hit reply — I want to know what the actual timeline looks like on the ground, not just in the partner briefing slides.