Microsoft Licensing for M&A Post-Close Operations: Complete Integration Guide

Microsoft licensing is consistently among the top three unplanned cost items in post-M&A integration. In our work with 500+ enterprise clients, we have seen mid-market acquisitions carry $280,000–$2,400,000 in unidentified Microsoft licence exposure that was not surfaced in due diligence. SQL Server miscounting alone — the single largest source — creates seven-figure liabilities in acquisitions of organisations with large data centre footprints. This guide covers the post-close operations framework that eliminates those surprises and turns M&A integration into a Microsoft cost reduction event rather than a cost overrun.

Day 1 Through Day 90: The Critical Post-Close Window

The first 90 days after close are the highest-risk period for Microsoft licensing compliance. The acquired entity's IT team is managing two priorities simultaneously: business continuity and integration. Licence compliance typically falls to third priority — meaning licence exposure can accumulate rapidly while IT leadership attention is elsewhere.

Day 1 Priorities

On day 1, three licence-related actions must be taken before anything else:

• Freeze new Microsoft licence purchases. The acquired entity's IT team should make no new Microsoft purchases — licences, subscriptions, add-ons — without acquirer procurement approval. Rogue purchases on the acquired entity's agreements create commitments that may conflict with the integration strategy.
• Document existing agreements. Obtain from the acquired entity's IT team: all Microsoft agreement numbers, agreement types (EA, Open, CSP), anniversary dates, and the name of the Microsoft account manager. This takes 2–4 hours and is the foundation for every subsequent decision.
• Identify imminent true-up or renewal dates. Any EA anniversary date within 90 days of close requires immediate attention. A true-up obligation falling within 90 days of close can represent an unexpected cash cost of $50,000–$500,000 for a mid-market acquisition. This must be funded and managed as an integration cost item from day 1.

Days 1–30: Compliance Baseline

Deploy discovery tools (MECM, Snow Software, or equivalent) into the acquired entity's environment and run an initial inventory scan. Do not wait for the IT integration workstream to include the acquired entity in the SAM programme — run a standalone scan immediately. The baseline output should include: all installed Microsoft server products (SQL Server by version and edition, Windows Server by version), all M365 user licences by tier, and all developer tool subscriptions.

Cross-reference this inventory against the agreements documented on day 1. Identify products installed that are not covered by any agreement — these are immediate compliance exposures. For SQL Server, follow the product use rights interpretation guide to correctly assess virtualisation-related exposure before drawing any conclusions.

Days 31–90: Remediation and Stabilisation

Any compliance exposures identified in the baseline must be remediated or formally acknowledged as accepted risk before day 90. Remediation options are: purchase additional licences through the acquired entity's existing agreement (note: this may accelerate the true-up), harvest and reassign excess licences from identified surpluses, or migrate workloads to platforms with existing licence coverage. For the reconciliation automation approach that accelerates this work, see the dedicated guide.

EA Integration: The Four Structural Options

Once the compliance baseline is established, the integration team must decide how to structure the combined entity's Microsoft agreements. There are four structural options, each with different commercial implications.

Option	Structure	Best For	Key Risk	Timeline
Run to expiry, then consolidate	Both EAs continue independently until the first expiry date, then fold into acquirer's EA	Target EA expiry within 18 months; clean separation of entities during integration	Duplicate licence spend during overlap period	0–18 months
Affiliate amendment (acquirer EA)	Acquired entity added as affiliate to acquirer's EA; covered by acquirer's pricing and SA	Acquirer has advantageous pricing; target entity fully integrated quickly	Requires Microsoft approval; may trigger true-up on acquirer's EA	30–60 days for amendment
Affiliate amendment (target EA)	Acquirer's entities added as affiliates to target's EA if target has better pricing	Target has better per-seat pricing or more favourable terms than acquirer	Unusual structure; Microsoft may push back	60–90 days for amendment
New combined EA	Both entities exit existing EAs and sign a new combined EA with revised commercial terms	Both existing EAs near expiry; combined entity qualifies for significantly better volume tier pricing	Most complex; requires early termination of existing EAs; Microsoft involvement mandatory	90–180 days

Choosing the Right Structure

The affiliate amendment approach is the most common for acquisitions where the acquirer has an active EA with at least 12 months remaining. The commercial test is straightforward: compare the acquirer's effective per-unit price for key products (M365 E3/E5, SQL Server, Windows Server) against the target's agreement pricing. If the acquirer's price is lower (which is typical for larger organisations), bring the target under the acquirer's EA as an affiliate immediately.

The "new combined EA" option, while complex, delivers the largest commercial benefit when both entities are near renewal. The combined headcount creates pricing leverage that neither entity achieves independently. A combined 8,000-user organisation created by an acquisition of a 3,000-user target (5,000-user acquirer) may qualify for pricing tier breaks that reduce effective per-seat cost by 12–18%. For the negotiation strategy around these tier breaks, see the EA negotiation advanced guide.

Divestiture: Licensing When Selling a Business Unit

Divestitures create a mirror-image challenge to acquisitions. When selling a business unit, you must ensure that the divested entity can operate independently after separation — which means it needs its own Microsoft agreements, its own licences, and its own VLSC access.

The Divestiture Licence Allocation Problem

Enterprise Agreement licences cannot be divided. An EA is a single agreement covering the total qualifying entity — you cannot carve out a portion of an EA and transfer it to a divested entity. The divested entity must either: (a) purchase new licences under its own agreement post-close, (b) negotiate a TSA (Transition Services Agreement) under which the parent provides licensed software for a defined transition period (typically 12–24 months), or (c) immediately qualify for its own EA at close (requires minimum 250 users/devices).

Perpetual Licence Allocation in Divestitures

Unlike subscription licences, perpetual licences acquired under an EA can be permanently assigned to a divested entity — subject to Microsoft's licence transfer rules. The process requires a formal licence transfer request to Microsoft. For the detailed rules on what can and cannot be transferred, see the licence transfer and assignment rules guide.

Common M&A Microsoft Licensing Findings and Valuations

Finding Type	Frequency in Acquisitions	Typical Exposure Range	Remediation Cost
SQL Server unlicensed VMs on VMware	Very common (67%)	$280K–$2.4M	High — requires re-licensing or workload restructuring
Windows Server Standard over-licensing	Common (48%)	$40K–$380K surplus (recoverable at renewal)	Low — optimisation at EA restructuring
Expired SA on perpetual licences	Very common (71%)	Cost to renew: $50K–$800K	Medium — SA reinstatement fees apply
Ghost M365 licences (>5%)	Common (54%)	$30K–$250K annual waste	Low — harvest and deprovision
Unlicensed Azure deployments (AHUB not applied)	Very common (62%)	$20K–$200K annual overspend	Low — AHUB toggle in Azure portal
CSP auto-renewal commitments	Moderate (34%)	$15K–$120K annual obligation	Medium — requires CSP renegotiation or cancellation penalties
Developer licence personal accounts	Common (41%)	$10K–$80K non-transferable value	Low — transfer to organisational accounts post-close

Integration with the SAM Programme

Post-M&A licence normalisation is most effective when it is built into a formal SAM programme from the outset. The acquired entity's licence estate should be onboarded to the acquirer's SAM platform within 90 days — even as a separate "subsidiary" scope — to ensure continuous visibility and reconciliation coverage.

For the full SAM programme framework, including how to structure subsidiary onboarding, see the SAM programme implementation guide. For the documentation required to manage VLSC entitlements through the integration process, see the VLSC administration guide. For the licence mobility provisions that may be affected by the acquisition, see the licence mobility documentation guide.

Frequently Asked Questions

What happens to a target company's Microsoft EA when an acquisition closes?

The target's EA does not automatically transfer to the acquiring company. The target's EA continues independently until its expiry date. Change of control provisions in the EA may give Microsoft the right to terminate — though in practice Microsoft rarely exercises this right, preferring to negotiate a commercial path forward. The typical outcome is: the target's EA runs to expiry, then licences are folded into the acquirer's EA at the next renewal cycle.

How long do we have to integrate a target company's Microsoft licensing post-close?

There is no hard Microsoft-mandated deadline for EA integration, but practical timelines are driven by the target's EA anniversary date and the acquirer's EA renewal date. Most integration programmes target 18–24 months for full EA consolidation. Compliance-critical items should be completed within 90 days of close.

Can we use the acquirer's Microsoft EA licences for the target company immediately after close?

Generally no, without formal amendment. Microsoft EA licences are bound to the legal entity named in the agreement. Using acquirer EA licences for a newly acquired entity typically requires a formal amendment to add the acquired entity as an affiliate, which takes 30–60 days.

What Microsoft licensing risks are most commonly found in M&A due diligence?

The top five risks are: (1) unlicensed SQL Server deployments averaging $280K–$1.2M exposure; (2) expired Software Assurance removing upgrade rights and licence mobility; (3) CSP auto-renewal commitments; (4) Azure spend without MACC structure; and (5) developer licence personal account subscriptions that are non-transferable.

How should we handle the target's Microsoft true-up that falls after close?

Treat the first post-close true-up as a standalone compliance exercise. Complete a full licence reconciliation before the true-up date. The true-up payment obligation belongs to the acquired entity but is typically funded as an integration cost. This true-up is also an opportunity to restructure the acquired entity's EA toward the acquirer's pricing tiers.