A merger, acquisition or divestiture event materially resets the Microsoft licensing position. The Admodum read on the contract Affiliate clause, the integration window, the EA assignment route, the transitional service agreement and the buyer artefacts.
The Microsoft master contract (the Microsoft Business and Services Agreement under the Enterprise Agreement, the Microsoft Customer Agreement under the MCA-E) defines the Affiliate set. The standard definition is an entity that the customer (or that the customer's ultimate parent) owns more than fifty percent of, directly or indirectly. The Affiliate set is the set of entities that may use the licensed software under the master contract.
A merger, acquisition or divestiture event changes the Affiliate set: an acquisition adds entities; a divestiture removes entities; a corporate reorganisation may add and remove entities simultaneously. The Affiliate-set change is the licence position reset. The wider Enterprise Agreement overview and MCA-E versus EA spokes are the contract-framework reads.
An acquisition expands the Affiliate set by adding the acquired entity. The acquired entity becomes a permitted user of the licensed software under the existing master contract, subject to the Affiliate definition test (the more-than-fifty-percent ownership test, the corporate control test). The acquired entity's existing Microsoft contracts (its own EA, MCA-E, MPSA, Open Value or CSP estate) sit alongside the buyer's contracts.
The integration question is the consolidation route: the buyer typically consolidates the acquired entity's licence position into the buyer's primary master contract at the next anniversary or true-up. The wider EA true-up mechanics spoke is the true-up-window read; the wider Microsoft EA renewal cycle spoke is the renewal-window read against which the consolidation can be timed.
A divestiture (a sell-off of a business unit, a spin-off of a subsidiary, a separation of a corporate division) contracts the Affiliate set. The divested entity ceases to be a permitted user under the seller's master contract on the close date. The product terms specify that licences cannot be transferred to the new owner without Microsoft consent.
The buyer-side of the divestiture (the entity acquiring the divested business) must establish its own licence position: an existing EA or MCA-E expanded to absorb the divested estate, a new agreement, or a CSP transition. The licence allocation is the central question: which licences were assigned to the divested estate inside the seller's pool, on what basis, with what audit evidence.
The transitional service agreement (TSA) is the standard mechanism by which the seller in a divestiture continues to provide IT services to the divested entity for a defined period (typically six to twenty-four months) after close. The TSA period is the specific licensing exposure window: the seller's Microsoft licences would, in the absence of explicit permission, be used by an entity that is no longer in the Affiliate set.
The Microsoft product terms include limited TSA permissions in some contexts; the buyer-side artefact is the explicit Microsoft confirmation of the TSA-period licence position (often via an amendment to the master contract). The wider LSP versus direct framework reads the procurement channel question that frequently runs in parallel with the TSA window.
The integration window is the post-close procurement event. The acquired entity's existing Microsoft contracts must be inventoried (every EA, every MCA-E, every MPSA, every Open Value, every CSP relationship). The licence position must be reconciled (every product, every quantity, every Software Assurance attachment, every renewal date). The consolidation or termination route must be established (move to the buyer's EA at next true-up, terminate at the acquired entity's anniversary, run in parallel through a renewal cycle).
The window is typically before the next anniversary or true-up; running into the next renewal cycle without a consolidated position weakens the buyer's negotiation. The wider Microsoft fiscal year spoke reads the seller-side timing that the buyer can use; the wider Microsoft BATNA spoke reads the alternative-route reading the buyer holds inside the integration window.
The buyer-side artefacts to hold against the M&A event are: the Affiliate-set declaration (every legal entity, every parent-subsidiary relationship, every change-of-control event); the contract inventory (every Microsoft contract on both sides of the event, every renewal date, every Software Assurance attachment); the licence-allocation map (every product, every quantity, every assigned entity, every audit-evidence trail); the TSA position (every TSA service, every TSA period, every Microsoft consent or amendment); the integration plan (every consolidation step, every termination step, every anniversary date).
The wider engagement sits in the Microsoft practice; the aggregated reading list sits in the Microsoft knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The contract framework against which the Affiliate-set change is read.
The contract-framework comparison that frequently sits at the heart of the integration decision.
The true-up window through which the acquired-entity quantities are consolidated.
A senior Admodum Microsoft advisor will read your Affiliate-set declaration, your contract inventory, your TSA position and your integration plan on a private call. Pre-close diligence, post-close consolidation and divestiture separations are all sequenced inside a single engagement.