Transferring Microsoft licenses between corporate entities is governed by the licence transfer clauses of the Microsoft Business and Services Agreement (MBSA) and the Enterprise Agreement, plus the underlying Product Terms. Microsoft's default position is that volume licences are non-transferable except in narrow circumstances — intra-affiliate transfers, M&A transactions where the licences follow the assets, and Microsoft-approved assignments. The practical mechanic for entity-to-entity transfer is therefore a written transfer notice plus Microsoft consent, executed through the Microsoft account team via an amendment or a license-assignment letter. The transfer instrument matters: assignment carries forward existing terms; novation creates a fresh contract relationship with re-priced terms. The novation path is materially more expensive than assignment, so the buyer-side discipline is to position the transfer as an assignment unless novation is the only available path. This article covers the legal mechanics, the consent-seeking posture, the assignment-vs-novation distinction, the seven transfer scenarios that recur in practice, and the 2026 amplifiers that change the consent posture. For the M&A-specific transfer mechanic see the M&A license transfer article.
The starting position on transferring Microsoft licenses between entities: Microsoft's default contract language frames volume licences as non-transferable. The MBSA and the EA both restrict transfer of rights and obligations without Microsoft's prior written consent. In practice this default is permissive in narrow circumstances and restrictive in the rest. The narrow permissive cases are: (a) intra-affiliate transfers within the same EA-affiliate inclusion schedule, (b) M&A transactions where the licences follow the assets being sold, and (c) Microsoft-approved assignments documented in a written amendment or assignment letter. Outside these narrow cases, the buyer-side discipline is to engage Microsoft proactively, position the transfer as an assignment of existing terms rather than a novation, and structure the deal documents so Microsoft consent is a closing condition rather than a post-close hope.
Transfer Microsoft licenses: the seven scenarios that recur in practice
Seven entity-to-entity transfer scenarios recur. Each has distinct mechanics, consent posture, and pricing implications.
| Transfer scenario | Typical mechanic | Microsoft consent posture |
|---|---|---|
| Intra-affiliate transfer (parent to subsidiary or sibling-to-sibling) | Affiliate-inclusion schedule update; no formal transfer required | Schedule update only; no consent needed beyond schedule confirmation |
| M&A acquisition (buyer absorbs target's licences) | Written assignment letter as part of close documents | Microsoft consent required; typically granted |
| Divestiture (target carves out licences to new owner) | Assignment to buyer or termination-and-repurchase | Microsoft consent required; typically granted but at re-priced terms unless negotiated |
| Spin-off (parent to SpinCo) | Assignment to SpinCo as part of spin documents | Microsoft consent required; new-logo pricing posture absent pre-negotiation |
| Internal restructuring (legal-entity reorganisation) | Assignment letter plus updated affiliate schedule | Microsoft consent required where the receiving entity is not on the existing affiliate schedule |
| Joint-venture formation (parent to JV entity) | Assignment to JV with JV-specific affiliate schedule | Microsoft consent required; JV-specific pricing negotiable |
| Receivership / insolvency transfer | Transfer to successor entity through bankruptcy court order plus Microsoft consent | Microsoft consent required; consent posture varies by jurisdiction and successor entity creditworthiness |
Transfer Microsoft licenses: the assignment-vs-novation distinction
The instrument used to transfer the licences shapes the post-transfer commercial position. The distinction between assignment and novation is the single most important commercial decision in the transfer planning.
Assignment carries forward the existing contract terms to the receiving entity
An assignment is a transfer of rights and obligations under an existing contract from one entity to another, without changing the contract terms. The receiving entity steps into the assigning entity's position. The existing pricing, discount tier, anniversary date, SA-coverage, and amendment history all carry forward. From the buyer-side perspective, assignment is the preferred instrument because it preserves the commercial position. Microsoft account teams sometimes propose novation where assignment is available because novation gives Microsoft an opportunity to re-price.
Novation creates a new contract between Microsoft and the receiving entity
A novation terminates the existing contract and creates a new one with the receiving entity. The receiving entity is treated as a new commercial relationship. Pricing, discount tier, anniversary, and SA-coverage are all re-set. Microsoft account teams price novations at then-current list, often without grandfathering the prior discount tier. Novation is materially more expensive than assignment in most scenarios. Novation is appropriate only where the legal structure prevents assignment (e.g., the receiving entity is not yet established at transfer-decision time, or the assigning entity is being dissolved).
The written instrument that documents an assignment
The license assignment letter is the written instrument that documents a transfer between named entities. The letter identifies (a) the assigning entity, (b) the receiving entity, (c) the licences being transferred (by SKU, count, agreement, and anniversary), (d) the effective date, (e) the basis for transfer (M&A, restructuring, spin-off, etc.), and (f) the Microsoft consent acknowledgement. The letter is typically prepared by the LSP or by the customer's licensing advisor and signed by all three parties (assigning entity, receiving entity, Microsoft).
The mechanism for intra-affiliate transfers
Where the receiving entity is already on the existing EA's affiliate-inclusion schedule, no formal transfer is required — the receiving entity is already authorised under the EA. Where the receiving entity is not on the schedule but should be, a schedule update adds the entity. Schedule updates are the lowest-friction transfer mechanism but are only available within the affiliate-inclusion ambit. See the EA affiliates and subsidiaries article for the schedule mechanics.
The omnibus instrument for complex transfers
Where the transfer requires changes beyond a simple assignment — new affiliate schedule, modified scope of licences transferred, partial assignment with retained entitlements — the cleanest instrument is an amendment to the existing agreement. The amendment specifies the transfer terms, the receiving entity's affiliate status, the licence-scope split, and any consequential changes (Unified Support tier, MACC, Copilot commitments). Amendments require Microsoft signature but are more flexible than assignment letters.
Transfer Microsoft licenses: the consent-seeking posture
Microsoft consent is required for most entity-to-entity transfers. The posture used to seek consent materially shapes the outcome.
- Engage early. Microsoft consent is a 4-8 week process for straightforward transfers, 8-16 weeks for complex ones. Engagement should start at the transfer-decision moment, not at the transfer-execution moment. Late engagement creates calendar pressure that Microsoft account teams use to extract pricing concessions.
- Position the transfer as assignment, not novation. The default framing should be assignment with carry-forward terms. Novation should only be accepted where the legal structure makes assignment unavailable.
- Anchor the consent ask to a contractual basis. Most EAs contain transfer language that is permissive in specific circumstances (M&A, restructuring, affiliate inclusion). The consent ask should reference the relevant transfer clause and frame the transfer as falling within the permissive scope.
- Document the M&A or restructuring basis. Where the transfer arises from M&A or restructuring, the deal documents (SPA, merger agreement, restructuring plan) should be summarised in the consent request. Microsoft account teams require a documented basis before recommending consent.
- Negotiate the consent as a deal-document workstream. Where the transfer is consequential (M&A close, spin completion), the consent should be a closing condition or a deal-document workstream rather than a post-close hope. Post-close engagement gives Microsoft material leverage.
- Escalate appropriately when needed. Where the front-line account team is unresponsive or extractive, escalation to the regional Microsoft commercial leadership often produces faster and more favourable consent decisions. The escalation should be measured but firm.
License transfer between entities? The assignment-vs-novation framing and consent posture are the leverage moves.
30-minute scoping call. License-transfer engagements are standard advisory work.
2026 amplifiers shaping license transfer posture
Three 2026 dynamics change the license-transfer posture this cycle.
The EA tier-collapse pricing structure makes the cost difference between assignment (preserving an existing tier) and novation (re-priced at receiving-entity volume in the new tier grid) materially larger than at any prior cycle. The 2026 calculus favours assignment more strongly than the pre-2026 calculus did.
The CSP grace-period elimination of April 2026 creates new transfer scenarios for entities that need to move from CSP to EA / MCA-E mid-cycle to avoid the cancellation-fee posture. The transfer mechanics for CSP-to-EA mid-cycle migration are non-trivial; see the migration-planning angle below.
The Agent 365 framework and the Copilot Studio 2026 mechanism introduce new commitment instruments that have specific transfer-portability provisions. Where an entity transferring licences also carries Copilot or Agent 365 commitments, the commitment-portability mechanics should be addressed in the transfer instrument explicitly — Microsoft default position is that Copilot commitments are entity-specific rather than transferable.
Transfer Microsoft licenses: the pre-transfer discipline
The pre-transfer discipline determines the transfer cost. Six practices recur in mature pre-transfer planning.
- Audit the transferred licence position. The transferring entity should run a deployed-vs-purchased audit on the licences being transferred. Differences identified pre-transfer are addressed in the assignment letter; differences identified post-transfer become receiving-entity audit exposure. See the licence-position audit article.
- Map SA-coverage and benefit balances. SA-coverage on transferred licences should be enumerated — including residual Planning Services Days, Training Vouchers, step-up rights, and any Home Use Program allocations. The mapping ensures these benefits transfer cleanly. See the deployment-planning SA article.
- Document the SKU and product mix. The assignment letter should specify the SKU-level seat count and product mix being transferred, not just the aggregate licence count. SKU-level specification prevents post-transfer disputes about what was transferred.
- Specify the receiving entity's affiliate status. Whether the receiving entity is on the existing affiliate-inclusion schedule, being added to it, or starting a new schedule should be specified in the transfer instrument.
- Address commitment-instrument portability. MACC, Copilot, and Unified Support commitments should be explicitly addressed in the transfer instrument. Default Microsoft position is that these are entity-specific; portability requires negotiation.
- Build in escape valves for over-allocation. Where the transferred licence count materially exceeds the receiving entity's actual need, the assignment instrument should allow proportionate reduction at the next anniversary rather than locking the receiving entity into surplus commitment.
The single highest-leverage move in license transfer is to frame the transfer as an assignment of existing terms with no re-pricing, anchored in the EA's transfer clause and supported by the deal documents that establish the transfer basis. Microsoft account teams accept this framing where the customer is articulate and the deal documents are clear. Where the framing is unclear or the deal documents are absent, the default Microsoft position is novation with re-priced terms, which is materially more expensive. Independent advisory engages on license transfer as a discrete workstream that pairs with M&A close, restructuring, spin-off, or affiliate-restructuring engagements. The engagement typically runs 4-12 weeks depending on transfer complexity.
The Microsoft Negotiations briefing
Monthly. Microsoft license transfer mechanics, assignment-vs-novation discipline, M&A integration intelligence, 2026 inflection-point updates. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the license-transfer discipline next
License transfer pairs with the broader M&A and restructuring framework. The M&A license transfer article covers the M&A-specific assignment mechanics; the M&A playbook covers the broader transaction context; the EA affiliates article covers the affiliate-inclusion schedule mechanic; the divestiture playbook covers carve-out transfer scenarios; the spin-off playbook covers SpinCo transfer scenarios; the post-merger integration article covers post-transfer combined-entity discipline; the EA negotiation pillar covers the broader contract context; the contract advisory service is the productised assignment-and-amendment engagement; the EA strategy service is the productised renewal-cycle engagement; the EA renewal checklist is the cadence guide. For organisations planning entity restructuring or M&A transfer, the scoping call is the direct engagement channel.