EA plus CSP plus MCA in one estate: the contract register, the calendar, and the co termination strategy. Three knowledge checks along the way, and 1 clip from a senior cloud advisor.
The presenter in this session is an AI generated avatar. The curriculum and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. Once in the session the frame splits and a senior cloud advisor gives the view from inside real Oracle negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back, session thirty five of forty, and this closes module seven. We have covered compliance, visibility, shelfware, and the financial view. Today is the structural question underneath all of it, which is how many purchasing vehicles you are running and whether anybody decided that. And I want to be clear from the start that this session is not an argument for consolidation. A blend of vehicles is frequently the cheapest answer, and blended estates that split stable and volatile demand ran eight to fifteen percent cheaper net than all annual estates over a full year. The problem is not that estates have an EA and a CSP agreement and an inherited MCA. The problem is that almost nobody chose that combination. It arrived through acquisitions, mid year purchases, and expired terms, which means nothing is co terminated, nothing is compared, and every renewal is a separate small negotiation with less leverage than one large one would have.
Five takeaways. One, a blend can be right: mixing CSP and EA across workloads is valid and often optimal, and blended estates ran eight to fifteen percent cheaper net than all annual ones. Two, but it is usually inherited, arriving through acquisitions, mid year purchases, and expired terms rather than through a decision. Three, the NCE term trap: annual and multi year NCE terms lock the seat count for the term, and estates that put volatile seats on annual carried ten to eighteen percent they could not release. Four, the window nobody diarises: fewer than one in three buyers had captured the NCE cancellation window in their procurement calendar, and outside it the term is fixed. Five, the register and the calendar: two documents that between them prevent almost every problem in this session, and neither takes more than a morning to produce.
How estates end up with three, and none of these routes are a decision. Acquisitions: you buy a company and inherit whatever they were on, their agreement runs to its own term on its own dates, and integrating it becomes somebody's project competing with every other integration priority for about two years. Mid year purchases: a team needs something the EA does not cover, buys it through a partner, and a second vehicle exists from that day onward, which is individually reasonable and collectively a governance problem. And the steering: sub five hundred seat estates were steered to CSP with EA renewals quietly declined, so a divested or shrinking business unit can find itself on a different vehicle without anybody choosing one. The point is not that multiple vehicles are wrong. It is that an inherited blend has no strategy behind it, so nothing gets co terminated and nothing gets compared.
The contract register, one row per agreement, and five fields per row. Vehicle and entity: which agreement, held by which legal entity, which prevents two business units buying the same thing twice. Term dates: start, end, and the notice window, which prevents the session twenty six failure of discovering a renewal at ninety days. Change window: when seats can be reduced, if at all, which prevents missing the NCE window that most buyers currently miss. Products covered: what sits on this vehicle rather than another, which prevents duplicate entitlement across vehicles. And owner: one named person per agreement, which prevents an agreement renewing simply because nobody owned it. Five fields, and most organisations cannot produce that table today, while the account team on the other side can produce their version of it in minutes. That is the session twenty nine asymmetry appearing in a new place and costing just as much.
First check. You hold an EA and inherit a CSP agreement through an acquisition. What is the first thing to establish? A, how quickly the CSP agreement can be terminated. B, its term dates, change windows, and what products it covers, because until those are known you cannot tell whether consolidating is cheaper than keeping it. C, whether the CSP partner will match your EA pricing. D, how to migrate the users onto your existing tenant. Pause it, and as you think, ask what you would actually need to know before deciding whether to keep the thing at all.
The answer is B, and notice that A, C, and D all quietly assume the answer is consolidation. Consolidation is sometimes right and sometimes not. If the acquired population is volatile, seasonal, or likely to be divested again, a flexible CSP profile may genuinely beat folding it into a three year commitment, and shrinking estates on an EA overpaid by ten to twenty percent against a flexible CSP profile. A also risks discovering the termination question after the change window has already closed, which is the exact failure this session is about. C is a good question asked in the wrong order, because a matched rate on the wrong vehicle is still the wrong vehicle. D is an operational project that may follow the decision and should certainly not precede it. Fill in the register row first: vehicle, entity, dates, windows, products, owner. Then decide, with the facts in front of you.
The NCE term trap, five things about how the terms actually work. The terms are committed: annual and multi year NCE terms lock the seat count for the term, which is the change from the legacy model where seats could move almost any month. Increases are easy and decreases are not: you can add seats at any time, while reductions are only possible inside a short window after purchase or renewal, and after that the term is simply fixed. Monthly costs more, deliberately: monthly term NCE carries a premium over annual, and that premium is the price of being able to flex down, so sometimes it is worth paying and it should be a calculation rather than an instinct. The window is short and unmarked: fewer than one in three buyers had it in their procurement calendar. And the partner sets price and support, with the partner of record being a negotiable lever, which is next session.
Guest analyst The most avoidable problem in this whole area, and I see it constantly, is the New Commerce cancellation window. Let me describe one. A retail group with a large seasonal workforce, and they had done what looked like sensible procurement: moved their CSP estate onto annual terms to capture the discount, which was worth a few points. About eleven thousand seats. What nobody had established was that annual New Commerce terms lock the seat count, and that reductions are only possible inside a short window after purchase or renewal. So in January, when the seasonal population dropped by about three thousand people the way it does every single year, they went to reduce the seats and found they could not. Not because a partner was being difficult, the partner was very helpful about it, but because the term was fixed and the window had closed months earlier. They paid for three thousand unused seats for the remainder of the year. And here is the part that I think is genuinely instructive. When we looked at it afterwards, the annual discount they had captured was worth substantially less than the seats they could not release. So the procurement decision that looked like a saving was a net loss, and it was a net loss that was entirely predictable from a seasonal headcount chart anybody in that business could have drawn from memory. What they do now is very simple. Stable population on annual. Seasonal population on monthly, premium paid deliberately. And every change window is in the procurement calendar with a reminder six weeks ahead of it.
A discount worth less than the seats they could not release, and predictable from their own headcount chart. Second check.
Check two. You have seasonal staff on annual NCE terms and headcount drops after the season. What can you do? A, reduce the seats, since they are no longer needed. B, nothing until the term ends, unless you are inside the change window, which is why volatile populations belong on monthly terms even at a premium. C, move them to the EA instead. D, ask the partner for a credit. Pause it, and as you think, ask which populations in your own estate are genuinely stable across a full year and which are not, because that is the distinction the whole session turns on.
The answer is B. A describes what people expect rather than what the terms permit: annual NCE locks the seat count, and decreases are only available inside the short window after purchase or renewal. This is the single most common surprise in the CSP part of a Microsoft estate, and the story you just heard is the standard version of it. C moves a volatile population onto a three year commitment, which is the same mistake with a longer term attached and is worse rather than better. D is worth asking and rarely succeeds, because the partner is passing through terms rather than setting them, and a partner who grants that credit has funded it out of their own margin. So the lesson here is a planning one rather than a remedy: stable seats on annual, volatile seats on monthly, large stable volume on the EA. Blended estates that split demand that way ran eight to fifteen percent cheaper net over a full year.
The deliberate blend, three populations and three vehicles, where the design follows the volatility of the population rather than the preference of the buyer. Large and stable to the EA: your core knowledge worker population where the count is predictable across three years, and EA price lock saved eight to fifteen percent for estates with rising headcount over the term, which is exactly the population where a lock is worth having. Stable but smaller to annual NCE: populations that are steady but sit outside the EA or below the thresholds where an EA is offered, where annual terms buy the discount and the seat count genuinely will not move. And volatile to monthly: seasonal staff, project teams, contractors, and anything attached to a business that might be divested, where the monthly premium is the price of a right you will actually exercise. This is the session fifteen persona model applied to contracts rather than to plan tiers.
Co termination, and what aligning the dates actually buys you. One negotiation, with everything on the table at once, which is the session twenty nine point that a buyer is strongest with scale. One preparation cycle, a single two hundred and seventy day programme rather than three, which is what makes the session twenty six runway affordable, because most organisations cannot resource that three times a year. Comparable pricing: same basket, same moment, across vehicles, which is what makes the session twenty seven comparison possible at all. Fewer windows to miss, one calendar entry rather than several, addressing that one in three failure rate directly. And a cleaner true up, with aligned anniversaries and no stub periods distorting the session ten arithmetic. Co terming is requested rather than granted, and it must be asked for before signature. It also costs something once, because aligning dates usually creates a stub period somewhere, and that is worth paying to stop paying the coordination cost annually.
Last check. Your estate has an EA, two CSP agreements, and an inherited MCA, all on different dates. What is the first move? A, consolidate everything onto the EA at the next renewal. B, build the register and the calendar first, then decide which to co terminate and which to keep separate deliberately. C, move everything to CSP for flexibility. D, leave it, since each agreement is individually well priced. Pause it, and notice that two of those answers pick a destination before anybody has drawn the map.
The answer is B. A and C both choose a single destination before anybody has established which populations are stable and which are volatile, and each is wrong for at least one population in almost every estate. A also spends the leverage from session twenty eight, because consolidating everything removes the alternative that discount depth actually tracked, which is a real cost that never appears in the consolidation business case. D is the position that lets this persist, and it contains a genuine error worth naming: each agreement being individually well priced says nothing at all about whether the combination is right. Three well priced agreements on three different dates is three small negotiations, three preparation cycles nobody has time to run, and three windows to miss. So build the register, put every date and window in one calendar, then decide deliberately which to co terminate, which to keep separate, and why, in writing.
The governance method, two documents and one habit, and this closes module seven with a smaller ask than most of what came before it. One, the register: one row per agreement covering vehicle, entity, term dates, change window, products covered, and a named owner. A morning's work, and most organisations have never had it in one place. Two, the calendar: every date from that register in one calendar, term ends, notice windows, NCE change windows, true up dates, and Microsoft's thirtieth of June, with owners attached and reminders set well before each rather than on the day. Three, the annual review: once a year against the register, asking whether each population is still on the right vehicle, whether volatility has changed, and what should be co terminated at the next opportunity. Module seven has been about the time between renewals, and it ends with four small artefacts that turn a triennial scramble into a managed position.
Session thirty five, three sentences. One: a blend of vehicles is often optimal and blended estates that split stable and volatile demand ran eight to fifteen percent cheaper net than all annual estates, but most multi vehicle estates are inherited through acquisitions and mid year purchases rather than designed. Two: NCE annual terms lock the seat count and decreases are only possible inside a short window that fewer than one in three buyers had in their calendar, which is why volatile populations belong on monthly terms even at a premium. Three: build the register and the calendar before choosing a destination, because consolidating everything spends the leverage that discount depth actually tracks, and leaving three agreements on three dates is three weak negotiations instead of one strong one. That completes module seven. Module eight is the advanced situations and then the capstone.
Homework, about an hour, and this week you build the register. One, list every agreement: every Microsoft vehicle your organisation holds, including inherited ones and anything a business unit bought directly, and that last category is where the surprises live. Two, fill in the five fields: vehicle and entity, term dates, change window, products covered, owner, and leave blanks visible rather than guessing at them, because a visible blank gets filled and a guess does not. Three, find the NCE windows: for any CSP subscription, when can seats actually be reduced, and most people discover this is not documented anywhere internally. Four, put it all in one calendar, every date with an owner and a reminder set well ahead of it. Five, mark the volatile populations: which groups change size during a term, because those are the ones that should never be on annual commitments.
Five reads before next session, all free on redress compliance dot com. First, the CIO playbook on navigating Microsoft's shift to CSP and NCE, which carries the committed terms, the change window, and the blended estate finding in full. Second, CSP against the Enterprise Agreement, on seat band economics and which populations belong where. Third, the Microsoft EA to MCA renewal guide, for the third vehicle and how it interacts with the other two. Fourth, beyond EA and CSP, on MPSA and other programmes, which is useful for estates that inherit something unusual through an acquisition. And fifth, aligning Microsoft support renewal with EA timing, which is co termination applied to the agreement most often left out of it entirely. Next session opens module eight: CSP economics in depth. Partner margin, price protection, support quality, and how to run a partner selection or a switch without losing continuity. See you there.