Mergers, acquisitions, and divestitures create immediate Microsoft licensing risk that most deal teams discover too late. The standard Enterprise Agreement is not assignable without Microsoft's consent. Change of control provisions in the EA can be triggered by acquisitions. Deployed software at an acquired entity may not be covered by either the acquirer's or the target's existing EA. And Microsoft's commercial organisation — which tracks corporate change closely — uses M&A events as audit triggers and commercial reset opportunities.
The organisations that manage through M&A without significant Microsoft licensing disruption are those that engage their Microsoft licensing adviser before close — ideally during due diligence — not after the transaction has completed and the licensing gaps have crystallised into exposure.
The Three M&A Scenarios and Their Distinct Licensing Implications
Microsoft licensing in M&A covers three distinct corporate scenarios, each with different implications for EA structure, licence coverage, and renegotiation strategy.
Scenario 1: You Are the Acquirer
Your organisation acquires another entity. You need to determine: whether the acquired entity is covered under your existing EA; whether the acquired entity has its own EA (and if so, what happens to it); whether there is deployment at the acquired entity that is not covered by any EA; and what the combined entity's Microsoft spend looks like and what leverage that creates for commercial renegotiation.
Scenario 2: You Are the Target
Your organisation is being acquired. Your EA commitments — financial and operational — are assets and liabilities that the acquirer is buying. Change of control may trigger specific EA provisions. Your Microsoft account team will be aware of the transaction and will be planning commercial actions accordingly.
Scenario 3: You Are Divesting a Business Unit
Part of your organisation is being separated. The divested entity needs Microsoft licensing. Whether that comes from your EA, a new independent EA, or a transition agreement is a negotiation — with both Microsoft and the buyer. Licence transfer provisions in your EA determine what is and is not moveable.
What Happens to Your EA in Each Scenario
| M&A Event | EA Assignment Status | Key EA Provisions Triggered | Primary Risk | Action Required |
|---|---|---|---|---|
| Acquisition of unlicensed entity | Your EA likely does not cover acquired entity automatically | EA affiliate/subsidiary definition; audit rights Section 6 | Unlicensed deployment from Day 1 of consolidation | Verify EA affiliate definition; negotiate EA amendment to cover or obtain transition licence |
| Acquisition of entity with its own EA | Two separate EAs — cannot merge automatically | Co-terming provisions; MACC separate commitments | Duplicate EA overhead; missed volume consolidation leverage | Evaluate co-term or consolidation; negotiate at best timing window |
| Your organisation is acquired | Change of control may make EA non-assignable without consent | Change of control clause (if present); audit rights | EA becomes invalid or requires Microsoft consent to continue | Review EA change of control clause before close; negotiate consent terms |
| Divestiture of business unit | Licences not transferable without Microsoft consent as standard | Licence assignment restrictions; VLSC record transfer requirements | Divested entity has no licensing on Day 1 post-close | Negotiate licence transfer or transition agreement pre-close; VLSC records transfer plan |
| Merger of equals | Two EAs exist; new legal entity may need new EA | EA entity definition; VLSC registration; true-up recalibration | Compliance gap during IT integration period (often 12–18 months) | Negotiate integration period licence coverage; plan EA consolidation timeline |
The EA Affiliate and Subsidiary Definition — The Most Important Clause in M&A
Whether an acquired entity is automatically covered by your EA depends entirely on how your EA defines "Affiliate." The standard Microsoft EA definition of Affiliate is: "any legal entity that you own or control, or that owns or controls you, or that is under common ownership or control with you, where 'control' means ownership of more than a 50% interest in the voting securities of the entity."
The practical implication: entities you acquire at greater than 50 percent ownership are typically covered as Affiliates under your EA — but only for the products and licences already committed in your Enrolment. New users and devices at the acquired entity that push you above your committed licence count are subject to true-up reporting, at your EA pricing. Entities acquired at less than 50 percent are NOT covered automatically.
The "Day 1" Compliance Gap
Even where an acquired entity qualifies as an Affiliate under your EA, there is typically a period — from acquisition close to the first EA anniversary true-up — where the acquired entity's users are technically operating under your EA but the incremental licences have not been formally added. This is not automatically non-compliant, but it creates audit exposure if the total deployed count is not reconciled and reported at the next true-up. Build a post-acquisition licence reconciliation into your integration plan, with a defined timeline for true-up or mid-year EA amendment.
Acquisition Due Diligence: The Microsoft Licensing Checklist
Microsoft licensing due diligence in an acquisition is a distinct workstream that most deal teams do not adequately prioritise. The items below are the minimum required to understand your licensing exposure before close:
Target's Current EA / Licensing Agreements
Obtain copies of all current Microsoft agreements: EA enrolment, price sheet exhibit, any amendments, SPLA or MPSA agreements. Verify term dates, committed volumes, and pricing. Assess the gap between committed volume and actual deployment (over-licensing opportunity or under-licensing risk).
VLSC Licence Records
Request a VLSC (Volume Licensing Service Centre) export from the target showing all licence purchase history, Software Assurance status, and product activations. Compare against deployed software to establish the Effective Licence Position (ELP). Unresolved gaps become your liability at close.
Audit History and Open Audit Risk
Confirm whether the target has received any Microsoft audit or SAM engagement notice in the previous 24 months. Active or recently completed audits create specific contractual exposure that transfers with the acquisition unless explicitly carved out in the purchase agreement. An unresolved audit gap of $800K is a liability, not a post-close operational matter.
Software Assurance Status and Value
SA benefits have value — step-up rights, training vouchers, planning services, Azure hybrid benefit entitlements. Verify which SA benefits are active, what their expiry dates are, and whether any benefits have been claimed. SA expiry within 12 months of close is a flag: renewal decisions need to be made quickly post-integration.
Cloud Commitments — Azure MACC, M365 CSP, Dynamics
Cloud commitments are minimum spend obligations. A $2M annual MACC that the acquired entity cannot meet post-integration is a financial liability. Assess all cloud subscription commitments, their term dates, and whether they are transferable or must be novated. MACC commitments are generally not transferable without Microsoft agreement.
The Post-Close Licensing Integration Timeline
Post-acquisition, the licensing integration workstream has three phases. Each has a defined decision point and commercial consequence if missed.
Phase 1: 0–90 Days Post-Close (Immediate Coverage)
Priority: ensure no compliance gap exists. If the acquired entity's EA is expiring within 90 days of close, it needs to be extended or replaced. If your EA Affiliate definition covers the target, document this in writing with Microsoft. If the target was using unlicensed software, begin remediation immediately. Microsoft's commercial organisation will be aware of the acquisition and will be monitoring for engagement.
Phase 2: 90–180 Days Post-Close (Consolidation Planning)
Priority: develop the EA consolidation strategy. Options are: absorb the target's licences into your EA via amendment; allow both EAs to run until the earlier expiry and consolidate at that point; or allow both EAs to run independently and negotiate a combined deal at the later expiry. The right answer depends on the target's EA terms, pricing, and the combined volume leverage available. If the combined M365 or Azure commitment crosses a volume threshold, the consolidation negotiation can generate meaningful discount improvement.
For EA consolidation strategy, the post-M&A context is one of the strongest commercial positions for negotiating improvement: Microsoft wants to retain both EA customers in a single consolidated agreement and will make commercial concessions to secure that outcome.
Phase 3: 180 Days–24 Months (Commercial Optimisation)
Priority: use the combined spend profile to negotiate the optimal long-term agreement. The combined Microsoft spend of both entities represents new volume leverage that neither had independently. This leverage is most valuable at the first EA renewal after integration — when you can present a consolidated volume commitment with a single negotiating event.
Use the M&A Event as a Commercial Reset Trigger
Microsoft's commercial organisation treats significant M&A events as sales opportunities. Your account team will be proactive in scheduling meetings, presenting "integration offers," and proposing combined agreements. This commercial interest is your leverage. Do not engage with Microsoft's consolidation proposal until you have independently assessed your optimal combined licensing position, established competitive alternatives, and determined your target pricing. Microsoft's first consolidation proposal is almost never their best commercial offer. See our EA negotiation complete guide for the approach.
Divestiture: What Happens to Your Licences When You Spin Off
Divestitures are the licensing scenario most organisations plan for least. The divested entity needs Microsoft licensing from Day 1 post-close, but the licences they have been using are typically attached to the parent's EA — which the divested entity can no longer use.
The Licence Transfer Problem
Microsoft licences are not freely transferable. The standard EA does not allow you to transfer committed licences to a third party — including a divested subsidiary — without Microsoft's explicit consent. Software Assurance benefits are particularly non-transferable. VLSC records showing licence ownership sit under the parent entity's billing account and require a formal transfer process that can take 60–90 days.
The Transition Licence Solution
The practical solution is a Transition Licence Agreement — a temporary extension that allows the divested entity to continue using Microsoft software under a transitional arrangement for a defined period (typically 12–24 months) while it establishes its own independent licensing. Transition licences are negotiated as part of the divestiture transaction and should be addressed in the sale agreement, not as an afterthought post-close.
Key terms to negotiate in the transition licence: duration (minimum 18 months to allow the divested entity to establish its own EA); pricing (typically at the parent's EA rate — the divested entity is losing volume discount but should not pay list price during transition); and scope (must cover all products in active use by the divested entity's users).
Carve-Out Negotiations with Microsoft
For material divestitures, engage Microsoft directly — at the account executive and AVP level — to negotiate a carve-out arrangement. Microsoft has commercial interest in retaining the divested entity as a customer. This interest creates negotiating leverage: the divested entity will need to sign its own EA eventually, and Microsoft will compete for that business. Use that future revenue prospect as leverage to negotiate reasonable transition terms and pricing.
Purchase Agreement Provisions for Microsoft Licensing
The acquisition or divestiture purchase agreement should include specific provisions addressing Microsoft licensing. These are frequently overlooked by deal counsel who are not specialists in software licensing, and the omission creates post-close disputes.
For acquisitions, include: representations and warranties on Microsoft licence compliance as of close date; disclosure of all open Microsoft audit or SAM engagements; disclosure of all EA commitments and their financial terms; and a post-close mechanism for indemnifying the acquirer for pre-close compliance gaps discovered in post-close due diligence.
For divestitures, include: the transition licence agreement terms as an exhibit; the VLSC licence transfer plan and timeline; representations on which licences are included in the divested entity's licensing footprint; and the pricing basis for transition period licensing.
The most common post-close dispute in M&A transactions involving significant Microsoft licensing is the "who owns this liability" argument when a compliance gap is discovered after close. Clear purchase agreement language resolves this before the dispute arises. See our guide to Microsoft audit defense for the compliance gap assessment methodology that should be performed as part of due diligence.
The Microsoft Account Team in M&A Transactions
Microsoft's commercial organisation tracks M&A activity through public filings, press coverage, and their own corporate intelligence. When a significant transaction involving one of their enterprise customers is announced, the account team begins planning their commercial response before you engage them.
This is not cynicism — it is the commercial reality of how enterprise software vendors operate. The account team's response typically includes: scheduling an "integration support" meeting that is really a commercial opportunity assessment; proposing a combined agreement that is optimised for Microsoft's revenue objectives, not yours; and potentially accelerating audit or SAM engagement activity to establish a compliance baseline before the integration changes the deployment picture.
The appropriate response is structured proactive engagement. Contact your account team early, control the information shared (do not provide detailed deployment data before you have validated your own ELP), and establish that your organisation's integration timeline — not Microsoft's commercial calendar — will drive any agreement restructuring. For guidance on managing this dynamic, see our account team management guide.
M&A is one of the highest-impact licensing events in your Microsoft relationship. The organisations that handle it well treat it as a structured commercial negotiation — one that begins in due diligence, is managed proactively through the integration period, and is resolved with a combined agreement that reflects the value of the consolidated relationship.