NCE rewired how Microsoft seats are bought, locked, and reduced. Here is how the terms work, where the commitment bites, and the term mix that protects your budget.
The New Commerce Experience replaced the old CSP model and rewired how Microsoft seats are bought, locked, and reduced. The term you pick now drives a year of cost.
This pillar is for procurement leads, license managers, and IT finance teams buying Microsoft 365 through the New Commerce Experience. Read it with the Microsoft Enterprise Agreement guide and the Microsoft pillar hub.
NCE looks like a packaging change. It is really a commitment change. The platform pushes longer locks in exchange for a discount, and the discount is small next to the flexibility you give up.
The New Commerce Experience is the buying framework Microsoft uses for cloud subscriptions sold through partners. It replaced the legacy CSP program and standardized terms, price locks, and cancellation rules across the seat base.
Most per user cloud subscriptions sit inside NCE. That covers Microsoft 365, Dynamics 365, and Power Platform seats bought through a partner. The Microsoft partner documentation on license based subscriptions sets the rules each seat follows.
An Enterprise Agreement is a direct Microsoft contract for large estates. NCE is the partner channel path, often better for mid sized buyers. The two can coexist, and many estates split seats between them.
NCE offers monthly, annual, and three year terms. The term decides your price and your flexibility. Most buyers default to annual without modelling the cost of being locked.
A monthly term can be cancelled or reduced each month at a higher unit price. An annual term locks both price and quantity for twelve months. A three year term locks price for the full period.
Stable headcount belongs on annual or three year terms for the discount. Volatile or seasonal roles belong on monthly terms. Splitting the base captures the discount where it is safe and keeps flexibility where it matters.
NCE term options compared
| Term | Relative price | Mid term reduction | Best for |
|---|---|---|---|
| Monthly | Highest | Any month | Volatile or seasonal roles |
| Annual | Lower | Only within 7 days | Stable core headcount |
| Three year | Lowest | None | Locked long term headcount |
A term lock fixes your unit price for the life of that term. With Microsoft list prices rising across several cloud SKUs, the lock has become a planning tool rather than a constraint. The Microsoft 365 plans and pricing page shows the current list positions.
A three year lock pays off when you expect list prices to rise and your headcount to hold. It hurts when headcount falls, because you keep paying for seats you no longer use.
Renewing just before an announced increase locks the lower price for the whole term. Watching the Microsoft pricing calendar and timing the renewal is a no cost lever that buyers routinely miss.
The standard partner pitch is that the three year term is the smart default because it locks the lowest price. We disagree.
In roughly 4 out of 5 Microsoft estates we benchmarked, headcount moved enough over three years that the lock cost more than it saved through idle seats.
The buyer side move is to lock only the stable headcount floor on a long term and keep the volatile band on monthly. A discount on seats you stop using is not a saving.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
NCE looks like a packaging change. It is really a commitment change, and the discount is small next to the flexibility you trade away.
This is where NCE bites. Once an annual or three year term is past the cancellation window, you cannot reduce the seat count until renewal. The commitment is firm.
Microsoft allows a cancellation or reduction within seven calendar days of the start of an annual term, with a prorated refund. After day seven the quantity is locked for the term.
Locking more annual seats than you need converts flexibility into a fixed cost. A layoff or a project ending leaves you paying for idle seats until renewal, which is the most common NCE overspend we see.
The levers are term mix, timing, and a true count of real demand. None require Microsoft approval, and all are easiest to pull before the order is placed.
Pull active usage data per SKU before committing. Seats that have not signed in for ninety days are reduction candidates. Buy the annual term to the floor of stable demand, not the ceiling of headcount.
Partners set their own margin inside the NCE price. Putting the seat base out to two or three partners at renewal surfaces the margin difference and is one of the few price levers NCE still leaves open.
The New Commerce Experience is Microsoft's standardized framework for buying cloud subscriptions through partners. It replaced the legacy CSP model and fixes the term, price lock, and cancellation rules for Microsoft 365, Dynamics 365, and Power Platform seats.
No, not after the seven day cancellation window. An annual term locks the seat quantity for twelve months. You can add seats at any time, but you cannot reduce the count until the term renews.
The monthly term costs roughly 20 percent more per seat than the annual term. You pay that premium for full flexibility to cancel or reduce seats each month, which suits volatile or seasonal roles.
Microsoft allows a cancellation or seat reduction within seven calendar days of an annual term starting, with a prorated refund. After day seven the quantity is firm for the rest of the term.
A three year term gives the lowest price and the longest lock. It pays off when list prices rise and headcount holds, but it hurts if headcount falls, because you keep paying for idle seats until renewal.
Yes, and most buyers should. Put stable core headcount on annual or three year terms for the discount, and put volatile or seasonal roles on monthly terms to keep the right to reduce them.
No, the two can coexist. The Enterprise Agreement is a direct Microsoft contract suited to large estates, while NCE is the partner channel path. Many organizations split seats between the two models.
Baseline real seat demand from active usage data before committing. Buy the annual term to the floor of stable demand rather than the ceiling of headcount, and keep volatile roles on monthly terms.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The annual term discount looks attractive until a layoff leaves you paying for idle seats for nine more months.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
NCE term moves, EA renewal levers, and Copilot pricing reality. No noise.
