Microsoft Enterprise Agreement (EA) Renewal: Managing the 3-Year Cycle & Annual True-Ups

The Three-Year Architecture: Anniversaries, Annual True-Ups, and the Final Expiration Date

For organizations with 500 or more users or devices, the Microsoft Enterprise Agreement (EA) is the foundational procurement vehicle for Microsoft 365, Windows Enterprise, Azure, and on-premises server infrastructure (Server and Cloud Enrollment - SCE). An EA is structured around a rigid 3-year commitment cycle:

• Year 1 Anniversary (T+12 Months): First mandatory True-Up reconciliation and annual payment.
• Year 2 Anniversary (T+24 Months): Second mandatory True-Up reconciliation and annual payment.
• Year 3 Expiration (T+36 Months): Final True-Up reconciliation, contract expiration, and execution of a replacement EA enrollment or transition to a modern licensing agreement.

While an EA provides valuable price protection by locking user licensing rates against inflationary list-price increases across the 3-year term, managing the milestone calendar requires active governance. Failing to prepare for anniversary True-Ups or end-of-term negotiations erodes those financial advantages entirely.

The True-Up Audit: Calculating Actual Qualified Devices and Enterprise Users

The core operating mechanism of an EA is the Annual True-Up. Microsoft permits enterprise customers to deploy additional software licenses and cloud services throughout the year without submitting individual purchase orders each time a new employee is hired.

However, between 30 to 60 days prior to each contract anniversary, the customer must submit an authoritative inventory report detailing all newly deployed qualified devices, enterprise users, and processor cores:

The 60-Day Notice Window: Preventing Evergreen Rollovers into Unfavorable Tiers

As the final Year 3 expiration date approaches, organizations must avoid falling into the default Extension or Bridge Term. Most EA enrollments specify that if a replacement agreement is not executed before the expiration date, services continue under short-term extensions at un-discounted list rates.

Furthermore, Licensing Solution Providers (LSPs)—such as CDW, SHI, Insight, or SoftwareOne—require an approved Bill of Materials (BOM) signed off at least 45 to 60 days prior to expiration to submit discount requests to Microsoft Corp business desk executives. If negotiations drag to the final two weeks of the contract, Microsoft sales leadership loses the ability to push custom concession packages through corporate review.

Transitioning from EA to Cloud Solution Provider (CSP) or MCA-E: Timeline Realities

Many enterprise organizations are migrating away from traditional 3-year EAs toward the Microsoft Customer Agreement (MCA-E) or monthly/annual Cloud Solution Provider (CSP) agreements to gain agility. However, executing this transition requires strict milestone alignment:

1. Azure Subscription Migration: Transitioning active Azure enterprise subscriptions from an EA enrollment to MCA-E requires tenant-level ownership re-binding that must be executed over a scheduled weekend maintenance window.
2. Software Assurance (SA) Preservation: If you own perpetual on-premises server licenses with active SA under your EA, transitioning to CSP without purchasing Software Assurance Step-Up or subscription equivalents forfeits disaster recovery rights and license mobility.

Microsoft EA Milestones and Action Timeline (T-180 to T-0 Days)

Executing an enterprise Microsoft renewal that saves 15% to 25% requires an established runway:

• T-180 Days: Run automated discovery across Entra ID and server infrastructure. Quantify unassigned licenses and downscaling candidates.
• T-120 Days: Engage your LSP to deliver the baseline renewal quote. Solicit competing quotes from alternate LSPs if permissible.
• T-90 Days: Submit concession requests (pricing locks, Azure credits, unified support fee caps) to Microsoft account leadership.
• T-30 Days: Execute the final Order Form and submit the Year 3 final True-Up reconciliation.

Centralizing your Microsoft EA anniversaries, True-Up deadlines, and LSP notice requirements in RenewOS ensures your IT leadership never enters negotiations on the back foot.