What Co-Terming Means in an Enterprise Agreement Context
Co-terming is the process of aligning the end dates of multiple Microsoft agreements — whether separate Enterprise Agreements, add-on enrolments, or product-specific subscription terms — to a single common expiry date. The purpose is administrative simplification, but when executed at a strategically chosen date, it also concentrates your renewal leverage at one commercial moment rather than distributing it across multiple smaller engagements over time.
The mechanics are straightforward in principle and surprisingly complex in practice. Microsoft extends shorter agreements to the target date by charging a pro-rata uplift for the extended period; agreements that expire after the target date may require early termination, usually with a credit or fee depending on the circumstances. Most organisations only encounter co-terming during post-acquisition integration or when attempting to consolidate multiple EAs, but it also occurs at every EA renewal when a customer adds mid-term enrolments that need to align with the anchor agreement's anniversary date.
Done correctly, co-terming is commercially neutral to slightly positive — you pay proportional costs for extended terms and gain the benefit of single-point renewal leverage. Done incorrectly, it creates billing disputes, orphaned Software Assurance benefits, and renewed agreements with misaligned true-up dates that generate compliance exposure. This guide covers both the mechanics and the strategy.
The Pro-Rata Arithmetic
When Microsoft extends an agreement to align its end date with a target date, the cost of the extension is calculated on a monthly pro-rata basis against the annual contract value of the agreement being extended. The formula Microsoft applies is:
Extension Cost = (Annual Contract Value ÷ 12) × Number of Extension Months
Where Annual Contract Value = total annual licence cost of the agreement being extended at current rates
Extension Months = months between the shorter agreement's original end date and the target co-term date
In practice, two complications arise. First, Microsoft's "current rates" may not be the rates on your original agreement — if list prices have increased since signing, the extension calculation may be performed against the new higher rates unless your original agreement contains explicit price protection for extensions. Second, the month calculation is typically performed on a calendar-month basis, but some agreements use a 30-day month convention that produces slightly different numbers. Always confirm the convention in writing before the amendment is drafted.
For a concrete example: an agreement with an annual contract value of £600,000 that needs to be extended by seven months would carry a co-terming cost of £350,000 (£50,000 per month × 7). This is not a discount or a fee — it is simply payment for the additional licence period. The key variable to negotiate is the rate at which this extension is calculated, particularly if price list increases have occurred since the original agreement was signed. Your original agreement's price protection clause governs this; the EA price protection guide explains what standard and negotiated protection clauses actually cover.
Choosing the Right Co-Term Target Date
The choice of target co-term date is a commercial decision, not merely an administrative one. The optimal co-term date should be selected against four criteria: Microsoft's fiscal year end, your internal budget cycle, your organisation's strategic planning horizon, and the combined user count you will present at the shared renewal date.
Aligning with Microsoft's Fiscal Year End
Microsoft's fiscal year ends on 30 June. The final weeks of June — and to a lesser extent December, which marks the mid-year close — represent the period when Microsoft's account teams and their managers have the greatest commercial flexibility to authorise discounts and concessions in order to hit their annual targets. An EA renewal falling in April, May, or June consistently produces better commercial outcomes than an identical renewal in July or August, when Microsoft enters the new fiscal year with reset quotas and reduced urgency. Selecting a co-term target date that places your renewal in Q4 of Microsoft's fiscal year (April–June) is a structural commercial advantage. The end-of-quarter discount guide quantifies this advantage in detail.
Your Internal Budget Cycle
Your EA renewal date needs to land in a window when your finance team can approve a three-year commitment at the required scale. For most organisations, this means aligning the renewal to Q1 or Q2 of your own financial year — after annual budgets have been set and before mid-year freezes. A renewal that falls in your organisation's Q4 budget crunch or during an externally mandated freeze period gives Microsoft unnecessary leverage: time pressure on your side always transfers to their side.
The Combined Volume Consideration
When co-terming multiple agreements ahead of a consolidation, the target date should coincide with a renewal negotiation at which you will present the combined user count as a unified commercial commitment. Co-terming to a date without following it with a consolidation negotiation captures the administrative benefit without capturing the commercial benefit. Sequence the co-terming to precede your planned consolidation discussion by no more than 30–60 days. The EA consolidation guide covers the full consolidation process.
Software Assurance Benefits During Co-Terming
The most common source of material financial loss during co-terming is the mishandling of Software Assurance benefit balances. When an agreement is extended, the SA benefit period should extend proportionally — but Microsoft's VLSC system does not always reflect this automatically. Specific benefits that require manual verification and, in some cases, explicit amendment language to protect:
| SA Benefit | Co-Terming Risk | Required Action |
|---|---|---|
| Planning Services Days | High — often reset or lost | Document balance in VLSC before amendment; require written transfer confirmation |
| Training Vouchers | Medium — expiry date may not extend | Verify expiry date explicitly in amendment language |
| License Mobility Rights | Low — typically carries through | Confirm in amendment for belt-and-braces protection |
| Step-Up Licensing Rights | Medium — depends on extension period | Confirm step-up eligibility is maintained through new end date |
| Spread Payments | High — payment schedule may be disrupted | Require revised payment schedule in writing before signing |
| Home Use Programme | Low — user entitlement based, not date based | Standard review; confirm user count alignment |
The safest position is to extract a complete SA benefits statement from VLSC for every agreement involved in the co-terming before any amendment is signed, then require the amendment to explicitly state that all SA benefit balances are carried forward to the new end date with no reduction. Microsoft will normally agree to this language; the problem is that it is rarely included in the default amendment template. If it is not included, it is not protected. See the Software Assurance guide for the complete benefits framework.
Mid-Term Additions and the Annual Co-Terming Trap
Every time you add licences mid-term on an existing EA, you create a micro co-terming event. Microsoft adds the new licences to your true-up count and charges for the remaining months of the current EA year — a pro-rata charge from the addition date to the anniversary date. This is standard and expected. The trap is when multiple mid-term additions accumulate across a three-year EA and nobody tracks the cumulative effect on the true-up baseline.
By the third year of an EA, an organisation that has made mid-term additions in years one and two may have a significantly different licence baseline than the original agreement documented — and if those additions were entered at the wrong price tier or with incorrect Software Assurance status, the compounded error by year three can be substantial. The true-up clauses explained guide covers how to prevent this accumulation of errors through systematic mid-term tracking.
Using Co-Terming as Negotiation Leverage
Co-terming is most powerful as a leverage mechanism when you time it to place your consolidated renewal at Microsoft's fiscal year end and present a larger combined commitment than you have historically. The approach is to initiate the co-terming conversation with Microsoft's account team framed as administrative simplification — which it is — while simultaneously signalling that the outcome of the co-terming will be a formal renewal negotiation in which you expect improved commercial terms in return for the multi-year commitment.
Microsoft's account teams are measured on agreement renewals and seat retention. An account team that successfully co-terms multiple agreements and consolidates them into a single, growing EA at a target date is a better outcome for them than managing a fragmented portfolio of agreements expiring at different times with the attendant churn risk each one creates. Use their internal incentive explicitly: frame co-terming as a path to a simplified, strategic relationship. Then negotiate the commercial terms of that strategic relationship as part of the co-terming process, not after it. The EA negotiation tactics guide covers how to structure this conversation.
Always request a written co-terming calculation from your Large Account Reseller before signing any amendment. The calculation should show: the original agreement end date, the target co-term date, the number of extension months, the ACV base used for the calculation, the extension cost per month, and the total extension charge. Verify the ACV base against your original agreement. Verify the month count independently. Errors in Microsoft's co-terming calculations are common and rarely discovered unless the customer checks the arithmetic themselves.
Early Termination vs Extension: Which Applies
When an agreement runs longer than the target co-term date, the question becomes whether to early-terminate the longer agreement or accept a period of misalignment until its natural expiry. Microsoft's standard position is that early termination is not permitted on a standard EA without a fee — typically the remaining annual payments owed under the agreement. However, there are two scenarios where early termination without penalty is achievable: where the longer agreement contains a termination-for-convenience clause (rare but negotiable at original signing), and where the longer agreement is associated with a corporate entity being divested.
If early termination carries a cost that exceeds the administrative benefit of alignment, the rational choice is to allow the misalignment and manage the two-agreement structure until the longer agreement expires naturally. The administrative overhead of two agreements is manageable; an early termination fee on a multi-million pound agreement is not. Run the numbers before choosing. Our EA advisory service includes modelling of exactly these scenarios as part of a standard engagement.