Microsoft licensing divestiture is structurally harder than acquisition consolidation because the licensing position has to be split between two surviving entities with separate post-close contractual relationships with Microsoft. The split runs across four artefact categories: SKU-level seat allocation (which users move with the carve-out entity), SA-coverage transfer (does the carve-out entity inherit the SA-coverage on its allocated licences?), commitment apportionment (how does MACC, Copilot, and Unified Support split?), and the contractual instrument itself (carve-out entity continues under a Transition Services Agreement, gets its own new EA / MCA-E, or moves to CSP). Microsoft account teams will typically push for the carve-out entity to land on a new MCA-E at a higher unit-price than the seller's existing EA tier, because the carve-out is a structurally weaker negotiation position. The buyer-side discipline for the carve-out entity is to engage advisory before close, negotiate the carve-out licensing terms inside the Transition Services Agreement, and use the close-date as the anchor for a multi-year price-protection negotiation. The companion M&A integration playbook covers the broader programme context.
The starting position on EA splitting: most divestitures address the Microsoft licensing position as a Transition Services Agreement (TSA) line-item rather than a substantive workstream. The seller agrees to continue providing M365, Azure, and ancillary Microsoft services to the divested entity for a 6-12 month transition window; the divested entity is then expected to "stand up its own licensing" before the TSA expires. That framing is operationally clean but commercially harmful for the divested entity: it lands in an inherently weak negotiation position at the worst possible moment (under deadline pressure, with a TSA-expiry forcing function, against a Microsoft account team that knows the timeline). A more disciplined approach treats Microsoft licensing divestiture as a commercial workstream from announcement, with deliverables on both seller-side and buyer-side that are negotiated before close.
Microsoft licensing divestiture: the four split categories
The licensing split runs across four artefact categories. Each has its own mechanic, its own timing constraint, and its own commercial leverage profile.
| Split category | Mechanic | Timing constraint | Commercial leverage |
|---|---|---|---|
| SKU-level seat allocation | Identify which users and devices move with the carve-out entity; allocate the seat counts at the EA SKU level | Must be locked before TSA execution | Affects both seller post-close volume and buyer entry-point pricing |
| SA-coverage transfer | Document SA-coverage status, step-up rights, and benefit-redemption history for the allocated licences | Must be documented before close; transfer mechanic varies by deal structure | Carve-out entity may lose SA-coverage if mechanic is mis-handled |
| Commitment apportionment | Split MACC, Copilot, Unified Support across seller and carve-out positions | Microsoft consent required; engage account team early | Strongest leverage moment is during deal negotiation, not after |
| Contractual instrument | Decide whether carve-out runs on seller's contract via TSA, gets a new EA, moves to MCA-E, or moves to CSP | Decision must precede TSA execution; instrument must be live before TSA expiry | Defines the multi-year commercial trajectory for the carve-out entity |
Microsoft licensing divestiture: SKU-level seat allocation
The seat allocation determines which entitlements travel with the carve-out entity. The allocation is a deal-document exhibit, not a post-close operational task.
- User-mapping inventory. The carve-out user population is mapped at user-by-user granularity to the EA SKU they currently consume. The mapping must reconcile to the seller's M365 admin centre and Azure AD records.
- SKU-level allocation. Each affected SKU (M365 E3, E5, Frontline F1/F3, Project, Visio, Power Platform, Dynamics) is allocated between the seller's residual position and the carve-out entity's new position.
- Step-up-right allocation. If the seller has step-up rights from E3 to E5 (or to E7 in 2026), the allocation must specify which entity inherits the step-up rights for which licences. Mis-allocation forfeits the step-up rights for the entity that loses them.
- Server licensing allocation. Windows Server, SQL Server, and other server SKUs are allocated based on which infrastructure is moving. SA-coverage on the server licences must be preserved through the allocation.
- Reserved Instance and Savings Plan allocation. Azure RIs and Savings Plans are not generally transferable between Microsoft tenants. The allocation must address what happens to existing RIs (typically: seller retains, carve-out builds new) and the commercial implications for both sides.
Microsoft licensing divestiture: SA-coverage transfer
SA-coverage transfer is the most-frequently-mishandled mechanic in EA splits. SA-coverage attaches to the licence, but the transfer requires explicit documentation in the deal documents.
Pull the SA-coverage detail from VLSC before close
The seller's VLSC report generates the SA-coverage baseline. The baseline documents which SKUs carry SA, the SA expiry dates, the unused SA benefits (Planning Services Days balance, e-learning entitlement, HUP eligibility), and any SA step-up rights. The baseline must be agreed between seller and buyer as a deal-document exhibit, not an operational handover artefact.
Map SA-coverage at the SKU + entity level in the deal documents
The deal documents should specify which SA-coverage transfers with the carve-out entity. The allocation should mirror the seat allocation: SA-coverage on E3 licences moves with the E3 licences that move with the carve-out users. Step-up rights, Planning Services Days balance, and other transferable SA benefits should be allocated proportionally or by an explicit deal-negotiated split.
Get Microsoft consent on the SA-transfer pathway before close
Microsoft account-team consent is generally required for SA-coverage transfer between tenants. The consent should be sought as part of the carve-out negotiation, not after the carve-out entity is operational. Microsoft account teams have material discretion on the transfer mechanic; engaging before close preserves leverage that disappears post-close. The license-transfer mechanics article covers the broader consent posture.
Document SA transfer in the new EA / MCA-E / CSP contract for the carve-out entity
When the carve-out entity stands up its own contract (new EA, new MCA-E, or new CSP), the SA-coverage from the seller's prior position must be documented in the new contract as an inheritance from the prior position. Without explicit documentation, Microsoft will frequently treat the new contract as a fresh start and the SA-coverage as not-applicable. Documenting the inheritance preserves the SA-benefit value.
Re-pull VLSC for both entities at 90 and 180 days post-close to verify
The carve-out entity should re-pull its VLSC report at 90 and 180 days post-close and verify that the SA-coverage is correctly documented on the new entity's licences. Microsoft licence-management systems frequently fail to propagate the SA-coverage transfer correctly on the first attempt; the audit catches the gap before SA benefits are forfeited.
Microsoft licensing divestiture: MACC, Copilot, and Unified Support apportionment
Commitment apportionment is the highest-leverage and highest-risk mechanic in the divestiture. The commitments are the contractual instruments Microsoft uses to lock-in revenue; splitting them is structurally adversarial to Microsoft's commercial position.
- MACC apportionment. The seller's MACC commitment is generally not transferable to the carve-out entity as a partial commitment. Three pathways are common: seller retains the full MACC commitment and provides Azure services to the carve-out through the TSA window (carve-out builds its own MACC at TSA expiry); seller and Microsoft negotiate a MACC-reduction for the seller proportionate to the carve-out volume; Microsoft and the carve-out negotiate a new MACC for the carve-out at favourable terms as a "new logo" customer. See the MACC negotiation pillar for the underlying mechanics.
- Copilot commitment apportionment. Copilot for M365 seat commitments and Copilot Studio CCCU/ACU capacity reservations follow a similar pattern. Where the seller has committed Copilot seats to users who are moving with the carve-out, the seller has stranded commitment exposure that has to be re-negotiated with Microsoft. The carve-out has Copilot adoption needs but no contracted position. Reference the Agent 365 framework for the broader AI-product portfolio context.
- Unified Support apportionment. Unified Support is calculated as a percentage of contracted Microsoft spend. The carve-out reduces the seller's contracted spend, which should reduce the seller's Unified Support fee at the next anniversary; the carve-out itself starts at zero Unified Support and has to either contract its own tier or operate without enterprise support. See the Unified Support 2026 pillar for the tier mechanics.
- Reserved Instance apportionment. Azure RIs and Savings Plans are typically left with the seller. The carve-out's Azure consumption shifts from RI-coverage to pay-as-you-go at TSA expiry, which represents a material cost step-up that should be modelled in the carve-out's post-TSA budget.
Carve-out entity facing TSA expiry without negotiated post-TSA pricing? The leverage moment is before close, not after.
30-minute scoping call. Divestiture-side Microsoft licensing is standard advisory work.
Microsoft licensing divestiture: choosing the carve-out's contractual instrument
The carve-out entity's contractual instrument at TSA expiry is the most consequential commercial decision in the divestiture. Four pathways are typical.
The carve-out establishes its own Enterprise Agreement, typically at "new logo" terms unless pre-negotiated as part of the divestiture deal. Strongest pathway if the carve-out is large enough to qualify for EA (500+ users or $1M+ committed spend), has predictable headcount, and wants traditional volume-licensing terms. The pre-negotiation of pricing exhibits inside the divestiture deal is the leverage moment.
The carve-out moves directly to Microsoft Customer Agreement for Enterprise. Modern pathway, more flexible than EA, but loses some of the predictable-pricing protection that EA carries. Best fit if the carve-out is mid-market or expects volatile headcount in the post-divestiture period.
The carve-out moves to Cloud Solution Provider via an LSP or direct reseller. Lower commitment floor, monthly billing flexibility, but typically higher per-seat unit cost and exposure to the post-2026 CSP grace-period elimination. See the CSP grace-period pillar for the cancellation-window mechanics that changed in April 2026.
The carve-out runs M365 via CSP for flexibility and Azure direct via MCA / MACC for committed-spend discounts. Optimal for organisations with predictable Azure spend and volatile M365 headcount. Adds operational complexity but captures the commercial strengths of both channels.
2026 amplifiers shaping divestiture licensing
Three 2026 dynamics affect divestiture timing and structure this cycle.
- EA tier-collapse repricing. The seller's residual EA position after the carve-out is at a lower volume, which may drop the seller into a less-favourable tier in the post-2026 tier-collapse pricing structure. The seller's post-divestiture renewal should model the tier outcome at the reduced volume; in some cases, the carve-out is the trigger for the seller to consider its own consolidation strategy with other portfolio companies.
- July 2026 price-increase asymmetry. Carve-outs that close after July 2026 enter the higher M365 price grid as new contracts. Where carve-out timing has any flexibility, pulling the carve-out's contractual stand-up to before July 2026 (even if operational TSA continues longer) is worth modelling. The July 2026 pricing pillar covers the increase scope.
- CSP grace-period elimination impact. The April 2026 elimination of the 7-day CSP grace period changes the cancellation mechanics for carve-out CSP positions. Carve-outs moving to CSP at TSA expiry should structure the subscription terms with awareness that mid-term cancellation is now contractually constrained. The pillar above is the reference.
Microsoft account teams frequently treat carve-out entities as "new logo" customers post-divestiture, which means standard "new logo" pricing rather than any inheritance from the parent's negotiated tier. The carve-out entity has limited counter-leverage post-close because the carve-out is operationally locked in to the Microsoft ecosystem during the TSA window. The leverage moment is pre-close, inside the divestiture deal documents, where the carve-out's post-TSA pricing can be specified as a deal exhibit. Independent advisory engaged before close has the strongest negotiating posture; engagement after TSA expiry frequently arrives too late to recover the pre-close leverage window.
The Microsoft Negotiations briefing
Monthly. Divestiture carve-outs, M&A licensing integration, post-close negotiation leverage, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the divestiture-licensing discipline next
Divestiture licensing pairs with the broader M&A and renewal-cycle framework. The M&A integration playbook covers the broader programme context; the license transfer guide covers the assignment mechanics; the licensing diligence pillar covers the pre-close artefact set; the consolidation playbook covers the inverse scenario from the acquirer's perspective; the EA negotiation pillar covers the broader renewal-cycle context; the contract advisory service is the productised carve-out and amendment engagement; the EA strategy service is the productised renewal-cycle engagement; the EA renewal checklist tool is the T-12 to T-3 cadence guide. For organisations executing a divestiture, the scoping call is the direct engagement channel; the free EA assessment is the broader entry channel.