White paper · Agreements

EA to MCA E migration.

Microsoft is steering enterprise buyers off the Enterprise Agreement and onto the Microsoft Customer Agreement Enterprise. The move is framed as administrative. It is not. It changes how you are priced, how you commit, and how much protection you carry into the next term. This white paper sets out what actually changes commercially, where the transition creates risk, and how a buyer times and negotiates the move so it lands as a renewal in your favor rather than a quiet reset of terms. A migration is a negotiation. Treat it as one.

Abstract What you will learn Inside this paper The practice Open the paper

Abstract

The Microsoft Customer Agreement Enterprise, the MCA E, is the vehicle Microsoft intends most enterprise customers to sign in place of the Enterprise Agreement. Microsoft presents the transition as a modernization of paper, but the commercial substance shifts in ways that matter to the buyer. Pricing moves from negotiated, locked levels toward a deal desk model. Familiar EA protections such as price holds, true up mechanics, and anniversary structure do not carry across automatically. Subscriptions move to a different billing and commitment model. This paper explains what changes commercially, identifies where the transition introduces risk, and lays out how a buyer secures price protection through the move. Above all it argues that an EA to MCA E migration is a renewal in disguise and should be timed, prepared, and negotiated with the same discipline as any renewal, because the terms a buyer accepts in the migration set the baseline for years.

What you will learn

  • What changes commercially when an Enterprise Agreement becomes a Microsoft Customer Agreement Enterprise, beyond the change of paper.
  • Which EA protections do not carry across and have to be renegotiated rather than assumed.
  • How to secure price protection through the transition so the move is not a quiet uplift.
  • Where the transition creates risk in pricing, in tooling, and in the loss of structure buyers relied on.
  • How to time and sequence the move so it is negotiated as a renewal rather than accepted as an administrative event.

Inside this paper

  • The migration Microsoft wants and the one you should run
  • What actually changes commercially
  • The protections that do not carry across
  • Securing price protection through the move
  • Timing and sequencing the migration

The practice behind it

This paper reflects method developed across hundreds of Microsoft engagements, including EA to MCA E migrations run from the buyer side. The figures below are firm level and cumulative across the practice.

$420M+
in cumulative client savings on Microsoft contracts
340+
Microsoft engagements delivered
79%
average reduction in audit financial exposure
20+
years combined practice experience across Microsoft licensing
Gated white paper · Opens on submit

Open the EA to MCA E migration paper.

Tell us who you are and the full paper opens immediately in your browser. We ask for a corporate identity because the buyer side method inside is shared with practitioners, not crawlers. No sales sequence is attached.

Opens immediately in your browser. Use a corporate email; personal and freemail addresses are not accepted. We do not share your address and there is no sales sequence attached.