The Licensing Problem No One Plans For in M&A
The deal team negotiates terms. The IT team begins integration planning. Legal coordinates the entity restructure. And somewhere in the background, Microsoft is quietly running two separate Enterprise Agreements, two separate Microsoft 365 tenants, and two separate billing relationships — with no automatic mechanism to reconcile any of it.
This is the standard state of affairs in the first 90 days of any significant merger or acquisition involving enterprise Microsoft customers. Both entities typically have active EAs or NCE agreements with different renewal dates, different user counts, different SKU mixes, and different discounts. Neither agreement acknowledges the other's existence. Microsoft's commercial team is aware of the situation, but they will not proactively come to you with a consolidation plan. That work falls on you — and the clock is running from the day the deal closes.
The organisations that handle this well engage their Microsoft licensing function — either internal or external — at the Letter of Intent stage, not after close. The ones that handle it badly discover the problem at their first True-Up after the merger, when the headcount discrepancy between their EA and their actual user count triggers an unexpected bill, or worse, a compliance flag during an audit.
Step One: Map All Active Microsoft Agreements
Before any consolidation strategy can be built, you need a complete view of what you are actually consolidating. This sounds obvious, but in practice, enterprise organisations routinely hold Microsoft commitments they have forgotten about: legacy Open Value subscriptions, MPSA agreements from a previous acquisition, scattered CSP relationships managed by different regional IT teams, and Office 365 NCE subscriptions purchased outside the main EA.
The mapping exercise should cover every legal entity involved in the transaction and produce a register of: agreement type (EA, MCA-E, CSP, MPSA, Open Value), agreement number, reseller, renewal date, annual commitment value, current user count, SKU mix, and active Software Assurance coverage. This register is the foundation for every subsequent decision. Without it, you are consolidating blind.
For organisations with 2,000 or more users across the merged entity, this mapping exercise typically takes 2–4 weeks and requires co-operation from the target company's IT leadership. Resistance at this stage is a red flag — it often signals that the target company's licence position is not clean, which has direct implications for your post-close True-Up liability.
The EA Consolidation Options: What Microsoft Actually Allows
A fundamental point that catches many integration teams off guard: you cannot simply merge two Enterprise Agreements mid-term. Microsoft's contractual framework does not provide a mechanism to combine active agreements into a single agreement before their respective renewal dates. You have three practical options, and the right choice depends on the relative size of the two agreements and their renewal timing.
Option 1: Let Both EAs Run to Term, Consolidate at Renewal
If both agreements have similar remaining terms (within 12 months of each other), the cleanest approach is often to maintain both independently until the first one renews, then consolidate the combined entity's seat count into a single new EA at that point. This avoids the complexity of mid-term transfer and gives your team time to complete user consolidation before committing to a unified commercial structure. The risk is carrying parallel administrative overhead and potentially paying for redundant licences during the gap period.
Option 2: True-Up the Acquired Entity Into the Acquirer's EA
If the acquirer holds an active EA with a near-term True-Up date, the acquired entity's user count can be added to the acquirer's True-Up, expanding the EA to cover the combined organisation. Microsoft's standard EA includes a clause stating that if a merger or acquisition changes the covered licence quantity by more than 10%, Microsoft will work in good faith to accommodate the change under the current agreement. This clause is useful but not unconditional — you need to engage your Microsoft account team proactively, with deal documentation, well before the True-Up date.
The practical requirement for this approach is that the acquired entity's users must be genuinely on the acquirer's Microsoft infrastructure — either already migrated to the acquirer's tenant, or at minimum, covered under a written integration plan that Microsoft accepts. Claiming 3,000 additional users on a True-Up against an EA that does not yet serve those users will trigger scrutiny and may result in Microsoft requiring a separate agreement for those users until migration is complete.
Option 3: Bridge Agreement or MCA-E Transition
For acquisitions where the acquired entity is significantly smaller than the acquirer, or where the acquired company is on a CSP or MPSA arrangement rather than an EA, a bridge agreement or transition to MCA-E may be the most practical path. A bridge agreement — essentially a short-term extension of the acquired entity's existing terms, negotiated with Microsoft — provides 12–18 months of stability while the full technical and commercial integration is completed. MCA-E transition is increasingly Microsoft's preferred recommendation in these scenarios, particularly for acquired organisations below 1,000 users, because MCA reduces the negotiated structure that gives large customers commercial leverage.
Be cautious about accepting MCA-E as the default consolidation vehicle without pressure-testing the economics. MCA-E terms are less negotiable than EA terms, the pricing structure is largely standardised, and the discount depth achievable in an MCA-E is typically lower than what you can secure in a properly negotiated EA. For a combined entity of 5,000+ users, the difference between EA-level and MCA-level discounts over a three-year term can exceed £1M on a standard M365 SKU footprint.
Avoiding Double-Licensing During the Migration Window
The most immediate and tangible cost risk in Microsoft M&A licensing is the double-licensing window — the period during which users in the acquired organisation are still running on their existing Microsoft licences while the acquiring organisation is provisioning licences for them in its own tenant. Without careful planning, you pay for both simultaneously.
For subscription-based licences (M365, Dynamics 365, NCE products), the double-licensing period is directly proportional to your migration timeline. A 6-month tenant migration for 1,500 users, at an average E3 cost of £25/user/month, generates approximately £225,000 in parallel licence spend — for software that half of those users may not be actively using on both platforms simultaneously. This is not a theoretical risk; it appears on virtually every post-acquisition Microsoft invoice review we conduct.
The mitigation playbook has three components. First, accelerate the deactivation of acquired-entity licences as users are migrated, rather than waiting for subscription expiry. Many organisations let acquired licences run to their subscription end date out of administrative convenience; this is expensive. Second, negotiate with Microsoft for a migration window credit — Microsoft will sometimes offer a 60–90 day licence offset for users mid-migration if the request is made proactively and with documented migration progress. Third, align your migration phases with your True-Up dates; timing large-scale user moves to complete just before a True-Up allows you to remove acquired-entity licences from your baseline before the annual count is locked.
Tenant Consolidation: The Technical and Commercial Timeline
Tenant-to-tenant migration — the process of moving all users, mailboxes, SharePoint content, and Teams data from one Microsoft 365 tenant to another — is a distinct workstream from the commercial agreement consolidation, but the two must be coordinated carefully.
For mid-size acquisitions (1,000–5,000 users), expect a tenant migration timeline of 3–6 months from project kick-off to final decommission. Large acquisitions (5,000–20,000 users) typically require 6–12 months. The key variables are data volume, the complexity of SharePoint and Teams integrations, the number of custom SaaS application identities tied to the acquired tenant, and the availability of third-party migration tooling with sufficient throughput.
On the commercial side, the tenant migration timeline defines the outer boundary of your double-licensing exposure. If your migration takes 9 months, you have a 9-month window during which both tenants are live and both sets of licences are technically required. Building this cost into your integration business case — and presenting it to Microsoft as a negotiating point — is far more effective than discovering it mid-project.
Licence Transfer Rules for Perpetual Licences
Perpetual volume licences — Windows Server, SQL Server, Office Standard, and other products purchased under volume licensing programmes — are transferable in the context of a genuine merger or acquisition, but the transfer process requires explicit Microsoft authorisation. The rules are stricter than many IT teams realise.
Microsoft's volume licensing policy permits transfer of fully-paid perpetual licences between entities following a merger, consolidation, or divestiture. Subscription-based products (including all NCE subscriptions and Office 365 cloud products) cannot be transferred — they must be assigned anew in the receiving entity's agreement. For perpetual licences, the original licence holder must submit a Licence Transfer Form to Microsoft before the transfer is legally effective. This is not an administrative formality — without the form, Microsoft considers the licences as still belonging to the transferring entity. In an audit scenario, the acquiring entity deploying those licences without completing the transfer is non-compliant.
In a divestiture — where a business unit is being sold rather than acquired — the same rules apply in reverse. The divested entity needs its own agreement structure and properly transferred licence entitlements before Day 1 of independence. Divestitures are frequently more complex than acquisitions from a licensing perspective because the divested entity typically has no existing Microsoft commercial relationship of its own, and Microsoft must issue new agreements while simultaneously managing the transfer of applicable licences from the parent.
SKU Rationalisation: The M&A Opportunity Most Teams Miss
An M&A event creates a natural forcing function for Microsoft SKU rationalisation that many organisations fail to leverage. When two companies merge, they frequently arrive with different SKU mixes — one might have deployed primarily E3, the other E5, with a variety of standalone add-ons built up over years of incremental procurement. Consolidating into a unified agreement is the moment to rationalise.
The current M365 SKU stack runs E1 → E3 → E5 → E7, with E7 now the top tier above E5. E7 bundles Copilot, advanced AI, and security capabilities that were previously sold as expensive add-ons to E5. Microsoft's field teams are actively pushing E5 customers toward E7 at renewal. In an M&A context, if the combined organisation is evaluating a unified SKU framework, the E7 discussion should happen during EA consolidation negotiations — not as a separate later upsell. Buying E7 as part of a merger consolidation deal, when Microsoft is motivated to close the combined agreement, often yields meaningfully better pricing than a standalone E5-to-E7 upgrade discussion at a routine renewal.
Handling a merger or acquisition involving Microsoft licensing?
Our Microsoft EA advisory specialists team has managed M&A licence consolidations for enterprises across EMEA and North America. We are 100% buyer-side.Checklist: Microsoft Licensing in M&A — 12 Actions to Take
- Map all active agreements across both entities within 30 days of deal close, including EA, MCA-E, CSP, MPSA, and any open value or retail licences.
- Notify Microsoft of the corporate change event as soon as the deal closes — do not wait until the next True-Up or renewal cycle to surface this.
- Review EA corporate change clauses in both agreements for any provisions governing M&A, including the 10% headcount adjustment clause.
- Complete Licence Transfer Forms for all perpetual volume licences being transferred between legal entities.
- Model the double-licensing cost for the expected tenant migration window and include this in your integration cost estimate.
- Negotiate a migration credit with your Microsoft account team for the parallel-run period — ask explicitly; it is not offered automatically.
- Align tenant migration milestones with EA True-Up dates to minimise the window where both licence sets are simultaneously billable.
- Evaluate SKU rationalisation as part of the consolidation negotiation, including whether E7 adoption makes economic sense at the combined entity's scale.
- Assess Copilot positioning — if the combined entity has 500+ knowledge workers who are target Copilot users, the M&A consolidation is the right moment to negotiate E7 pricing for those seats.
- Review Software Assurance continuity to ensure active SA is maintained across the migration period, preserving Azure Hybrid Benefit and Licence Mobility rights.
- Document all Microsoft communications during the M&A process — verbal assurances from account teams are not binding; written confirmations are.
- Plan for divestiture scenarios proactively: if the acquisition involves business units that may be divested within 3–5 years, build exit clauses into the new consolidated EA before signing.