CloudCockpit Team | Published July 24, 2026
Growth margins are a new incremental partner margin Microsoft is adding to the Cloud Solution Provider (CSP) program, effective October 1, 2026. They stack on top of a partner's standard base margin whenever a transaction meets one of four qualifying growth scenarios, and Microsoft scopes the program to Direct Bill partners and Distributors only. This article covers how those four scenarios work, what changes at renewal, and how the margin actually gets calculated on top of base margin and promotions.
Microsoft's own documentation is explicit about what this is and isn't: "When a growth margin applies, you receive a new partner price for the transaction in addition to your standard base margin. Growth margins are partner-earned economics (a partner margin), not a customer-facing discount."
CloudCockpit note: As of this writing, the growth margins experience and APIs are live in the Partner Center Sandbox only, not in production. Partners can test eligibility scenarios and pricing today, but nothing transacts live until the October 1, 2026 launch. Treat anything you see in sandbox as a preview of the rules, not a guarantee of what a specific customer will qualify for on day one.
Four scenarios determine whether a transaction earns growth margin, and each one is really a specific way to shape a customer conversation so the deal lands inside the margin instead of outside it.
CloudCockpit note: The seat expansion rule is easy to miss operationally. If a provisioning workflow just adds seats to a customer's existing subscription because that is the path of least resistance, that expansion is already disqualified from growth margin, even if everything else about the deal would have qualified. Flagging mid-term expansions before they are provisioned, not after, is what actually captures this.
A deal that doesn't meet these criteria isn't blocked: it simply transacts at standard, non-margin pricing, and Microsoft's growth margin eligibility API returns the specific reason before a partner submits the order. The most common reasons are:
Growth margin only lasts for the term it was earned on, so every renewal is its own eligibility check, not an automatic extension of what was already in place. Microsoft's documentation states it directly: "Growth margins are valid for the term of the purchase. At renewal, the subscription reverts to the base margin unless the customer independently requalifies for a growth margin under the then-current criteria."
Eligibility is re-evaluated close to the renewal date, so a margin that's visible when a renewal is first scheduled can change, or disappear, by the time it actually processes. Confirm the applied margin near the renewal date itself rather than assuming it carries forward from when the renewal was scheduled.
CloudCockpit note: Because re-evaluation happens close to the renewal date rather than at the point of sale, a growth margin a partner sees weeks or months ahead of a renewal is provisional, not locked in. Build a habit of re-checking eligibility in the days immediately before the renewal date, not when the renewal is first scheduled, especially on larger accounts where the difference moves real margin.
Seat reductions on a subscription earning growth margin are only allowed down to the minimum seat count required to keep the margin. Drop below that minimum, and the entire subscription has to be canceled within the standard cancellation window; it cannot be partially reduced instead.
Growth margin stacks additively on top of base margin, and any customer promotion is applied after both, so the calculation always follows the same order: base margin, then growth margin, then promotion.
| Scenario | Formula | Illustrative example |
|---|---|---|
| Base margin only | ERP × (1 − base margin %) | $100 × (1 − 20%) = $80.00 |
| Base margin + growth margin | ERP × (1 − base % − growth %) | $100 × (1 − 20% − 15%) = $65.00 |
| Base margin + growth margin + promo | (ERP × (1 − base % − growth %)) × (1 − promo %) | ($100 × (1 − 20% − 15%)) × (1 − 10%) = $58.50 |
The percentages above are illustrative, taken directly from Microsoft's own documentation; actual rates vary by product, market, and offer. The rule that stays constant is the order of operations: margin first, promotion second.
The next step for most CSP partners is approval-gated self-service, where a customer can request a change but a partner or a policy engine confirms it before the order becomes billable.
Neither of Partner Center's native tools gets partners there today. Azure spending budgets alert on usage, they do not block it, and the AllowSelfServicePurchase policy that governs Microsoft's own self-service purchase feature is a binary switch, on or off per product, not a workflow with a checkpoint in between.
CloudCockpit note: This is the gap we hear about most from partners who want to offer self-service without giving up control of their own margin. An approval step, where a customer-initiated request sits for partner confirmation before it becomes a billable order, turns self-service from an exposure into a convenience. It is an operational pattern, not a built-in Microsoft feature, so today it has to be built or bought.
As Partner of Record validation and other compliance checkpoints tighten across the CSP program, expect approval-gated self-service to become the default expectation, not an advanced option.
Growth margin turns what used to be a fixed renewal number into something a partner can actively shape: a few more seats, a new subscription instead of an add-on, a SKU bundled in at the right moment.
The rules go live for production transactions on October 1, 2026, for Direct Bill partners and Distributors, after a sandbox-only preview period that started July 7, 2026. Getting the mechanics right (new subscription versus add-on, lookback windows, renewal timing) means holding several qualifying variables in your head on every deal, and that complexity is unlikely to shrink as Microsoft extends similar incremental margin models across more of the CSP catalog.