When Two EAs Collide: Microsoft After a Deal

When two EAs collide, the buyer inherits one of the most consequential decisions in Microsoft licensing: how to merge two enterprise agreements that were never designed to meet. An enterprise agreement is a three year commitment with its own price levels, product set, anniversary, and true up rhythm, and a merger places two of them side by side with different terms and different renewal dates. When two EAs collide, the combined organisation can pay twice for the same people, lose negotiated discounts, or stumble into an unplanned true up unless the consolidation is measured and sequenced deliberately. Inherited enterprise agreement exposure is usually latent and unquantified in standard due diligence, and it tends to surface at the next true up or renewal once the new owner is known.

This guide explains how to handle two enterprise agreements that meet in a deal and turn the collision into a clean, lower cost combined position. It is a core workstream in post close license reconciliation and a specific case of the broader Microsoft work.

When two EAs collide: what actually breaks

Two enterprise agreements do not simply add together. Each was priced at a volume level that may change when the organisations combine, each carries product selections that overlap, and each has an anniversary and a true up window that will not align. The first thing that breaks is cost visibility, because the combined Microsoft spend is now spread across two contracts with different terms, and nobody owns the total. The second is duplication, because the same people are very likely licensed under both agreements. The third is timing, because a true up on one agreement can fall due before the consolidation is ready, billing growth the buyer would rather have folded into a single renewal. The reconciliation puts both agreements on one timeline and measures the real combined position before any of these breaks costs money.

This is the Microsoft specific edge of a general problem. The same overlap and timing issues appear across publishers, which is why this connects to reconciling Microsoft agreements after a merger and to reconciling overlapping software agreements more broadly.

Choosing the anchor renewal

The central decision when two EAs collide is which agreement to consolidate into and when. One agreement becomes the anchor, the other is allowed to lapse or is co terminated into the anchor, and the timing is chosen to capture the best combined pricing without paying twice or forfeiting value. Consolidating mid term can mean walking away from committed spend or paying an early termination cost, so the reconciliation maps both anniversaries, both true up windows, and both price levels, then identifies the renewal that gives the buyer the most leverage. Getting this sequence right is usually worth more than any single line item negotiation, because it sets the price level and the term for the entire combined estate.

Deduplicating before consolidating

Before two agreements merge, the user picture has to be clean. The same person licensed under both agreements is paid for twice, and leavers from either organisation may still hold assigned licenses. The reconciliation deduplicates users across both agreements and both tenants, strips out the ghosts, and produces the true count of people who need each product. Consolidating before this is done simply carries the duplication into the new agreement and locks the waste in for another three year term. The order matters: measure, deduplicate, then consolidate. The wider mechanics of this sequencing are set out in the post close reconciliation project plan.

Resolving the collision on the buyer terms

Once both agreements are on one timeline and the user picture is clean, the buyer chooses the anchor, the timing, and the target product set, then negotiates the combined renewal from a measured position. Microsoft renewals are commercial events, so a buyer that arrives knowing the combined volume, the overlaps, the better of the two price levels, and the discounts worth carrying forward negotiates from strength. The buyer that lets two agreements drift pays for the privilege twice. Controlling the measurement controls the timing, and with enterprise agreements the timing is the anchor renewal.

What a clean consolidation looks like

A well handled enterprise agreement collision ends in a single agreement, on the better of the two price levels, with a product set rationalised to what the combined organisation actually uses, and a user count free of duplicates and leavers. It is timed to the anchor renewal so no committed spend is forfeited and no true up falls due mid sequence. The negotiated terms worth keeping from either original agreement are carried forward, and the combined volume is used to argue for a better tier where the numbers support it. None of that happens by accident. It happens because both agreements were put on one timeline early, the user picture was cleaned before consolidation, and the renewal was chosen deliberately rather than allowed to arrive.

The contrast is the drift case, where two agreements run on in parallel, each truing up separately, each carrying its own duplicates, until a renewal forces a rushed decision with no measured position behind it. The difference between the two outcomes is planning, and the planning starts the week the deal closes.

Why an independent advisor handles the collision

When two enterprise agreements collide, the buyer faces a publisher whose true up captures growth automatically and whose renewals reward complexity. An independent, buyer side advisor puts both agreements on one timeline, measures the combined position, deduplicates the users, and sequences the consolidation to the renewal that serves the buyer, with no affiliation to Microsoft or any reseller. That independence is what turns a collision into a single clean agreement at a better price rather than two contracts quietly billing twice.

Price levels, volume tiers, and the anniversary trap

When two enterprise agreements collide, the first commercial question is what happens to the price level. Microsoft enterprise agreements set discounting against a volume band, and the combined organisation usually qualifies for a better band than either company held alone. That improvement is only captured if the consolidation is timed to a renewal rather than forced mid term, because merging two agreements before either anniversary can mean paying out the remaining commitments on both while gaining none of the volume benefit. The reconciliation models the combined volume, identifies the band the merged entity should reach, and sequences the move so the buyer enters the renewal with the leverage the larger footprint provides.

The anniversary and true up cycle is the trap that catches unprepared buyers. Each enterprise agreement carries an annual true up where added users and products are reconciled and paid for, and the two agreements rarely share a date. A buyer that consolidates carelessly can trigger a true up on the larger combined count before the deduplication is finished, paying for ghosts and duplicates that should have been removed first. The safe order is to measure, deduplicate, then consolidate, so the true up that does occur reflects the clean position. The same disciplines apply to the wider Microsoft estate covered in reconciling Microsoft agreements after a merger.

Turning the collision into leverage

Two enterprise agreements meeting is a problem, but a measured buyer can turn it into leverage. The combined organisation is a larger account to Microsoft, and a larger account with a clean, quantified position negotiates from strength. The buyer that knows its true combined user count, its overlaps, and its target state can propose the consolidation on its own terms, time it to the renewal that captures the best band, and fold any correction into a single commercial conversation rather than reacting to a true up it did not plan for.

The opposite posture, consolidating in a hurry to simplify the estate, hands the advantage back. Speed without measurement locks duplication into the new agreement for a full term and forfeits the volume benefit the merger should have unlocked. The right sequence is patient by design: measure the combined demand, remove the duplication, then consolidate to the anniversary that pays. That is the same measured approach the buyer applies across every publisher in the estate.