Microsoft Enterprise Agreements require careful handling during mergers, acquisitions, and divestitures. Transferring or novating an EA to a new corporate entity, or splitting one for a spin-off, is a complex yet critical process. Done correctly, EA novation preserves licence rights and avoids compliance gaps, while proactive planning can optimise costs significantly.
When companies merge or split, Microsoft licensing does not automatically follow the organisational change. An Enterprise Agreement is a contract tied to specific legal entities. Without proper adjustments, a merger could leave the new combined company using licences it is not legally authorised to use, or a divested unit without the licences it needs to operate.
Software vendors, including Microsoft, closely monitor M&A activity and may initiate audits during these transitions. The financial exposure from licensing non-compliance can be material enough to affect deal economics, and should be assessed alongside other integration risks during the due diligence phase.
Without proper novation, the acquiring entity may be using Microsoft software under a contract belonging to a dissolved or divested entity. This is a direct licence violation that Microsoft can enforce through audit claims and back-billing.
M&A creates opportunities to combine volumes for higher discount tiers (Level C or D pricing), eliminate redundant licences, and renegotiate terms. Failing to plan means missing savings worth hundreds of thousands annually.
M&A events are known audit triggers. Microsoft typically reaches out for a licence review within 12–18 months of a major merger, acquisition, or divestiture. Proactive compliance preparation is essential.
EA novation processing takes 2–3 months. Without advance planning, you may close the deal with no formal licence authority for the surviving entity, creating a compliance gap that Microsoft can exploit.
EA Novation refers to the formal transfer of an entire Enterprise Agreement, along with its associated rights and obligations, from one legal entity to another. In an acquisition, this typically means assigning Company A’s EA to the acquiring Company B, so B becomes the new customer on that contract.
Licence transfer is a related but distinct concept: the movement of specific licence entitlements from one organisation to another (for example, transferring certain Windows Server licences to a spun-off business unit).
Perpetual licences: Microsoft’s volume licensing policies permit transfers in the context of mergers, consolidations, or divestitures without special permission, provided licences are fully paid and perpetual. Subscription licences: Microsoft 365 seats, Azure subscriptions, and any unpaid ongoing EA subscriptions cannot be transferred. The new entity must acquire its own subscriptions or negotiate a new agreement. Software Assurance: SA benefits typically do not transfer with perpetual licences. The new entity may lose update and support coverage unless they negotiate continuation or purchase SA separately. Formal process required: Even for permitted transfers, you must notify Microsoft and complete their official transfer forms. An informal arrangement or verbal confirmation is not sufficient.
An EA novation can move contract ownership, but it does not convert non-transferable licences into transferable ones. Plan for subscriptions and SA separately from the perpetual licence transfer. Read Transferring Volume Licences and Cloud Subscriptions.
In a merger or acquisition scenario, CIOs and CTOs should first assess the existing EAs of all parties: when do they expire, what products are covered, and how many users or devices are licensed? If the acquired company continues as a wholly owned affiliate, Microsoft typically allows it to operate under its existing EA until the next renewal. However, if the acquired entity is being absorbed or dissolved, an EA novation is required.
Inventory every Microsoft agreement across both organisations: EA enrolments, Server and Cloud Enrolments (SCE), Microsoft Customer Agreements (MCA), CSP subscriptions, and any MPSA or Open Value agreements. Document expiry dates, pricing levels, product mix, and user counts. This baseline is essential for planning the integration approach.
Inform your Microsoft account manager as soon as the M&A deal is announced. Early communication opens options: short-term EA extensions, bridge agreements, bespoke novation timelines, and potentially improved pricing for the combined entity. Microsoft prefers to be involved early rather than discovering changes through an audit.
Complete Microsoft’s Contract Novation Agreement form, listing all licences being novated and the reason (merger, consolidation, acquisition). Both companies and Microsoft must sign. Schedule the novation close to the deal closing date to minimise time in limbo. Allow 2–3 months for processing; form errors or delays are common.
If both entities have EAs with different expiry dates, decide whether to run parallel EAs until co-terming at renewal, or negotiate early termination of one EA. Some organisations negotiate a short bridge EA (12-month renewal instead of the usual 3-year) to align with post-merger integration timing, avoiding long commitments while user counts and needs are in flux.
Company B acquires Company A. Company A’s EA has 18 months remaining with 1,000 licensed users; Company B’s EA covers 5,000 users. Rather than paying termination fees or duplicating coverage, Company B novates Company A’s EA and runs both in parallel until co-terming at renewal. At renewal, the combined 6,000 seats qualifies for Level D pricing, a higher discount tier than either company held individually. The consolidation saves approximately $180,000 annually in reduced per-seat costs, plus eliminates redundant licences identified during the integration assessment.
Divestitures create a mirror-image challenge. The departing unit (“NewCo”) needs to stand on its own feet with Microsoft licences, and the parent company wants to reduce its licence count accordingly.
Microsoft’s rules permit licence transfers to an unaffiliated third party in connection with a divestiture, provided the licences are perpetual and fully paid. The parent company identifies which licences NewCo needs, submits a Perpetual Licence Transfer Form to Microsoft detailing these entitlements and citing the divestiture event, and Microsoft acknowledges the transfer.
Fully paid perpetual licences (Windows, Office, SQL Server, etc.) can be transferred to NewCo using Microsoft’s official transfer form. NewCo receives the licence entitlements but not Software Assurance benefits, which must be purchased separately.
Microsoft 365, Azure, Dynamics 365, and other subscription services cannot be split or handed over. NewCo must establish its own subscriptions, either a new EA (if 500+ seats), CSP arrangement, or MCA. Budget for these as a separate line item in the divestiture plan.
SA benefits generally do not transfer with perpetual licences. NewCo loses upgrade rights, deployment planning services, and training vouchers unless they negotiate SA continuation with Microsoft or purchase it separately at the point of transfer.
In many divestitures, the parent and NewCo sign a TSA allowing the parent to continue providing IT services, including software use, for a limited time (typically 6–12 months post-close). During that window, NewCo should procure its own licences or EAs. This transition period is critical, giving NewCo time to negotiate a new agreement rather than rushing and overpaying.
A divestiture is a chance to right-size the EA. If 20% of your users are leaving, you want to reduce EA coverage by a similar proportion. EA terms include clauses that Microsoft will work “in good faith” to accommodate major organisational changes. Inform Microsoft of the divestiture and request a contract adjustment to drop licences at the next anniversary. Microsoft may not automatically reduce your annual bill unless you explicitly ask. Any reduction should be proportionate and well-documented.
A global technology company divested its professional services division (1,200 employees) to a private equity buyer. The parent held a Level C EA covering 8,500 users. They transferred 1,200 perpetual Windows and Office licences to NewCo using Microsoft’s transfer form, and negotiated a 9-month TSA for Microsoft 365 and Azure services. During the TSA period, NewCo established its own EA at Level A pricing (1,200 seats). The parent simultaneously negotiated a contract adjustment reducing their EA by 1,200 seats at the next anniversary, saving $340,000 annually. NewCo’s per-seat cost was approximately 18% higher than the parent’s Level C rate, a predictable cost differential factored into the divestiture financial model.
M&A events can either increase or decrease your Microsoft spend dramatically. Smart planning minimises unbudgeted costs.
| M&A Scenario | Licensing Approach | Cost Impact |
|---|---|---|
| Two companies merge (both have EAs) | Run parallel EAs until co-term, then consolidate | Combined volumes may qualify for higher discount tier (Level C/D); eliminate redundant licences |
| Large acquires smaller company | Absorb acquired users into acquirer’s EA | Minimal incremental cost if acquirer has headroom; >10% change triggers good-faith adjustment clause |
| Divestiture / spin-off | Transfer perpetual licences; NewCo signs own EA/CSP | NewCo faces 15–20% higher per-seat costs at lower pricing level; parent saves by right-sizing |
| Post-merger duplicate licensing | Rationalise and consolidate at renewal | Consolidating into one EA simplifies management and maximises discounts; check early termination fees |
Compliance is equally critical. Using software without a proper licence transfer is a violation, even if it is an honest oversight due to M&A complexity. Microsoft considers mergers and spin-offs as trigger events for audits. To avoid surprises, conduct an internal licence audit during the M&A process.
In the first 12–18 months post-M&A, expect Microsoft scrutiny. Perform your own internal true-up before Microsoft does it for you. Proactive compliance planning gives you negotiating leverage; reactive audit response gives Microsoft the leverage.
A healthcare company acquired a regional competitor, combining two organisations with a total of 4,200 Microsoft-licensed users. During integration, an internal licence audit identified a 380-seat compliance gap in Windows Server licences (the acquired company had been under-licensed for two years without realising). Rather than waiting for Microsoft to discover the gap, the combined entity purchased the additional licences proactively at negotiated EA rates, including them in a broader contract consolidation discussion. When Microsoft initiated a licence review 14 months later, the company demonstrated full compliance with documented evidence of the proactive remediation, avoiding estimated penalty exposure of $420,000 that would have applied under a formal audit finding.
Cloud subscriptions present unique challenges in M&A that differ fundamentally from perpetual licence transfers. While perpetual licences can be novated or transferred using Microsoft’s established processes, cloud services are tied to specific tenants, billing accounts, and subscription agreements that do not transfer between legal entities.
Subscriptions cannot be transferred. Coordinate a cut-over date when the new entity starts using its own tenant. During transition, the parent can keep users on its tenant via a TSA with a strict time limit.
Azure subscriptions are tied to specific tenants and billing accounts. In a merger, you may need to transfer subscriptions between tenants using Azure’s subscription transfer process. In a divestiture, NewCo needs its own Azure billing account.
Like M365, Dynamics subscriptions are non-transferable. The new entity needs its own agreement. Data migration planning is equally important: licensing and data must move together.
After a merger, running multiple Microsoft tenants creates operational complexity and security gaps. Plan tenant consolidation early, but do not rush it. Identity migration, mailbox moves, and SharePoint transfers are major projects. Budget for a 6–12 month co-existence period where both tenants operate in parallel. This requires inter-tenant federation and may involve temporary duplicate subscriptions.
Read our comprehensive guide to Consolidating Tenants and Contracts in M&A.
Even well-managed M&A transactions frequently encounter Microsoft licensing pitfalls that create compliance gaps, unexpected costs, or missed optimisation opportunities.
Microsoft licences do not follow corporate ownership changes automatically. Without formal novation or transfer forms, the surviving entity has no legal right to use the acquired company’s software, even if the acquisition is complete and the original entity has been dissolved. This is the single most common and most expensive M&A licensing mistake.
Teams that successfully transfer perpetual licences often assume the same process applies to Microsoft 365 and Azure subscriptions. It does not. Subscription services require separate procurement for the new entity, creating budget gaps that surface weeks after close when IT teams discover they cannot simply “move” M365 seats.
EA novation takes 2–3 months to process. If you start the paperwork on closing day, you have a multi-month compliance gap where the surviving entity is using software without contractual authority. Start the novation process during the due diligence phase, not after closing.
Parent companies frequently continue paying for licences that departed with the divested unit. Without an explicit contract adjustment request to Microsoft, the EA continues at the pre-divestiture commitment level. You must actively negotiate the reduction. Microsoft will not volunteer it.
SA benefits have specific coverage periods that may not align with the novation timeline. If SA lapses during the transfer process, the new entity loses upgrade rights and may need to purchase new licences at current pricing rather than exercising upgrade entitlements. Coordinate SA renewal dates with the novation schedule to avoid this expensive gap.
Organisations often underestimate the complexity of tenant migration that accompanies an EA novation. Moving users between Microsoft 365 tenants requires careful planning for identity management, mailbox migration, SharePoint content, Teams channels, and security policies. The licensing transfer and the technical migration are separate workstreams that must be coordinated. Completing one without the other creates either compliance gaps or operational disruption.
Redress Compliance provides independent, vendor-neutral advisory on EA novation, licence transfers, and contract optimisation during mergers, acquisitions, and divestitures. Fixed-fee engagement models with no Microsoft partnerships or referral arrangements.
Microsoft Contract Negotiation Service →Add Microsoft (and all major software vendor) licensing to your M&A due diligence checklist from day one. Assess the target’s EA terms, pricing levels, product entitlements, compliance posture, and any audit history. Licensing liabilities can be material. An undisclosed compliance gap in the target company becomes your problem post-acquisition.
Perform a detailed licence audit on both sides of the transaction. Document all entitlements and keep copies of all EA contracts, transfer forms, and novation agreements. This provides a clear baseline and evidence in case of future disputes or Microsoft audits.
Budget for the new entity to subscribe to Microsoft 365, Azure, and Dynamics independently. Include subscription procurement in the transition timeline. These cannot be novated and require their own agreements. Factor in the higher per-seat costs that smaller entities face at lower EA pricing tiers.
M&A is an opportunity to optimise contracts. A larger combined entity can secure deeper discounts or incentive funds from Microsoft. A smaller spun-off entity can negotiate starter discounts or favourable terms. If the combined entity crosses a pricing level threshold (e.g., from Level B to Level C), quantify the per-seat savings and ensure Microsoft applies the new tier from the first consolidated renewal. Confirm it in writing during the consolidation negotiation.
If a major merger is happening mid-EA, consider negotiating a one-year renewal instead of a full three-year term, so you can consolidate or adjust once the integration settles. A bridge EA provides flexibility without locking the combined entity into terms negotiated before the full scope of the integration was understood.
The first 12–18 months post-M&A are high-risk for unintentional non-compliance as systems integrate. Monitor licence usage against entitlements monthly. If you discover gaps, resolve them proactively with Microsoft through purchasing or adjustments. Assign a dedicated resource to track licence entitlements across the transitioning entities until full integration is confirmed.
An EA novation is the formal transfer of an entire Microsoft Enterprise Agreement from one legal entity to another. The acquiring or surviving company steps into the shoes of the original customer on the contract. This involves signing a novation agreement with Microsoft’s approval, ensuring the new entity can continue using licences under the existing EA and assumes all responsibilities including payments and compliance obligations.
You cannot merge two contracts mid-term, but you have options. You may maintain separate EAs until one expires, or negotiate early termination of one and move users onto the other via true-up. The most common approach is running parallel EAs until renewal, then consolidating into a single new EA for the combined company. At renewal, Microsoft calculates pricing based on total users and devices, which may qualify for a higher discount tier.
Identify which perpetual licences NewCo needs and transfer them using Microsoft’s Perpetual Licence Transfer Form. NewCo will need its own EA (if 500+ seats) or CSP/MCA arrangement for ongoing needs and cloud services. Use a Transition Services Agreement to bridge the gap, allowing the parent to cover NewCo’s licensing for 6–12 months while the new entity establishes its own agreements.
Microsoft’s standard agreements pre-authorise transfers in specific M&A scenarios (mergers, acquisitions, divestitures, transfers to affiliates). You do not need special permission, but you must notify Microsoft and complete their official transfer form. For any scenario outside M&A (e.g., selling licences commercially), Microsoft’s consent is required and rarely granted. Always follow the formal process.
Cloud subscriptions cannot be split or transferred like perpetual licences. NewCo must establish its own subscriptions. Coordinate a cut-over date, use a TSA to bridge the transition period, and have NewCo work with Microsoft or a licensing partner to sign a new agreement. Budget for NewCo’s subscription costs as a separate line item. Per-seat costs will likely be 15–20% higher at a lower pricing tier than the parent’s EA rate.
M&A events are known audit triggers. Microsoft commonly reaches out for a licence review within 12–18 months of a major transaction. To prepare, perform your own internal true-up during the M&A process, ensure accurate records of all transferred and acquired licences, and address any compliance gaps proactively. Resolving shortfalls before an official audit gives you far better negotiating leverage.
Microsoft’s EA requires a minimum of 500 seats. If NewCo falls below this threshold, it can use a Cloud Solution Provider (CSP) programme or Microsoft Customer Agreement (MCA) instead. CSP offers month-to-month flexibility but at slightly higher per-user pricing. If NewCo is close to 500 seats and expects growth, Microsoft may still allow an EA. They have been flexible for near-threshold cases, particularly to retain the relationship with a newly independent company.
Independent, vendor-neutral advisory on EA novation, licence transfers, and contract optimisation during mergers, acquisitions, and divestitures.