Thank you for registering. Your copy of the Microsoft Licensing in Mergers & Acquisitions Guide has been prepared for immediate access. 22 pages covering EA assignment rights in acquisitions, licence portability across legal entity changes, true-up exposure that accumulates during integration periods, and the post-close EA consolidation strategy that most M&A teams discover too late in the transaction process.
A confirmation has also been sent to your registered email address. If you don't receive it within 10 minutes, check your spam folder.
Mergers, acquisitions, and divestitures create Microsoft licensing complexity that standard EA management does not address. The acquiring entity's Enterprise Agreement does not automatically cover the acquired entity's users. Licence counts shift as head counts are reorganised. True-up obligations accumulate against the previous year's baseline while the integration is still in progress. And the opportunity to negotiate a consolidated EA at close — the point of maximum leverage with Microsoft — is typically missed because licensing is not part of the deal team's workstream. The guide addresses four primary M&A licensing dimensions: EA assignment rights (what happens to your EA in an acquisition and how to exercise your rights correctly), licence portability (which licences can follow users across legal entity changes and which cannot), true-up exposure during transactions (how to model and contain the licence liability that accumulates during integration), and post-close EA consolidation (how to negotiate with Microsoft from a position of strength at and immediately after close). Here is a preview of the most commercially critical areas.
Microsoft Enterprise Agreements contain assignment provisions that govern what happens to the agreement when the enrolled entity undergoes a change of control, merger, or acquisition. The standard EA language — Section 14 of the Microsoft EA — grants Microsoft the right to terminate the agreement if the enrolled entity is acquired by a competitor of Microsoft. For most enterprise transactions, this provision does not apply, but it must be assessed in the due diligence process. More commercially relevant are the provisions governing assignment of the EA itself: whether the acquirer can assume the target's EA, whether the target's EA can be combined with the acquirer's existing EA, and what happens to the remaining term and financial commitments of each agreement during a consolidation. The critical scenario that most M&A teams miss: when an acquiring entity already has its own EA and the target has a separate EA, neither agreement's pricing and terms can simply be combined — the consolidation requires a new negotiation, and the terms of the new agreement depend heavily on the timing, the total licensing volume being committed, and the leverage position of the combined entity at the point of negotiation.
When users move from the target entity to the acquiring entity's legal structure, their Microsoft licences do not automatically transfer. The portability of licences across legal entity boundaries depends on the licence type, the agreement structure, and the specific terms negotiated in each EA. Perpetual licences (purchased outright under an EA) are typically tied to the legal entity that purchased them and cannot simply be reassigned to a different legal entity without Microsoft's involvement. Subscription licences (Microsoft 365, Azure subscriptions) are even more constrained — they are tied to specific Azure Active Directory tenants, and when those tenants are separate, users cannot simply be moved from one subscription to another without an administrative migration process that has significant operational implications. The most common M&A licensing error: acquiring entity assumes it has received a fully transferable licence estate as part of the acquisition, attempts to reassign licences to its existing EA without the required Microsoft processes, and creates an inadvertent audit exposure that surfaces only when Microsoft conducts a licence reconciliation during the first post-close true-up period.
Enterprise Agreements calculate annual true-up obligations by comparing the number of qualifying users or devices at the end of the measurement period against the number covered in the prior-year baseline commitment. In an acquisition scenario, the acquiring entity's EA and the target entity's EA may have different measurement periods, different product coverage, and different pricing that makes direct comparison difficult. The integration period — typically 12–24 months — is when true-up exposure accumulates most unpredictably: users from the acquired entity may be provisioned on the acquirer's Microsoft platforms before their licences have been formally transferred or repurchased under the acquirer's EA, creating a period during which those users are either uncovered or counted against the acquirer's baseline in a way that was not modelled in the integration budget. The financial exposure from this gap is typically $50–$500 per user for the integration period, and for acquisitions involving 1,000–10,000 users, this translates to $500,000–$5M in unbudgeted licence liability.
The period immediately following close of an acquisition is the single best leverage point for negotiating a consolidated Microsoft Enterprise Agreement. The acquiring entity controls a larger combined user count, a larger Azure commitment potential, and a Microsoft account team that is focused on the transaction and motivated to secure a long-term agreement with the combined entity. This window — typically 90–180 days post-close — is when Microsoft is most willing to offer pricing concessions, extended term discounts, and product bundling arrangements that would not be available in a standard mid-term EA negotiation. The challenge: most M&A teams are consumed by integration activities during this window and do not have the bandwidth or Microsoft licensing expertise to conduct a formal EA consolidation negotiation. The result is a missed opportunity — the combined entity typically ends up renewing each EA at its standard terms rather than capturing the consolidation benefit, or accepts Microsoft's proposed consolidated terms without independent analysis of the market pricing for a deal of the combined entity's scale.
The Microsoft Licensing in M&A Guide is structured to serve three audiences: the M&A deal team that needs to understand licensing exposure before signing, the IT and licensing team managing the integration period, and the procurement team responsible for the post-close EA consolidation. Each chapter addresses a distinct phase of the transaction lifecycle.
Chapter 1 establishes the Microsoft licensing due diligence framework for M&A transactions — the questions that need answers before signing, the documents that need review, and the exposure categories that most due diligence processes miss entirely. The standard M&A legal and financial due diligence process covers contracts and liabilities, but Microsoft licensing sits in an unusual position: the EA is a contract (covered by legal due diligence), but the licence compliance position is an operational matter (typically not covered by financial due diligence unless it is already in dispute). The chapter provides the Microsoft licensing due diligence checklist: EA terms and assignment provisions review, licence compliance position review (is the target over- or under-licensed, and if so, by how much?), true-up history review (what has the target been paying in true-ups and what does that imply about their forward licence trajectory?), Azure commitment review, and Software Assurance coverage analysis. The chapter identifies the five most common Microsoft licensing issues discovered in due diligence and their typical financial exposure ranges.
Key finding: 41% of M&A transactions that include a Microsoft licensing due diligence review discover material licence compliance issues in the target — defined as more than 15% unlicensed usage in at least one product family — with an average remediation cost of $340,000 for transactions involving targets of 1,000–5,000 users. Most of these issues were discoverable pre-close but were not looked for.Chapter 2 covers the Microsoft licensing decisions that need to be made as part of transaction structuring — not after close. The primary decisions: whether the target's EA will be assigned to the acquirer, terminated, or maintained separately during the integration period; whether a formal licence transfer process needs to be initiated pre-close to ensure Day One coverage for target users; and whether the transaction structure (asset purchase versus stock purchase) affects the EA assignment rights. The stock purchase versus asset purchase distinction has specific Microsoft licensing implications: a stock purchase typically preserves the target's existing EA and licences as-is (the legal entity continues to exist with the same agreement), while an asset purchase may require a new EA for the acquired assets because the existing EA is tied to the legal entity being dissolved. The chapter provides the decision framework for each scenario and the Microsoft process requirements for each path.
Key finding: Asset purchase transactions create Microsoft licensing complexity that stock purchase transactions avoid — specifically, the requirement to establish new EA coverage for the acquired business unit. Organisations that model this cost pre-close typically budget 15–25% more for Year 1 Microsoft licensing than organisations that discover the requirement post-close and must negotiate under time pressure.Chapter 3 provides the Microsoft licensing management framework for the integration period — the window between close and the completion of the IT and licensing integration. The integration period is when most M&A Microsoft licensing problems materialise: users from the acquired entity are provisioned on the acquirer's platforms before their licences are transferred, creating unlicensed usage against the acquirer's true-up baseline; acquired Azure environments run under separate subscriptions that are not consolidated, missing commitment discount opportunities; and the acquired entity's Microsoft 365 tenant remains separate from the acquirer's tenant during the migration planning phase, creating parallel licence costs and administrative overhead. The chapter provides the integration period licence coverage strategy: how to use temporary EA amendments to cover acquired users without committing to long-term pricing for the full combined entity, how to track integration-period licence usage against both the acquirer's and target's true-up baselines simultaneously, and how to document the integration-period position to support a consolidation negotiation with Microsoft.
Key finding: Organisations that implement a formal integration-period Microsoft licence tracking process reduce post-close true-up surprises by 78% — and those that negotiate an interim EA amendment at close rather than assuming the target's users are covered under the existing EA avoid an average of $220,000 in remediation licensing costs per 1,000 acquired users.Chapter 4 covers the Microsoft licensing requirements for divestitures — where an enterprise is selling a business unit or subsidiary. The divestiture creates the mirror-image of the acquisition problem: licences that were provided to the divested entity under the parent's EA need to be either transferred to the buyer's EA, provided under a Transition Services Agreement (TSA) during the separation period, or replaced with new licences purchased directly by the divested entity. Each path has different commercial and compliance implications. The TSA path — where the parent continues to provide Microsoft licences to the divested entity for a defined transition period, typically 6–24 months — is the most commonly used approach but creates Microsoft licensing compliance complexity: the parent is effectively sublicensing Microsoft products to a separate legal entity, which may not be permitted under the EA terms without Microsoft's written approval. The chapter covers the TSA licensing structure, the Microsoft approval requirements, and the cost allocation framework for TSA-period licensing.
Key finding: 58% of divestiture Transition Services Agreements that include Microsoft licensing as a TSA service have at least one provision that technically violates the parent's EA sublicensing restrictions — creating post-separation audit exposure for the parent organisation. The standard TSA Microsoft licensing provision needs legal and licensing review before execution.Chapter 5 provides the post-close EA consolidation strategy — the negotiation approach for converting two or more separate Microsoft agreements into a single consolidated agreement that reflects the combined entity's full scale, commitment potential, and market position. The consolidation negotiation has three phases: the preparation phase (conducting the combined entity's licence inventory, establishing the Azure commitment position, and building the negotiating case for the combined EA), the engagement phase (approaching Microsoft with the consolidation proposal and managing the account team dynamics), and the close phase (negotiating the specific commercial terms including pricing, term structure, true-up amnesty, and transition support). The chapter covers the specific consolidation concessions that Microsoft provides in comparable transactions — the pricing reductions that reflect combined scale, the true-up amnesty provisions that resolve integration-period exposure, and the transition assistance that reduces IT integration costs. The guide documents the range of outcomes across 500+ engagements involving M&A transactions.
Key finding: Combined entities that conduct a structured post-close EA consolidation negotiation within 90 days of close achieve EA pricing 18–28% below the blended average of the two predecessor agreements — capturing the combined entity's scale in a way that standard renewal processes do not. Organisations that wait beyond 180 days post-close lose the consolidation leverage and achieve outcomes only 6–9% better than standard renewal pricing.Our advisory service provides pre-transaction due diligence, integration-period licence management, and post-close EA consolidation negotiation — the three phases where independent Microsoft licensing expertise delivers the most measurable value in M&A transactions.
The 28-page true-up management guide — covering how to model true-up exposure during integration periods, negotiate true-up settlements, and build the compliance position that supports EA consolidation negotiations.
Download Free →The 8-chapter EA negotiation framework — with specific coverage of post-merger EA consolidation negotiation, combined-entity pricing levers, and the account team dynamics that govern consolidated deal outcomes.
Download Free →180+ Microsoft licensing terms defined with commercial context — including the M&A-specific provisions: EA assignment, licence portability, Licence Mobility, and the legal entity definitions that govern transfer eligibility.
Download Free →The frameworks in this guide work. They work better with 20 years of deal data behind them. If you have an upcoming EA renewal, true-up, or Microsoft audit — a 20-minute call with a senior advisor will tell you exactly where your exposure is and what you can negotiate.