Microsoft is rolling out a new margin model for the Microsoft Cloud Solution Provider program, and it’s unlike anything partners have worked with before. Instead of a flat margin applied evenly across your book, CSP Growth Margin pays partners more for specific growth behavior — and it does so customer by customer, renewal by renewal.
It launches October 1, 2026. Sandbox access opened back in July, pricing breakdowns and the official Growth Margin Guide followed later that month, and billing reconciliation data starts flowing in early August. The rollout is already underway — most partners just haven’t felt it yet.
Here’s what it actually is, why it’s more complex to manage than it sounds, and what to check before it hits your book.
What CSP Growth Margin Actually Is
Growth Margin rewards Microsoft CSP partners — distributors, indirect resellers, direct bill partners, and scale solution providers — with higher margin for driving new-to-offer wins, seat expansion, and adoption across select AI workloads. Per Microsoft’s official documentation, partners can view and download growth margin details directly in the Partner Center Pricing workspace, including offer dates, discount type and value, term, and billing cycle for each qualifying product. The more you grow a customer’s engagement with qualifying products, the more margin you earn on that customer.
It sounds straightforward until you look at how it’s actually calculated and applied. Five details make this a genuinely different kind of margin to manage:
It’s evaluated per customer, not per account. Eligibility is assessed at the individual customer tenant level. One customer might qualify for Growth Margin on their next purchase; another, on the same offer, might not.
It’s not additive. Growth Margin adjusts your base margin — it doesn’t stack on top of it. Treating it as an extra layer on top of existing margin rules will produce the wrong number.
Certain SKUs are excluded entirely. Nonprofit, Education, and Government SKUs don’t qualify for Growth Margin, regardless of the customer’s growth behavior.
It can change at renewal. Growth Margin eligibility isn’t locked in at the original purchase. Microsoft re-evaluates it at renewal, meaning a customer’s margin can shift the same way mid-cycle subscription changes already do — without a new sale ever happening.
It shows up as a new data point on reconciliation files. Microsoft is adding a distinct attribute to identify Growth Margin line items in billing and invoice data — the kind of reconciliation detail that’s easy to miss without the right process in place.
Individually, none of these is complicated. Together, across hundreds of customers and renewal dates, they’re exactly the kind of detail that a flat, manually-managed pricing sheet quietly gets wrong — the same margin erosion partners already lose to when pricing isn’t kept current.
Before October 1: What to Check
Whether or not CSP Growth Margin affects your book of business today, it’s worth a quick self-check before it launches.
That’s the platform-level check. The next one is about which customers actually need your attention first.
How Hybr® Helps with CSP Growth Margin Today
Growth Margin pushes complexity down to the individual customer level — different eligibility, different exclusions, different margin outcomes that can shift at renewal. Here’s what that actually requires from a billing platform, and where Hybr already stands today.
Per-customer pricing, not one-size-fits-all. Growth Margin eligibility is evaluated at the individual customer tenant — not your account as a whole. Hybr’s Pricing Profiles are built for exactly this: each profile can be assigned to a specific customer, so one tenant’s margin rules never bleed into another’s. If Growth Margin means one customer qualifies and another doesn’t, that’s not a workaround — it’s how Hybr’s pricing engine already works.
Rules that don’t stack by accident. Microsoft has confirmed Growth Margin is not additive — it adjusts the base margin rather than piling on top of it. Hybr’s pricing engine applies the specific rule assigned to a service or subscription rather than layering multiple rules together, so there’s no risk of a margin silently compounding into a number nobody intended.
Keeping excluded SKUs excluded. Nonprofit, Education, and Government SKUs don’t qualify for Growth Margin. Hybr’s Pricing Profiles support this kind of granularity today — specific services or SKU groups can be routed to a different profile, so excluded categories stay on their own pricing logic instead of accidentally inheriting a rule meant for something else.
What still needs a manual step — for now. Two things are worth being upfront about. First, Growth Margin eligibility can change at renewal — a similar blind spot to the renewal-timing traps that already catch partners on the Microsoft licensing side — and while Hybr lets you update a customer’s Pricing Profile at any time, it doesn’t yet auto-trigger that update based on Microsoft’s eligibility logic — that’s a manual review today, not an automatic re-evaluation. Second, Microsoft is adding a new data attribute to reconciliation files to flag Growth Margin line items; Hybr’s data ingestion will need to map that new field before it shows up automatically in reconciliation and invoicing.
Neither of these is unusual for a program this new — Microsoft itself is still rolling out sandbox access, pricing breakdowns, and renewal logic through September. What matters is the foundation: the per-tenant precision and SKU-level control Growth Margin requires already exist in Hybr. The two remaining pieces are a near-term update, not a structural gap.
CSP Growth Margin: Ready for the Transition
Growth Margin isn’t a pricing tweak — it’s a new kind of variable that lives at the customer level, changes at renewal, and needs to be reflected accurately on every invoice it touches. Programs like this are where flat, manually-managed pricing sheets start to break down, one exception at a time.
Hybr isn’t claiming to have this fully automated end to end — and we’d rather tell you that plainly than oversell it. What we can say is that the foundation Growth Margin demands — per-customer pricing, non-additive margin logic, and SKU-level exclusions — is already how Hybr’s pricing engine works today. That’s not nothing: it’s the hard part most billing platforms built on flat pricing sheets will have to rebuild from scratch.
If you’re a Microsoft CSP partner heading into October without a clear answer to “can my platform handle per-customer margin that changes at renewal?” — now’s the time to find out, not after your first Growth Margin invoice goes out wrong. For more on what’s changing across the Microsoft partner ecosystem, browse the Hybr blog.
Curious how Hybr® Pricing Profiles handle this in practice? Let’s talk. — book a demo.