A working Microsoft true-up timing strategy recognises four windows where adding licences costs less than the default anniversary path: pre-anniversary scoping at T-150, mid-year RFQ refresh at month 6, anniversary-month consolidation, and post-anniversary first-quarter additions through the EA pricing schedule. The wrong window is the last 60 days before anniversary, where rushed additions land at retail-adjacent pricing with full-year prorating. The 2026 amplifiers — July price increase, EA tier collapse, Agent 365 tier mix — sharpen the cost difference between the right and wrong window to 18 to 32 percent of the year's added-licence spend. The companion true-up calculator framework is the six-input pre-modelled position.
The starting fact about Microsoft true-up timing: when a licence is added inside the anniversary year materially changes how the licence is priced, prorated, and reconciled against the EA pricing schedule. The default seller-side framing is that true-up timing does not matter and the buyer pays at anniversary regardless. The buyer-side reality is the opposite: timing carries 18 to 32 percent of the cost on a typical mid-cycle licence addition, and the timing decision is made by the buyer's licence-management lead, not Microsoft. This article walks the four windows where adding licences costs less, the wrong window to avoid, and the 2026 amplifiers that shift the math.
The four Microsoft true-up timing windows that lower cost
Four windows recur across active 2024 through 2026 buyer-side advisory work. Each window has a structural reason it costs less than the default anniversary path. The windows are not mutually exclusive; large organisations use two or three in a single year depending on the licence family.
Add the anniversary's full additions inside the EA scope at T-150
The most overlooked window. At T-150 (five months before anniversary) the buyer-side team runs a deployment-count reconciliation against the EA scope and identifies the SKUs that will end the year above entitlement. Those SKUs are added inside the EA at the negotiated pricing schedule, prorated to a clean five-month window. The pricing is the schedule rate; the prorating is documented at the addition date; the reconciliation at anniversary is a confirmation, not a discovery. Many organisations dismiss this window because the licences are not yet needed; the math says the discipline is worth running because the alternative is retail-adjacent pricing at anniversary.
When: 5 months before anniversaryRefresh the EA pricing schedule at month 6 with new-SKU pricing
EA pricing schedules age over the three-year term; mid-cycle, the schedule lacks pricing for SKUs Microsoft launched after signing. Without a refresh, the seller-side default true-up pricing for those new SKUs is retail. The mid-year RFQ refresh adds the new-SKU pricing to the schedule through an amendment; subsequent additions inside the year land at the refreshed schedule. The most material 2026 examples are M365 E7, Agent 365 Standard / Pro / Enterprise, Copilot Studio CCCU / ACU, and Fabric F-series capacities. See the EA amendment request article for the amendment mechanics.
When: Month 6 of each EA yearConsolidate the year's drift additions into the anniversary order with one negotiation
For organisations whose deployment counts drift continuously through the year, the consolidation window at the anniversary itself can compress the negotiation calendar without losing pricing discipline. The buyer-side team runs the full pre-modelled position at T-120 and adds the year's drift inside a single anniversary order using the pricing schedule and full prorating against each SKU's deployment activation date. The negotiation runs once instead of per addition; the deal team is in the room once instead of monthly. This window works best when the buyer's licence-management discipline is mature enough to track deployment activation dates accurately.
When: T-90 to anniversaryAdd the new year's first-quarter additions immediately after anniversary
The cleanest window for new-year additions. Immediately after anniversary, the EA pricing schedule resets to the new-year baseline and the next anniversary clock starts at T-365. Additions in the first 90 days carry full-year prorating against the new anniversary, the pricing schedule is fresh, and the seller-side close-cycle pressure is low so concessions are easier to extract. This is the cleanest window for predictable headcount growth like an acquisition close, a planned new-product launch, or the first quarter of a new fiscal year.
When: First 90 days after anniversaryThe wrong Microsoft true-up timing window: last 60 days before anniversary
The single worst window for adding licences is the last 60 days before anniversary. Three structural reasons. First, seller-side close-cycle pressure is high so the seller's flexibility on pricing rebuttals collapses; the seller wants to land the anniversary settlement quickly and reserves concessions for renewal not for in-year additions. Second, the deployment activation date for an addition in the last 60 days carries minimal prorating value (10 to 17 percent of the year) and the seller-side default reverts to full-year framing. Third, the time pressure on the buyer-side licence-management team means the pricing rebuttal and SA-offset application moves run short of their normal discipline. The reduction the buyer would otherwise extract collapses by 40 to 60 percent against the same addition made in Window 1 or Window 4. The discipline is to add the licences early or to wait two months.
The wrong-window rule has one exception: a regulatory or contractual deployment that cannot wait. A FedRAMP authorisation deadline, an M&A close inside the anniversary month, or a contractual customer-facing launch can justify the wrong-window addition. The buyer-side discipline is to document the regulatory or contractual driver, to bring the documentation to the seller-side conversation, and to anchor the pricing rebuttal to the contractual exception language in the EA itself.
Microsoft true-up timing comparison: cost by window
The table below compares the cost-per-SKU for a representative addition (1,000 seats of M365 E5 at negotiated $54 per seat per month) by window. The opening price is the same; the differences are in prorating treatment, pricing-schedule alignment, and the size of the buyer-side reduction the seller-side counter typically accepts.
| Window | Pricing anchor | Prorating | Net cost / 1,000 seats | Notes |
|---|---|---|---|---|
| Window 1 · T-150 pre-anniversary | Negotiated EA schedule | 5 months prorated | $270,000 | Clean addition; reconciliation is confirmation only |
| Window 2 · Mid-year RFQ refresh | Refreshed schedule + amendment | Per activation date | $285,000 | Carries amendment value into renewal as well |
| Window 3 · Anniversary consolidation | Negotiated schedule + pre-model | Per activation date | $324,000 | Compressed calendar; needs mature LM discipline |
| Window 4 · Post-anniversary Q1 | Fresh-year schedule | Full year on new clock | $648,000 | Higher absolute cost but full new-year value capture |
| Wrong window · T-60 to anniversary | Retail-adjacent | Full-year default | $810,000 | Wrong window; 25-50% premium vs the four right windows |
Anniversary in the next 150 days? The Window-1 discipline lands the savings before the seller anchors.
30-minute scoping call. Active 2024–2026 true-up timing practice.
2026 amplifiers that shift the timing math
Four 2026 inflection points make the timing windows more material than they were pre-2026.
- July 2026 price increase. Additions in the months before July 2026 lock pre-increase pricing through the price-hold clause; additions after July 2026 face the higher list. The single highest-impact timing decision in 2026 is whether to pull pre-July anniversary additions forward into Window 1 or Window 2 to capture pre-increase pricing. The pull-forward is worth 8 to 15 percent on each pre-July addition relative to the same SKU added post-July. See the July 2026 pricing pillar.
- EA tier collapse. The collapse of the A/B/C/D banding shifts the pricing-schedule structure for 2026 anniversaries; refreshes through Window 2 should re-anchor to the post-collapse tier framework. See the EA tier collapse pillar.
- Agent 365 tier mix. Agent 365 Standard / Pro / Enterprise was not on most EA pricing schedules signed before 2026. Window 2 mid-year refresh is the cleanest way to bring Agent 365 pricing onto the schedule before the year-one true-up. See the Agent 365 article.
- E7 Frontier Suite. E7 step-up from E5 is a new SKU family in 2026 and the step-up pricing varies by buyer. The Window-4 post-anniversary addition is the cleanest time to add E7 because the schedule is fresh and the step-up math runs against the new-year E5 baseline. See the E7 article.
The buyer-side Microsoft true-up timing calendar
The annual calendar below condenses the four windows into a single recurring discipline. The discipline runs quarterly with two larger touchpoints (T-150 and post-anniversary).
- Post-anniversary · Days 1 to 30. Reset the EA pricing schedule baseline. Confirm price-hold clause language. Identify the year's planned major additions (acquisitions, product launches, regulatory deployments). Add Window-4 additions for the first quarter.
- Quarter 2 · Months 4 to 6. Run Window-2 mid-year RFQ refresh. Negotiate the amendment for new-SKU pricing additions to the schedule. The most material 2026 refresh items are Agent 365 tier mix, Copilot Studio CCCU / ACU, E7 step-up, and Fabric F-series capacities.
- Quarter 3 · Months 7 to 8. Quarterly deployment-count reconciliation. Identify which SKUs are tracking above entitlement. Build the Window-1 pre-anniversary scoping plan for the end-of-year additions.
- Pre-anniversary · Month 7 onwards (T-150). Run Window 1. Add the anniversary year's planned additions inside the EA scope. Document each addition's activation date for prorating. Reconcile the EA pricing schedule against the latest amendments.
- Anniversary · T-90 to T-0. Run the pre-modelled true-up position using the six-input framework. Apply the nine moves from the reduction playbook. Avoid the wrong window for net-new additions; reserve the last 60 days for reconciliation and settlement only.
The single discipline that compresses the year's added-licence spend is the quarterly deployment-count reconciliation. Organisations that run a quarterly review surface deployment drift early enough to feed the Window-1 and Window-2 additions; organisations that wait for anniversary discover drift in the wrong window. The cost of quarterly reconciliation is one analyst day per quarter; the value is 15 to 30 percent of the year's added-licence spend depending on the SKU mix. The cost is recovered ten to twenty times over in any year with meaningful deployment growth.
The Microsoft Negotiations briefing
Monthly. True-up timing, audit defence, EA negotiation, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the true-up timing discipline next
The timing discipline pairs with the broader true-up framework. The true-up calculator framework is the six-input pre-modelled position; the true-up reduction playbook walks the nine buyer-side moves; the true-up leverage article walks the seven seller-side moves; the true-up risk assessment tool is the 10-question scorecard; the true-up defence service is the productised engagement. For organisations approaching anniversary, the scoping call is the direct engagement channel; for organisations in active EA renewal cycles, the free EA assessment is the broader scoping channel. The EA negotiation pillar connects timing discipline to the renewal-cycle defence.