Microsoft CSP, on your terms. Partner economics, NCE shape, and the EA migration math.

CSP is sold as flexibility. Read the contract and it is the opposite. This guide gives the buyer side framework that keeps Microsoft and the partner honest across the term.

The Microsoft CSP channel is sold to enterprises as a flexible alternative to the Enterprise Agreement. Read the contract and CSP is the opposite. It carries a three year New Commerce Experience lock, a zero percent mid term reduction rule, and a tight twenty percent annual cap on quantity changes.

This guide covers what CSP actually means for the buyer side, what the partner makes on the bill, and the procurement framework that keeps Microsoft and the partner honest. Read alongside the Microsoft advisory practice, the Microsoft knowledge hub, and the NCE and CSP hub for the broader context.

The CSP model

Three commercial roles

• Customer. Holds the use right. Pays the partner, not Microsoft directly.
• Indirect provider. Distributor between Microsoft and the partner.
• Indirect reseller. The partner that owns the customer relationship.

NCE shape

The New Commerce Experience locks term, billing cadence, and quantity. The default term is one year with quantity reduction allowed only at renewal. Three year terms unlock deeper discounts and lock the quantity for the full term.

Partner economics

Margin bands

Partners earn between four and twenty percent of the customer invoice depending on workload, segment, and incentive program. The number is invisible by default. The buyer side move is to ask for it openly.

Microsoft partner incentives

• Modern Workplace. Highest incentive tier on M365 family.
• Azure consumption. Lower margin but bigger absolute number.
• Security workloads. Premium incentive on Defender and Sentinel.
• Copilot family. Active recruitment incentives in 2026.

CSP rigidity

Zero mid term reduction

The most cited CSP risk is the zero mid term reduction rule on NCE. Quantities cannot drop inside the term, regardless of headcount change, divestiture, or seasonality.

Twenty percent cap

The annual cap rule allows up to twenty percent quantity changes at anniversary. Beyond the cap the change requires partner approval and Microsoft acknowledgment.

Procurement framework

Questions to ask the partner

• What is the partner margin on each line of this proposal?
• Which incentive programs apply to the SKUs in scope?
• What is the price difference between one and three year NCE term?
• Is the proposal benchmarked against the published Microsoft Customer Agreement rate?
• How are co term changes priced through the term?
• What is the dispute pathway if Microsoft changes the rate inside the term?

When CSP is the right answer

CSP is the right answer for shape that is not stable enough to commit through EA. It is also the right answer for mid market segments below the EA threshold.

For large estates with stable shape, EA almost always wins on price and on contractual flexibility. Read the CSP vs EA comparison for the decision framework.

What to do next

1. Inventory all Microsoft SKUs in scope and classify between EA and CSP today.
2. Ask the partner for the proposal margin on each line and for the applicable incentive programs.
3. Benchmark the proposed rate against published Microsoft Customer Agreement rates.
4. Confirm the NCE term and quantity for each SKU. Calendar the anniversary dates.
5. Stress test the proposal against a twenty percent quantity drop scenario.
6. Govern co terming across SKUs to one or two anniversary windows.
7. Document the dispute pathway for mid term rate changes.
8. Brief the Microsoft advisory practice and run the proposal through a buyer side review.

Frequently asked questions

Is CSP cheaper than EA?

For stable shape, EA is usually cheaper at scale. CSP carries partner margin on every line. The break even depends on volume, segment, and the partner incentive stack.

Can we reduce CSP quantities mid term?

No. NCE locks quantity for the term. Reductions happen only at anniversary and are capped at twenty percent on the renewal year.

What happens if our headcount drops mid term?

The CSP bill stays the same until the next anniversary. The buyer side mitigation is to size shorter terms or to absorb the risk through a Flex pool where available.

Is the partner margin negotiable?

Yes. Ask. Many partners will reduce margin to win or hold a customer, especially on Azure workloads where the absolute number is larger.

Does CSP protect us from a Microsoft audit?

No. The audit pathway is identical to EA. The partner facilitates the audit. The contractual exposure sits with the customer.

Can we run EA and CSP at the same time?

Yes. Many estates run a mixed model. EA for stable shape, CSP for new or volatile workloads, MCA for cloud first segments.

Should we migrate from EA to CSP at the next renewal?

Only if the shape is unstable and the partner offers a credible value above the margin they charge. For most large estates the answer is no.