Microsoft license transfer during M&A turns on three contract mechanics: the assignment clause that controls whether the contract can move to a new party, the change-of-control provisions that determine whether Microsoft's consent is required, and the notification window (typically 10 to 30 days post-close) Microsoft expects to learn of the transaction. In a stock acquisition where the named entity persists, the EA / MCA-E typically continues without separate assignment; in an asset acquisition where the entity dissolves, assignment to the acquirer requires Microsoft's written consent, and the consent is a negotiation. Divestitures require a separate transfer mechanism (typically a TSA bridge followed by a new EA for the divested business). The 2026 amplifiers are tier-collapse revaluation on the combined estate, Copilot-deployment commitments that may not transfer cleanly, and MACC reset risk when the underlying Azure consumption changes legal entity. The companion M&A integration playbook covers the broader programme context.
The starting position on Microsoft license transfer during M&A: the EA is not a transferable contract by default. The Enterprise Agreement is signed with a named customer entity, and Microsoft's terms condition assignment to a third party on Microsoft's written consent. The same conditioning applies to the MCA-E (Microsoft Customer Agreement for Enterprise) and most CSP indirect contracts. The mechanic produces an asymmetric outcome: the acquirer often discovers at Day 30 of integration that the target's EA cannot simply re-paper as an affiliate of the acquirer; the assignment requires consent; Microsoft uses the consent posture as leverage to drive pricing or commitment outcomes that the acquirer would not have accepted at an arm's-length renewal. The buyer-side discipline is to map the assignment posture pre-close and structure the transaction such that consent is either not required, or is sought in a posture where leverage favours the buyer rather than Microsoft.
The assignment clause in Microsoft enterprise contracts
Microsoft's standard assignment language in the EA and MCA-E follows a recognisable pattern: the agreement may not be assigned by the customer without Microsoft's prior written consent, except (in some EA generations) in a corporate reorganisation where the assignee assumes all the customer's obligations. The "except" clause is the leverage anchor; its specific wording varies by EA generation and by negotiated amendment, and a buyer-side review of the precise clause is the first artefact in any M&A licensing-integration plan.
Three patterns recur in the actual clause language.
- Strict assignment clause. Assignment requires Microsoft's written consent under any circumstance, including affiliate or corporate-reorganisation transactions. Microsoft has full discretion on consent. This clause appears in older EA generations and in some custom-amendment provisions; the buyer-side leverage is limited because Microsoft can condition consent.
- Reorganisation exception. Assignment requires consent except in a corporate reorganisation where the assignee assumes all obligations. The phrase "corporate reorganisation" is interpreted narrowly by Microsoft (typically to mean intra-group restructuring rather than third-party M&A); the exception does not automatically cover a third-party acquisition. The buyer-side discipline is to read the precise definition and not assume the exception covers the contemplated transaction.
- Change-of-control provision. Some EA amendments add a change-of-control clause that triggers Microsoft's right to terminate or re-negotiate on a change of control of the customer entity. This clause is less common in standard EAs but appears in custom amendments where Microsoft has negotiated additional protections. The buyer-side discipline is to scan for change-of-control language specifically; its presence converts a stock-acquisition continuity story into an explicit re-negotiation moment.
Stock vs asset deal mechanics for Microsoft license transfer
The deal-structure choice (stock vs asset) determines the default license-transfer mechanic.
| Deal structure | Named entity disposition | EA / MCA-E continuity default | Consent typically required |
|---|---|---|---|
| Stock acquisition (target entity persists as subsidiary) | Target entity continues to exist | EA continues; the named-entity is still the customer-of-record | No (unless change-of-control clause present) — but notification required |
| Asset acquisition (assets transferred, entity dissolved) | Target entity dissolved post-transfer | EA cannot continue; assignment to acquirer requires consent | Yes — Microsoft consent required for assignment |
| Merger (two entities combine into one or new entity) | One or both predecessor entities dissolved | Depends on which entity survives; assignment may be required | Possibly — depends on surviving-entity status |
| Divestiture (subsidiary or business unit separated) | Divested unit becomes new standalone entity | Parent EA continues; divested unit needs new EA or TSA bridge | For TSA bridge: covered by parent EA; new EA terms separately negotiated |
The stock acquisition is operationally simpler because the named entity persists; the EA does not need to be assigned. The acquirer typically rolls the acquired entity into its own EA at the acquired entity's next anniversary or via an amendment to the acquirer's EA expanding the affiliate scope. The notification to Microsoft is required (the named entity has a new ultimate parent), but the contract continuity itself does not turn on Microsoft's consent unless change-of-control language is present.
The asset acquisition forces the assignment question. The target's licensing position needs to move from the dissolved entity to the acquirer or to a new acquirer-controlled entity. Microsoft's consent is required for the assignment; the consent is negotiated; Microsoft's posture typically includes a request that the assigned position be repriced to the acquirer's discount tier, that any open commitments (MACC, Copilot, SA) be re-validated, and that the acquirer take on the target's true-up exposure. Mature M&A licensing-integration teams negotiate the consent and the re-pricing as a single conversation rather than accept Microsoft's preferred sequencing of "consent first, then we discuss pricing".
Consent as buyer-side leverage
The consent requirement is structurally a leverage exchange. Microsoft wants the named entity to remain a paying customer; the acquirer wants the consent to be granted at acceptable economics. The buyer-side leverage depends on three factors.
First, the deal-close timing relative to Microsoft's fiscal year. Microsoft's account teams have stronger Q4 (April-June) incentives to close deals; consent requests in Q4 carry better pricing leverage than the same request in Q1. The integration-team timing should map to this dynamic where deal-close timing is flexible. See the quarter-end discount dynamics for the broader timing context.
Second, the alternative consumption story. An acquirer that has a credible alternative (consolidating workloads onto an existing EA at a higher discount tier; moving acquired workloads to Google Workspace or AWS; deferring Copilot expansion) carries more consent leverage than an acquirer signalling that the target's full Microsoft stack is essential. The buyer-side discipline is to develop and present the alternative story explicitly, not just hold it as an unstated reservation.
Third, the consent posture matters relative to deal close. Consent sought pre-close gives Microsoft leverage to condition the consent on deal terms; consent sought post-close finds Microsoft negotiating against integration economics with the deal already done. The choice is deal-specific and depends on regulatory timing and risk tolerance, but the framework should be deliberate.
The buyer-side license-transfer discipline
Five operating practices recur in mature M&A license-transfer programmes.
Read the precise assignment and change-of-control clauses in both EAs pre-close
The first artefact is the precise assignment-clause language for the acquirer's EA and the target's EA. The language varies by EA generation and by negotiated amendment; the buyer-side discipline is to capture both clauses verbatim, model the consent posture for the contemplated transaction structure, and identify any change-of-control triggers that would convert a routine continuity story into an explicit re-negotiation. The artefact informs both deal structure and integration timing.
Build the post-close notification calendar against the 10-to-30-day window
Microsoft typically expects notification of a material change in customer-entity status (acquisition, dissolution, change of control) within 10 to 30 days post-close depending on the contract version. Late notification can produce its own friction, including challenges to continued licence validity. The buyer-side discipline is to calendar the notification windows from both contracts (acquirer and target) and ensure the integration team owns the notification artefact. Notifications should be documented in writing through the Microsoft account team and through the named contract-administration contact.
Decide pre-close whether to seek consent before or after deal close
The pre-close consent strategy is a deliberate choice. Pre-close consent gives Microsoft visibility into the transaction and an opportunity to condition consent; post-close consent finds Microsoft negotiating against integration economics with the deal complete. The choice depends on transaction risk tolerance, regulatory timing, and the strength of the buyer-side alternative consumption story. The framework should be agreed across the legal, deal-team, and licensing functions before approach to Microsoft.
Negotiate the consent and the re-pricing as a single integrated conversation
Microsoft's preferred sequencing is "grant consent first under existing terms, then renegotiate pricing at the next renewal". The buyer-side discipline is to refuse this sequencing and to negotiate consent and re-pricing as a single conversation. The combined discount tier, MACC commitment, Copilot true-up posture, and SA-renewal terms should all land on the table at the consent moment, not three separate conversations spread over 18 months. The integrated re-negotiation produces 6 to 14 percent better outcomes than the sequential approach.
Validate the target's pre-transfer commitments and clear exposure before transfer
The target may carry open commitments (MACC consumption shortfall, Copilot deployment commitments, true-up exposure, SA-renewal obligations) that transfer to the acquirer on assignment. The buyer-side discipline is to inventory these commitments pre-close and either resolve them on the target's side before transfer or explicitly carve them out of the transfer scope. Unresolved commitments inherited at transfer become integration-team problems with leverage now sitting fully with Microsoft.
Asset acquisition closing and assignment consent not yet sought? Pre-close framework decisions are leverage.
30-minute scoping call. Assignment-consent strategy is standard advisory work.
2026 amplifiers shaping Microsoft license transfer in M&A
Three 2026 dynamics reshape the license-transfer economics this cycle.
- EA tier-collapse revaluation on combined estate. The 2026 EA tier collapse changes the price-band economics for the combined post-transfer estate. Combined positions that crossed price bands in prior tier structures may price differently under the post-collapse structure; the buyer-side discipline is to model the combined position under both pricing structures and time the consent / transfer motion deliberately.
- Copilot commitments that may not transfer cleanly. Copilot for M365 commitments and Copilot Studio (CCCU/ACU) capacity reservations are structured as commitments tied to the named entity. Asset-acquisition transfer of these commitments requires explicit assignment and Microsoft's consent; the consent posture is more aggressive than for traditional EA SKUs because Microsoft tracks Copilot adoption as a strategic-deal metric. The buyer-side discipline is to inventory Copilot commitments separately and negotiate their transfer explicitly.
- MACC reset risk on entity change. The MACC (Microsoft Azure Consumption Commitment) is tied to the named entity; entity-level changes can trigger a MACC reset where the unconsumed commitment is forfeit and a new MACC negotiated. The reset is not automatic; it is Microsoft's posture at the transfer moment. The buyer-side discipline is to model the MACC posture pre-close and negotiate the MACC continuation explicitly as part of the consent conversation. See the MACC negotiation pillar for the broader context.
The under-appreciated leverage point in license-transfer negotiation is the formal alternative-consumption story. Microsoft's account teams respond to credible alternatives with more flexibility than to expressed need; the same consent request lands differently if the acquirer has documented an internal plan to migrate target workloads to Google Workspace, AWS, or a competing security stack should the consent / re-pricing terms not work. The plan does not need to be the acquirer's preferred outcome; it needs to be credible. Mature M&A licensing integration teams develop and present the alternative-consumption plan as a formal deck inside the negotiation, not as an unstated reservation. The framework produces 4 to 9 percent better consent outcomes versus the unstated-alternative approach.
The Microsoft Negotiations briefing
Monthly. M&A licensing integration, EA negotiation, transfer mechanics, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the license-transfer discipline next
The license-transfer discipline pairs with the broader M&A and EA-negotiation framework. The M&A integration playbook covers the broader programme context; the due-diligence guide covers the diligence-phase checklist; the affiliates and subsidiaries guide covers the affiliate-clause integration mechanic; the EA negotiation pillar covers the broader renewal-cycle context; the EA strategy service is the productised renewal-cycle engagement; the contract advisory service is the productised assignment / consent engagement. For organisations approaching an M&A transaction, the scoping call is the direct engagement channel; for broader scoping, the free EA assessment is the broader channel.
Transaction-specific guidance: the post-close EA consolidation playbook covers acquirer-side integration; the divestiture / EA-splitting playbook covers carve-out mechanics; the spin-off licensing playbook covers separation transactions; the cross-border M&A playbook covers international transfer considerations.
The general entity-to-entity transfer playbook covers the assignment-vs-novation mechanic across all restructuring scenarios beyond M&A; the post-merger integration playbook covers the 12-month integration cadence that follows the transfer; the private-equity portfolio playbook covers cross-portfolio transfer discipline for PE-backed acquirers; the merging IT environments playbook covers the operational tenant-and-workload reconciliation that follows transfer execution.