Why Microsoft Licensing Is a Hidden M&A Risk
Every significant enterprise M&A transaction involving organisations that run Microsoft technology creates a Microsoft licensing event — whether or not anyone in the deal team recognises it as one. Two companies merging typically means two Enterprise Agreements, two Microsoft 365 tenants, two sets of Azure subscriptions, two True-Up obligations, and an undetermined quantity of perpetual licences that may or may not transfer cleanly to the new combined entity.
Microsoft does not make this easy. Their agreements are bilateral contracts between Microsoft and a specific named legal entity. When that entity changes — through merger, acquisition, spin-off, or divestiture — the agreements do not automatically adjust. There is no Microsoft system that detects a corporate transaction and proactively resolves the licensing implications. The work falls on the buyer's team, and the financial consequences of getting it wrong are concrete: compliance exposure at the next audit, double-licensing costs during the integration window, and lost leverage in the commercial negotiation that inevitably follows the transaction.
This guide covers the complete Microsoft licensing framework for M&A scenarios, from pre-close due diligence through post-close integration and final rationalisation. Each section links to deeper sub-guides for organisations facing specific aspects of this challenge.
Phase 1: Pre-Close Due Diligence — What to Look for in the Target's Microsoft Estate
The quality of your post-close licensing position is largely determined by what you discover during due diligence. Most deal teams conduct IT due diligence at a high level — identifying major systems, validating infrastructure architecture, flagging critical dependencies. Few conduct deep Microsoft licensing due diligence unless prompted by a specific concern. This is an oversight with real financial consequences.
The Due Diligence Checklist
Pre-close Microsoft licensing due diligence should identify and document the following for the target organisation:
- All active Microsoft agreements: Agreement type (EA, MCA-E, CSP, MPSA, Open Value), agreement number, reseller, annual commitment value, remaining term, and renewal date.
- Microsoft 365 tenant architecture: How many tenants exist, what SKUs are deployed (E1/E3/E5/E7), user count per SKU, and whether all seats are properly assigned.
- Azure subscription structure: Active subscriptions, consumption levels, commitment versus pay-as-you-go split, and any committed spend agreements.
- Perpetual licence inventory: What products are held as perpetual licences (Windows Server, SQL Server, Office), whether they have active Software Assurance, and the currency of the entitlement documentation.
- True-Up history: Has the target company been accurately reporting True-Up counts? Underreported True-Ups represent a liability the acquirer assumes at close.
- Compliance status: Has the target received any Microsoft audit notices, participated in SAM engagements, or had any compliance disputes with Microsoft in the past three years?
- Software Assurance coverage: Which products have active SA? SA status determines eligibility for Azure Hybrid Benefit, Licence Mobility rights, and upgrade rights — all of which have real financial value.
Any material gap identified during this review — significant under-licensing, approaching True-Up with known headcount growth, or EA renewal dates that fall within 12 months of close — should be reflected in the deal valuation or in indemnification provisions. Microsoft licensing liability is an asset quality issue, and buyers who discover it post-close rather than pre-close absorb costs they had no chance to price.
Phase 2: Day 1 and the First 90 Days — Immediate Actions
From the moment a deal closes, the clock starts on several time-sensitive Microsoft licensing obligations. Organisations that treat the first 90 days as a period for continuing to operate two separate Microsoft estates without any formal intervention are incurring unnecessary cost and compliance risk every day they wait.
Immediate Notification to Microsoft
Microsoft should be notified of the corporate transaction as a formal communication — in writing, from the acquiring entity — within 30 days of deal close. This notification is not merely courteous; it is the mechanism that triggers Microsoft's account reorganisation, gets the combined entity recognised as a single commercial account, and starts the clock on any favourable corporate change provisions in the existing EA.
The notification should include: the names of both legal entities, the nature of the transaction (merger, acquisition, or divestiture), all relevant agreement numbers on both sides, the effective date of the transaction, and the intended commercial consolidation strategy. A clear, well-documented notification prevents Microsoft from discovering the transaction independently — through public announcements, LinkedIn data, or HR records — and approaching the combined entity for an audit or accelerated True-Up at a time of their choosing rather than yours.
Freeze Discretionary Microsoft Purchases
The period immediately following deal close is one of significant commercial uncertainty for Microsoft licensing. Until you have a clear view of the combined estate and a consolidated procurement strategy, discretionary new purchases — expanding existing subscriptions, adding new products, or renewing subscriptions as they expire — should be paused and reviewed centrally. Individual business units or IT teams purchasing Microsoft licences independently during the integration period add complexity and cost without strategic intent.
Establish the Licensing Integration Workstream
A dedicated Microsoft licensing integration workstream should be established within 30 days of close, with clear ownership, access to both entities' licence documentation, and authority to engage Microsoft and resellers directly. Without a dedicated workstream, licensing decisions default to whichever IT team is operationally louder, and the strategic opportunity is lost by default rather than by deliberate choice.
Phase 3: Contract Strategy — EA, MCA-E, and the Consolidation Decision
The most significant commercial decision in the Microsoft M&A process is the contract strategy for the combined entity. This decision shapes your Microsoft commercial relationship for the next three to five years, and it is a decision that Microsoft's field team will be eager to influence in ways that favour Microsoft's commercial interests rather than yours.
Understanding the Contract Options
The combined entity has several contract vehicles to evaluate. The Enterprise Agreement (EA) is a negotiated three-year volume agreement, typically available for organisations with 500 or more users. EAs offer the deepest discounts — currently 10–20% off list price, reduced from the historical 15–25% that was achievable before Microsoft's 2022 commercial changes — and the most contractual flexibility for large-scale licence management. The EA True-Up mechanism allows annual adjustments without triggering a new commercial process each time user counts change.
The Microsoft Customer Agreement Enterprise (MCA-E) is Microsoft's newer standardised commercial vehicle, designed to replace EA for most customer segments. MCA-E is a shorter, largely non-negotiable master agreement that relies on standardised order forms for specific products. Discounts under MCA-E are typically lower than what a well-negotiated EA can achieve, and the contractual leverage available to buyers is significantly reduced. Microsoft's field teams actively push MCA-E because it is commercially better for Microsoft; buyers should evaluate it objectively rather than accepting it as the default.
The Cloud Solution Provider (CSP) programme is partner-managed and appropriate for smaller organisations or for specific workloads where flexibility is more important than price. NCE monthly commitments under CSP carry zero discount. NCE annual commitments carry up to 5% off list. CSP is rarely the right vehicle for the primary agreement of a combined entity with 1,000+ users.
The Three Strategic Paths
As described in the EA Novation guide, the combined entity faces three main strategic options: formally novate one or both existing EAs to the new entity; let both run to term and consolidate at the first renewal; or negotiate a new EA for the combined entity, using the transaction as a forcing function for a comprehensive commercial negotiation. The right path depends on the relative terms of existing agreements, the renewal calendar, and the strategic Microsoft footprint the combined entity intends to build over the next three to five years.
For most organisations with 1,000+ users following a significant acquisition, the optimal path is a new consolidated EA negotiated during the first renewal window that falls within 12–18 months of deal close. This timeline allows sufficient integration to have a clear view of the combined user count, SKU requirements, and Azure consumption trajectory — all of which are essential inputs to a strong negotiation position.
Phase 4: Tenant Consolidation — The Technical and Commercial Integration
Tenant consolidation — moving all users from the acquired entity's Microsoft 365 tenant into the acquiring entity's tenant — is the most visible and most complex aspect of Microsoft M&A integration. It is also the phase with the most direct impact on double-licensing costs.
The Double-Licensing Window
The double-licensing window opens the moment two Microsoft 365 tenants are simultaneously active with users assigned to both. It closes when the last user in the acquired tenant is migrated and the acquired tenant is deprovisioned. For a mid-size acquisition (1,000–5,000 users), this window typically spans 3–6 months; for large enterprises, 6–12 months or longer. During this entire period, you are paying for two sets of licences for users who need only one.
The cost is real. A 2,000-user acquisition with users on M365 E3 at £25 per user per month carries a parallel licensing cost of £50,000 per month during the migration window. At 6 months, that is £300,000 in net incremental cost — entirely avoidable if the migration is executed promptly and phased deactivation of acquired-tenant licences is prioritised alongside user migration rather than deferred to subscription expiry.
Microsoft will sometimes provide a migration credit to partially offset this cost, but only if you ask explicitly and provide documented migration progress. The credit is not automatic and is typically negotiated as part of a broader EA consolidation discussion. Waiting until the double-licensing cost has already been incurred before raising the issue with Microsoft removes your negotiating leverage entirely.
Tenant Migration Planning Framework
Effective tenant migration planning follows a structured phasing approach. The pre-migration phase (typically 4–8 weeks) involves completing user identity mapping between tenants, auditing SharePoint and Teams content, documenting SaaS application integrations tied to the acquired tenant's identity, and selecting migration tooling. The migration phase involves phased user cutover — moving users in cohorts by business unit or geography — with parallel validation testing. The post-migration phase involves deprovisioning the acquired tenant, validating all SaaS reconnections, and completing the formal licence reduction with Microsoft.
The key planning decision is whether to migrate all workloads simultaneously (email, SharePoint, Teams, OneDrive) or in a phased approach by workload type. Simultaneous migration is faster but creates more dependency on migration tooling reliability; phased migration is slower but lower risk. For most mid-size acquisitions, a simultaneous workload migration in phased user cohorts strikes the right balance between speed (to reduce the double-licensing window) and risk management.
Phase 5: Licence Rationalisation and SKU Optimisation
The post-integration period — typically 6–18 months after close — is when the Microsoft licensing opportunity from the M&A event reaches its peak. You now have a complete view of the combined estate, the integration workstream has delivered a unified technical infrastructure, and you are positioned to make strategic decisions about the optimal licensing model for the combined organisation.
SKU Rationalisation: The M365 Tier Decision
The current M365 SKU stack is E1 → E3 → E5 → E7. E7 is the newest and top-tier SKU, positioned above E5, and it includes Microsoft 365 Copilot and advanced AI capabilities that were previously sold as expensive standalone add-ons to E5. Microsoft field teams are actively moving E5 customers to E7 at renewal, citing Copilot inclusion as the key value driver. This is an important context for the post-M&A SKU decision.
A combined entity arriving at EA renewal with a mixed E3/E5 footprint — one company on E3, one on E5 — must make a deliberate decision about the forward-going SKU mix. The options are: standardise on E3 (reducing cost but losing E5 security and compliance features), standardise on E5 (preserving advanced features but missing the E7 AI capabilities), or adopt a tiered approach with E3 for light users, E5 for core knowledge workers, and E7 for roles where Copilot has a demonstrable productivity case.
The tiered approach is almost always the right answer commercially, but it requires disciplined user segmentation — something that is significantly easier to establish during an EA renegotiation immediately following an M&A event than to retrofit into an existing EA mid-term. Use the post-M&A commercial moment to lock in a tiered SKU structure that reflects actual user roles and needs rather than the historical accident of what each company happened to purchase independently.
Azure Consumption Rationalisation
Azure consumption footprints from two independent organisations frequently contain significant overlap and inefficiency. Both entities may run separate Azure tenants (or even separate Azure AD tenants), with separate Reserved Instance commitments, separate Savings Plans, and separate relationships with different Azure regions. Post-integration Azure rationalisation can consolidate these into a single Azure consumption commitment with increased volume leverage and a unified Reserved Instance strategy.
The Azure Hybrid Benefit implications of a merged estate should also be reviewed. When two companies merge their Windows Server and SQL Server estates, the combined perpetual licence count and SA coverage may differ significantly from what was reported under two separate EAs. Ensuring that Azure Hybrid Benefit is correctly applied to the full combined estate — not just the portion originally managed by the acquirer's Azure team — is a straightforward optimisation that often yields 15–25% reduction in Azure infrastructure costs for the inherited workloads.
Phase 6: The EA Renewal — Negotiating from Strength Post-M&A
The EA renewal that follows a significant M&A event is one of the highest-leverage commercial conversations an enterprise buyer can have with Microsoft. The combined entity has increased volume, a defined consolidation story that Microsoft wants to participate in, and a clear opportunity to set the commercial terms for the next three-year period across the entire enlarged Microsoft footprint.
Building Your Negotiation Position
The negotiation position should be built on four pillars: consolidated volume (the combined user count and Azure consumption, presented as a single commercial commitment), competitive optionality (documented evaluation of alternative solutions, including Google Workspace for productivity and AWS/GCP for cloud — even if Microsoft is the likely winner, the threat must be credible), timing leverage (aligning the renewal negotiation to land in Microsoft's fiscal Q4, April through June, when field account managers have maximum quota pressure and maximum authority to discount), and future commit (an explicit willingness to commit to a meaningful Azure consumption increase or E7 adoption in exchange for improved pricing across the combined EA).
Each of these pillars individually moves the negotiation in the buyer's favour. Combined, they create the conditions for a materially better deal than either entity could have achieved independently before the transaction. The M&A event is not just an integration challenge — it is a commercial opportunity, and the organisations that treat it as such extract significantly more value from their Microsoft relationship over the subsequent three-year agreement term.
What to Expect from Microsoft in the Negotiation
Microsoft's field team will bring several commercial tools to the post-M&A renewal discussion. Expect an early push for MCA-E rather than EA — resist this default and insist on EA if your user count qualifies. Expect a Copilot-led upsell motion toward E7, which is legitimate if the economics work but should be evaluated on the actual per-user incremental cost rather than Microsoft's ROI storytelling. Expect an offer of Azure consumption credits or migration incentives — these are real but time-limited, and the conditions attached to them (minimum Azure commit, specific service adoption) need careful review.
Current standard EA discounts are 10–20% off list price. If Microsoft is offering 10% on a post-M&A renewal with 3,000+ users and a meaningful Azure commit, push back. A well-prepared negotiation at that scale should be achieving 18–20% off list on seats, with additional Azure consumption discounts layered on top. The data point to use internally is that standard pre-M&A discounts are already 10–20%, and a transaction that increases your Microsoft footprint by 30–50% should yield better economics than you had on either side pre-deal — not the same or worse.
Managing Microsoft licensing through a merger or acquisition?
Our Microsoft EA advisory specialists team has managed M&A licensing workstreams from due diligence through EA renewal for 500+ enterprise clients across EMEA and North America. We are 100% buyer-side.Divestitures: The Reverse Challenge
When an enterprise divests a business unit, the Microsoft licensing challenge runs in the opposite direction. The divested entity must exit the parent organisation's Microsoft commercial structure and establish its own — typically on a very compressed timeline driven by the separation management office rather than the optimal IT or licensing schedule.
The core challenges in a divestiture scenario are: carving out perpetual licences attributable to the divested business (often difficult when licences are held at the enterprise level without clear business-unit assignment), establishing a new Azure subscription and Microsoft 365 tenant for the divested entity, transferring Software Assurance coverage (which can affect the divested entity's cloud migration options and Azure Hybrid Benefit eligibility), and negotiating Microsoft's commercial terms for a smaller entity that may no longer qualify for EA pricing.
Divested entities face a particularly difficult Microsoft commercial reality: they are typically smaller than the parent, have less leverage in negotiations, and are transitioning at a time of operational disruption. Microsoft is aware of this dynamic. Engaging a specialist Microsoft licensing advisory firm on the buyer side of a divestiture — one that understands Microsoft's field team incentives and the range of commercial options available — can be the difference between landing on a reasonable standalone agreement and being pushed into an uncompetitive NCE structure at list price.
Summary: The Complete Microsoft M&A Licensing Framework
Effective Microsoft licensing management across an M&A transaction requires structured action across six phases: pre-close due diligence to identify hidden liabilities and compliance gaps; Day 1 notification and freeze of discretionary purchases; contract strategy decision across EA, MCA-E, and consolidation paths; tenant consolidation executed to minimise the double-licensing window; licence rationalisation and SKU optimisation for the combined estate; and EA renewal negotiated from a position of consolidated volume and commercial leverage.
The organisations that execute this well treat Microsoft licensing as a strategic workstream throughout the M&A lifecycle — not as an IT administration task to be dealt with after the operational priorities are resolved. The commercial opportunity is real: combined licence rationalisation, reduced double-licensing costs, and improved EA renewal terms can deliver savings that in many cases exceed £1M over the first three-year period following a significant acquisition. That is a return on the licensing investment that justifies the focus it deserves.