Reconciling Microsoft Agreements After a Merger

Reconciling Microsoft agreements after a merger is a workstream that looks administrative and turns out to be expensive, because Microsoft licensing spans enterprise agreements, cloud subscriptions, server and cloud enrolments, and per user and per device metrics that consolidation routinely disturbs. When two companies combine, they almost always arrive with two separate Microsoft estates, two enterprise agreements on different anniversaries, two tenants, and overlapping subscriptions for the same people. Reconciling Microsoft agreements after a merger means building one accurate combined position, measuring it the way Microsoft measures it, and resolving the overlaps and gaps on the buyer timetable rather than at the next true up. Inherited Microsoft exposure is usually latent and unquantified in standard due diligence, and it tends to surface at the annual true up or as an audit once the new owner is known.

This guide explains how to reconcile two Microsoft estates into one controlled position. It is a core workstream in post close license reconciliation and sits beside the equivalent work for the other major publishers.

Reconciling Microsoft agreements after a merger: the metrics that bite

Microsoft licensing carries several metrics that move when an estate changes shape. Per user subscriptions such as Microsoft 365 are easy to double count when the same person exists in two tenants. Server licensing measured by core counts can expand as workloads consolidate onto larger hardware, and the rules for license mobility and the cloud differ by product. Client access licensing, where it still applies, depends on the number of users or devices reaching a server. The reconciliation reads each agreement and enrolment literally and counts the combined deployment to Microsoft exact definitions, because the annual true up will do exactly that.

The discipline mirrors the work for other publishers. The specific problem of two enterprise agreements meeting is large enough to deserve its own treatment, set out in when two EAs collide. The common thread across all of them is that publisher counting logic, not intuition, governs the exposure.

Overlapping subscriptions, the quiet drain

The most common Microsoft finding after a merger is not a shortfall but waste. Both companies licensed the same people, often at premium tiers, and the combined organisation keeps paying twice until someone reconciles. Subscriptions assigned to leavers, duplicate Microsoft 365 licenses for the same individual across two tenants, and premium add ons nobody uses all sit on the bill. Reconciling these recovers real money, and the recovery often funds the rest of the integration. The reconciliation matches every assigned subscription to a real, current person in the combined organisation and strips out the duplicates and the ghosts before the next renewal locks the spend in.

Server and cloud licensing pull in the other direction. Consolidating data centres or moving workloads to the cloud can change the core count and the license mobility position, and a decision made for infrastructure reasons can move the Microsoft number either way. The reconciliation assesses each consolidation decision for its licensing consequence before it is made, so the buyer captures the subscription savings without walking into a server shortfall.

Timing the consolidation to the renewal

The single most valuable decision in Microsoft reconciliation is when to consolidate. Two enterprise agreements rarely share an anniversary, and trying to merge them mid term can forfeit value or trigger early termination costs. The reconciliation maps both agreement timelines, the renewal dates, and the true up windows, then sequences the consolidation to the moment that captures the best combined pricing without paying twice. This is where a measured position pays for itself, because the buyer enters the renewal conversation with Microsoft already knowing the combined volume, the overlaps, and the target state. The broader sequencing of this work is set out in the post close reconciliation project plan.

Resolving the position on the buyer terms

Once the combined position is measured, the buyer chooses the resolution. The options include consolidating to a single enterprise agreement at the right renewal, rationalising subscription tiers to what people actually use, deduplicating tenants, and negotiating combined volume pricing from a position of knowledge. Microsoft renewals are commercial events, so a buyer that arrives with a measured position and a clear target negotiates very differently from one that lets two agreements drift. The buyer that controls the measurement controls the timing, and with Microsoft the timing is the renewal. This connects to the wider question of reconciling overlapping software agreements across every publisher.

Where the savings actually come from

The recovered spend in a Microsoft reconciliation tends to come from a small number of large sources rather than many small ones. Duplicate Microsoft 365 subscriptions for the same person across two tenants are usually the biggest single line, followed by premium tier licenses assigned to people who use only standard features, then subscriptions still billing for leavers, then redundant add ons that overlap with capabilities already included in a higher tier. Quantifying each source separately lets the buyer attack the largest first and fund the rest of the integration from the early wins. The reconciliation produces that breakdown rather than a single blended number, because a blended number hides where the action is.

Server and cloud licensing is the counterweight that has to be checked before the savings are banked. A subscription saving that triggers a server shortfall when workloads consolidate is not a saving at all. The reconciliation nets the two so the buyer sees the true combined effect of every consolidation decision.

Why an independent advisor reconciles Microsoft

Reconciling Microsoft puts a buyer against a publisher whose commercial model rewards complexity and whose true up captures growth automatically. An independent, buyer side advisor builds the combined position across both estates, strips out the overlap, sequences the consolidation to the right renewal, and negotiates from a measured number with no affiliation to Microsoft or any reseller. That independence is what turns a Microsoft reconciliation into recovered spend and a clean combined agreement rather than a true up surprise.

Reconciling Microsoft across cloud and on premises

A merged Microsoft estate almost always spans two tenants, two sets of Microsoft 365 subscriptions, and a layer of on premises server licensing that each company bought under different terms. Reconciling Microsoft agreements after a merger means resolving all three layers at once. On the cloud side the buyer counts assigned licenses against active users in both tenants, strips the duplicates and the leavers, and identifies subscriptions that overlap so the combined renewal reflects real demand rather than two inherited baselines added together. On the server side the buyer checks core based licensing for SQL Server and Windows Server against the deployment that consolidation creates, because moving workloads onto shared infrastructure can change the core count that drives the bill.

Software Assurance and the timing of true up are where value leaks. A company that lets Software Assurance lapse loses upgrade rights and the ability to spread payments, so the reconciliation checks the coverage status of both estates before any renewal is signed. The combined position also changes the volume tier the buyer qualifies for, and a larger footprint can pull better pricing if the consolidation is sequenced to the right anniversary rather than rushed. The detail of two enterprise agreements meeting is set out in when two EAs collide, and the order of the whole workstream sits inside the post close reconciliation project plan.

What a clean Microsoft position looks like

A reconciled Microsoft position is one the buyer can defend on demand. Every assigned Microsoft 365 license maps to an active, named user with no duplicates carried across the two tenants and no leavers still holding seats. Every server product is counted against the deployment that consolidation actually produced, with the core counts current rather than inherited. Software Assurance status is known for both estates, and the combined volume sits in the band that the merged footprint qualifies for rather than two separate baselines stacked on top of each other.

Reaching that state is the work, and holding it is the harder part. Microsoft estates drift quickly as users are added, products are switched on, and infrastructure moves, so the reconciled position needs an owner and a cadence to stay clean. The buyer that builds the position once and then governs it avoids paying for the same reconciliation again at the next renewal, which is the outcome the wider plan in the post close reconciliation project plan is designed to protect.