Mergers, acquisitions, and divestitures create hidden Microsoft licensing landmines: duplicate tenants, overlapping EAs, compliance gaps, and double-payment traps. This guide covers contract review, tenant consolidation, EA vs CSP decisions during integration, licence transfer rules, divestiture carve-outs, and a step-by-step playbook to avoid millions in unnecessary costs.
Part of the Microsoft Licensing Knowledge Hub. Related M&A guides include Consolidating M365 Tenants Without Double Licensing, EA Novation and Transfer Strategies, and Licence Carve-Outs in Divestitures.
M&A events trigger hidden IT challenges, and Microsoft licensing is one of the most expensive. Two organisations combining inherit overlapping contracts, duplicate licences, and separate cloud tenants. Without proactive management, this means double payment, contract conflicts, or compliance gaps. When a company splits, determining which entity keeps which licences is equally complex.
The scale of the problem is significant. A typical mid-market acquisition brings two separate Microsoft 365 tenants, two Enterprise Agreements with different renewal dates and discount levels, overlapping perpetual licence entitlements for Windows Server and SQL Server, and separate Azure subscriptions with independent consumption commitments. Every day these remain unconsolidated, the combined entity pays more than it should.
Double-paying for licences: Running two tenants with overlapping M365 subscriptions means paying twice for the same users during integration, potentially for months or even years if not managed. For a 5,000-user acquisition, that is $1.5 to $2 million per year in duplicate licensing costs.
Contract conflicts: Different EA terms, renewal dates, discount levels, and special pricing across two organisations create a contractual maze that Microsoft will exploit at renewal. Misaligned true-up dates mean the acquiring company may face unexpected compliance charges.
Compliance gaps: The acquired company's systems may not be properly licensed under your agreements. Microsoft is known to scrutinise companies post-merger. Audit risk increases significantly in the 12 to 24 months following a transaction.
Lost volume discounts: Maintaining separate agreements means neither entity benefits from the combined volume. Consolidating unlocks better pricing tiers and negotiation leverage that neither organisation could access independently.
Microsoft frequently targets recently merged companies for compliance reviews. Getting your licensing house in order early, ideally within 90 days of close, is critical to avoiding expensive true-up demands. The post-merger period is when Microsoft has the greatest leverage: you are operationally distracted, your licensing position is unclear, and your contracts may have gaps that the acquired entity's systems fall through. See our Microsoft Audit Defence Service.
The first step in any M&A licensing workstream is a complete inventory of both organisations' Microsoft contracts. This must happen during due diligence, not after close. Licensing liabilities discovered post-close become the acquiring entity's problem, and they can be substantial.
Catalogue all active contracts. Both organisations likely have EAs, Microsoft Customer Agreements, or CSP subscriptions with different end dates and terms. Create a master inventory including contract type, expiry date, enrolled affiliates, user counts, special pricing or concessions, and any amendment letters. Most organisations have more Microsoft contracts than they realise: the core EA, separate Server and Cloud Enrollments, Visual Studio subscriptions, Dynamics 365 agreements, and Azure consumption commitments often exist as independent contracts with different terms.
Check M&A clauses in existing EAs. Microsoft's standard EA includes a clause: if a merger or acquisition changes licence quantity by more than 10%, Microsoft will "work in good faith" to accommodate the change. Leverage this. Engage Microsoft early about adjustments if your user count or IT footprint will change drastically. The key phrase is "good faith," which means Microsoft is not obligated to offer specific concessions but is expected to engage constructively.
Review MBSA affiliate definitions. Check the Microsoft Business and Services Agreement for "affiliate" definitions, usually entities with more than 50% ownership. If the acquired company qualifies as an affiliate, you may bring them under your existing umbrella agreements more easily. This is the simplest path when it applies.
Identify enterprise-wide commitments. Review any company-wide Office 365 or Windows licensing commitments. If you acquired a company with 300 new Windows Servers and your Server and Cloud Enrollment requires Software Assurance on all servers, that acquisition could trigger a massive true-up. Know obligations in advance.
Preserve special pricing and concessions. One company might have negotiated discounted pricing or flexible terms. Strive to preserve those in the combined contract. Do not assume Microsoft will automatically extend the same deals to the new larger entity. You will need to negotiate. See our Microsoft Contract Negotiation Service.
Some Microsoft agreements include termination or transfer clauses triggered by M&A events. In some cases, an acquired company's agreement may be terminable or mergeable, but this is not automatic. Plan for a period managing multiple Microsoft contracts concurrently until you can consolidate at renewal. The EA's standard terms allow Microsoft to review and potentially adjust pricing when the customer undergoes a change of control. Independent advisory ensures this review works in your favour, not Microsoft's.
Tenant consolidation is the most visible and technically complex workstream in a Microsoft M&A integration. Each company typically has its own M365 tenant with its own Entra ID (Azure AD), Exchange Online, Teams, SharePoint, OneDrive, and Intune. CIOs should decide early whether to merge into a single tenant for unified collaboration, reduced admin overhead, and elimination of duplicate licences.
Plan a phased migration. Microsoft does not provide a one-click "merge" button. Migration involves moving users, mailboxes, SharePoint sites, OneDrive data, Teams structures, and Intune device enrollments using third-party tools or Microsoft's cross-tenant migration capabilities. Migrate department by department to minimise disruption. Start with IT and pilot groups to validate the process before migrating business-critical departments. For mid-size organisations, expect 3 to 6 months. Large enterprises with complex SharePoint estates, custom Power Platform applications, and multiple Azure subscriptions may take 6 to 12 months.
Manage licensing during transition. A user being migrated should ideally consume only one licence at a time. Coordinate cutover to ensure you reassign or move licences rather than paying for two licences for the same user in both tenants for an extended period. In practice, there is always some overlap: the user's mailbox must exist in the target tenant before the source mailbox is fully decommissioned. Minimise this overlap window to days, not months.
Consolidate into the surviving entity's tenant. Merge into the tenant tied to the surviving or larger entity's Microsoft agreement. All users will eventually be covered under one subscription contract, enabling volume discount benefits. The surviving tenant retains its configuration, security policies, compliance settings, and application integrations, reducing the migration scope.
Decommission the old tenant promptly. After migration, shut down the acquired company's tenant to stop ongoing licensing charges. Do not forget to migrate Azure services, Power Platform applications, Dynamics 365 environments, and any other resources tied to the old tenant's Entra ID. Orphaned Azure subscriptions under the decommissioned tenant will continue incurring consumption charges until explicitly cancelled.
Consider interim cross-tenant collaboration. During the transition period, users from both tenants need to collaborate. Microsoft's cross-tenant access settings in Entra ID allow shared Teams channels, guest access, and conditional access trust between tenants. Configure these early to maintain productivity while the migration proceeds. This interim state should be time-boxed. Do not let cross-tenant collaboration become a permanent substitute for consolidation.
For mid-size organisations (1,000 to 5,000 users), expect 3 to 6 months for a phased tenant migration. Large enterprises with complex SharePoint estates, custom applications, and multiple Azure subscriptions may take 6 to 12 months. The key is starting the planning process immediately and migrating in waves to minimise business disruption. Every month of delay with dual tenants is a month of duplicate licensing costs. For detailed guidance, see Consolidating M365 Tenants Without Double Licensing.
Once integration begins, the combined software asset pool presents both savings opportunities and compliance risks. Perform an Effective Licence Position (ELP) analysis as soon as possible. Inventory all Microsoft software and subscriptions from both entities and compare against actual usage. This analysis identifies duplicate licences to eliminate, under-licensed deployments to remediate, and shelfware to reclaim.
| Licence Type | Transfer Rules in M&A | Action Required |
|---|---|---|
| Perpetual Licences (Windows, Office, Server CALs) | Can be transferred when companies merge or split | Complete Microsoft's Perpetual Licence Transfer form; maintain documentation for audit defence |
| Cloud Subscriptions (M365, Azure) | Cannot be "transferred" as they are tied to original tenant/contract | Migrate users to surviving tenant; cancel/expire old subscriptions at contract anniversary |
| Software Assurance | Follows the underlying licence; transfers with perpetual licences | Ensure SA benefits (Azure Hybrid Benefit, training vouchers) are preserved post-transfer |
| CSP Subscriptions | Monthly subscriptions can simply be stopped after migration | Cancel after users are migrated; no long-term penalties on monthly CSP |
| EA Subscriptions | Annual true-ups apply; may need to wait for anniversary for adjustments | Negotiate one-time adjustment or keep EA active until expiry, consolidating at renewal |
| Azure Consumption (MACC/MOSA) | Commitments cannot be merged between agreements | Prioritise workload migration to the agreement with better pricing; let smaller commitment expire |
| Dynamics 365 Licences | Environment-specific; tied to tenant and subscription | Plan Dynamics migration early as environments cannot simply be moved between tenants |
Perpetual licence transfers in Volume Licensing programmes like EA and Open are permitted in mergers and divestitures without requiring Microsoft's consent, but you must submit the Perpetual Licence Transfer form and maintain documentation. These transfers do not automatically appear in the Volume Licensing Service Centre (VLSC). Keep records of all transfers as your defence if Microsoft audits the new environment or questions compliance later.
Cloud subscription transfers are not technically possible. M365, Azure, and Dynamics 365 subscriptions are tied to the original tenant and agreement. The migration approach is to provision equivalent licences in the surviving tenant, migrate users and data, and then cancel or allow the old subscriptions to expire. Coordinate the timing carefully to minimise the overlap period where both subscriptions are active.
Software Assurance benefits transfer with the underlying perpetual licences. This is important for organisations using Azure Hybrid Benefit (AHB) to reduce Azure VM costs. If the acquired company has Windows Server licences with active SA, those AHB entitlements transfer to the acquiring entity and can be applied to Azure workloads, potentially saving 40 to 50% on Windows VM compute costs.
Beyond licence transfers, consolidation eliminates duplicate subscriptions (both companies may have separate Power BI, Project, Visio, or Copilot licences), standardises licence editions across the combined user base, and creates opportunities for bundle optimisation. A 1,000-user company at $20/user/month on M365 E3 merging with a 500-user company at $22/user/month can consolidate to a combined rate of approximately $18/user/month at the higher volume tier, saving roughly $48,000 per year on M365 alone. See Transferring Volume Licences and Cloud Subscriptions.
The licensing model decision post-merger is one of the most consequential choices in the integration. The Enterprise Agreement and Cloud Solution Provider model serve different needs, and the right answer often changes during the integration lifecycle.
| Factor | Enterprise Agreement (EA) | Cloud Solution Provider (CSP) |
|---|---|---|
| Commitment | 3-year term with annual true-ups | Monthly or annual; no multi-year lock-in |
| Pricing | Deepest volume discounts; fixed pricing for term | Slightly higher per-seat; may vary |
| Flexibility | Limited flexibility between true-ups | Scale up/down monthly; add or remove users freely |
| Software Assurance | Included for on-premises products | Not included by default |
| Best for M&A | Stable, known environment post-integration | Transition period when headcount and systems are in flux |
| Azure Commitment | MACC with committed spend discounts | Pay-as-you-go or partner-managed commitments |
| Recommendation | Renew/extend EA once integration stabilises | Use CSP during the 12 to 24 month integration period |
The EA provides the best pricing and most comprehensive coverage for a stable organisation. But during the 12 to 24 months of post-merger integration, headcount is uncertain, systems are being consolidated, and licence requirements change month to month. Committing to a 3-year EA during this period risks locking in the wrong quantities at the wrong prices.
CSP provides the flexibility to scale up or down without long-term penalties. Add 500 users this month because you acquired a division. Remove 200 next month because you consolidated systems. CSP accommodates this fluidity without penalty. The trade-off is slightly higher per-seat pricing and no Software Assurance benefits.
Many enterprises adopt a hybrid strategy in M&A: extend the existing EA for 12 months (instead of a full 3-year renewal) to maintain discounts and preserve special pricing, while using CSP for variable needs during the merger. Microsoft can offer custom "bridge" contracts, a one-year extension or interim agreement, if they know a major merger is underway. Do not hesitate to ask. The key is avoiding a full 3-year EA commitment while user counts, systems, and requirements are still in flux. Once integration stabilises (typically 12 to 18 months post-close), re-enter a full EA with the combined organisation's accurate requirements. See EA vs CSP Complete Guide and EA Novation and Transfer Strategies.
Divestitures create their own licensing challenges. The departing unit will eventually need its own Microsoft tenant and contracts, but this does not happen overnight. The parent company must manage a structured separation that maintains licensing compliance for both entities throughout the transition.
Establish a Transition Services Agreement (TSA). Formalise a transition period (typically 6 to 12 months) where the divested entity can legally use the parent company's IT resources, including Microsoft software. Both sides must agree on a hard cutoff date when the new entity secures its own Microsoft agreement. The TSA should specify which Microsoft services are covered, cost allocation during the transition, data residency requirements, and security responsibilities. Without a TSA, both companies risk being in breach of Microsoft's licensing terms from the moment the divestiture closes.
Transfer perpetual licences. Identify which perpetual licences (Windows, Office, Server CALs, SQL Server) need to transfer to the new entity. Volume Licensing programmes like EA and Open allow perpetual licence transfers in divestitures without Microsoft's consent, but you must submit the transfer form. Document every licence transfer meticulously. These records are your primary defence if either entity faces a Microsoft audit in the years following the separation.
New entity starts fresh on cloud subscriptions. Cloud subscriptions cannot be split. The new entity needs its own M365 tenant and subscriptions. Plan a user and data migration to a brand-new tenant. The parent may purchase a short-term CSP subscription on behalf of the new entity to cover them until they sign their own deal. CSP is ideal for this scenario because it requires no multi-year commitment and can be cancelled once the new entity's own agreement is in place.
Carve out Azure resources. Azure subscriptions tied to the parent's tenant must be separated. This involves migrating Azure resources (VMs, databases, storage, networking) to the new entity's tenant and Azure subscription. Azure resource moves between tenants are complex and may require redeployment rather than simple migration. Plan for this workstream to take 2 to 4 months for moderately complex Azure estates.
Do not leave the spin-off in licensing limbo. By the end of the transition period, the new entity either needs its own EA/CSP contract or a continuation arrangement. If they continue using the parent's licences after separation without authorisation, both companies are in breach. Treat this as a project with a hard deadline. See Licence Carve-Outs in Divestitures.
Before the transition period ends, the new entity must have: its own Entra ID tenant configured with security policies and conditional access, its own M365 subscriptions (EA or CSP) covering all users, transferred perpetual licences with completed Microsoft transfer forms, its own Azure subscriptions with migrated resources, its own Dynamics 365 environments if applicable, documented proof of all licence transfers for audit defence, and an independent relationship with Microsoft (new account team assignment, new VLSC access). Missing any of these creates compliance exposure for both the parent and the divested entity.
Microsoft licensing in M&A is not a single event but a sequence of workstreams that must be coordinated across legal, IT, procurement, and finance. The following timeline provides a practical sequence for managing licensing through the transaction lifecycle.
Pre-close (due diligence phase): Inventory all Microsoft contracts from both entities. Identify licence types, quantities, contract expiry dates, special pricing, and any compliance gaps. Quantify the licensing liability: what will it cost to bring the acquired entity into compliance? This number belongs in the acquisition cost model. Flag any Microsoft audit notices or outstanding compliance disputes. Assess the acquired company's Microsoft tenant structure and Azure estate complexity.
Close to Day 30: Notify Microsoft of the acquisition. Engage the account team about the combined licensing position. Establish cross-tenant collaboration settings so users from both organisations can work together during the transition. Begin the Effective Licence Position (ELP) analysis of the combined estate. Identify which EA will serve as the surviving agreement and begin planning the consolidation path.
Day 30 to Day 90: Complete the ELP analysis. Submit any perpetual licence transfer forms to Microsoft. Negotiate interim arrangements (EA extension, bridge contract, CSP for variable needs). Begin the tenant migration project. First wave: IT department and pilot groups. Establish the TSA if a divestiture is involved.
Day 90 to Day 180: Execute the core tenant migration in phases. Decommission migrated users from the old tenant and cancel their licences. Migrate Azure resources to the surviving subscription. Address any compliance gaps identified in the ELP analysis. True-up at the next EA anniversary if applicable.
Day 180 to Day 365: Complete the tenant migration. Decommission the old tenant. Finalise contract consolidation. If using a bridge EA or CSP during transition, begin planning the long-term EA renewal based on the stabilised combined requirements. Conduct a post-migration licence reconciliation to confirm the combined estate is fully compliant.
The most critical window is the first 90 days post-close. Decisions made (or not made) during this period determine whether the integration saves money or creates expensive problems. Engaging Microsoft with a clear plan within the first 30 days signals competence and reduces the risk of Microsoft pursuing aggressive compliance actions during the vulnerable transition period.
1. Inventory and audit early. Catalogue all Microsoft licences and contracts from both entities as soon as an M&A deal is on the horizon. This prevents surprises and identifies overlapping licences to eliminate or compliance gaps to fill. Do not wait until close. The due diligence phase is when licensing liabilities should be quantified and factored into the transaction price.
2. Engage Microsoft with a clear plan. Come to Microsoft with desired contract terms, combined licence counts, and integration timeline rather than reacting to their offers. This keeps you in control and often yields more flexible options like short-term agreements or special pricing. Microsoft's account team will have their own agenda. Your job is to set the agenda first.
3. Consolidate tenants strategically. Merge M365/Entra ID tenants into a single tenant using phased migrations. Consider interim solutions like cross-tenant collaboration setups or temporary dual licensing to maintain business continuity during transition. The target is one tenant, one contract, one set of policies. See our Microsoft Optimisation Services.
4. Use flexible licensing during transition. If uncertainty is high, opt for CSP or short-term agreements to avoid overcommitting. Re-enter a longer EA after the organisation stabilises. If renewing an EA mid-merger, negotiate an opt-out or adjustment clause that accounts for the changing user population.
5. Preserve licence value. Do not let licences go to waste. Reassign licences from retired systems elsewhere in the organisation. For perpetual licences no longer needed, consider reharvesting before deactivating or terminating agreements. Software Assurance benefits (Azure Hybrid Benefit, training vouchers, planning services) represent real value. Track and use them before they expire.
6. Handle divestitures with a TSA. In a split, formalise a transition period. Mark the end date clearly and work backwards to ensure the new entity has its own tenant and agreement in place before the deadline. Include Microsoft licensing requirements in the TSA alongside infrastructure, application, and data migration obligations.
7. Document everything. Maintain meticulous records of all licence transfers, contract changes, and Microsoft approvals related to the M&A. This documentation is your defence if Microsoft audits the new environment or questions compliance later. Keep records for at least 5 years post-transaction.
8. Negotiate the combined position aggressively. The combined organisation's larger user count and broader Microsoft footprint create negotiation leverage that neither entity had independently. Use this leverage at the first EA renewal post-integration. Target volume-tier pricing improvements, bundle optimisation, and structural concessions (price caps, flex-down rights, extended payment terms). See our Microsoft Contract Negotiation Service and EA Renewal Playbook: Leveraging Competitive Pressure.
Microsoft licensing in M&A is one of the highest-risk, highest-value workstreams in any integration. The complexity of overlapping contracts, the technical challenges of tenant migration, and Microsoft's own commercial incentives create a situation where independent advisory delivers outsized value.
Pre-close licensing due diligence: Redress Compliance conducts licensing assessments of both entities during the due diligence phase, quantifying the total Microsoft licensing liability: what it will cost to bring both organisations into compliance, the savings available from consolidation, and the risks if licensing is not addressed. This number belongs in the acquisition cost model before the deal closes.
Contract consolidation and negotiation: We design the optimal contract structure for the combined entity: which EA survives, how to handle the acquired company's agreement, whether to use CSP or a bridge contract during transition, and how to negotiate the first post-integration EA renewal. Our independence means we optimise for your cost position, not Microsoft's revenue targets.
Tenant migration licensing support: We manage the licensing dimension of tenant consolidation: coordinating licence reassignment to minimise dual-payment periods, tracking perpetual licence transfers, ensuring compliance throughout the migration, and conducting post-migration reconciliation to confirm the combined estate is properly licensed.
Divestiture carve-out support: For divestitures, we design the licence allocation between parent and divested entity, manage the TSA licensing obligations, and ensure both entities have compliant, cost-optimised Microsoft positions at the end of the transition period.
"Microsoft M&A licensing is a multi-million-dollar decision disguised as an IT integration project. Every month of delay in consolidating tenants and contracts costs the combined entity in duplicate licensing, lost volume discounts, and compliance risk. The organisations that save the most are the ones that start the licensing workstream during due diligence, not after close, and that engage independent advisory to negotiate the combined position before Microsoft sets the terms."
Not directly. Cloud subscriptions are tied to the original tenant and agreement. The typical approach is to migrate acquired users into your tenant and then cancel or let old subscriptions expire. You replace their licences with yours. There is no official Microsoft process to "merge" two subscriptions. The migration creates a brief overlap period where users have licences in both tenants. Minimise this overlap to days rather than months to control duplicate costs.
Review its end date and terms. Often, the simplest path is to keep the acquired EA active until it expires (avoiding early termination penalties) while gradually moving users onto the primary EA. At the next renewal cycle, consolidate by signing one new EA covering the combined organisation. In some cases, you can negotiate early termination or fold licences into your agreement, but get Microsoft's written approval. The EA's 10% M&A adjustment clause may allow mid-term modifications, but Microsoft is not obligated to agree to specific terms. See EA Novation Strategies.
It depends on stability. An EA offers volume discounts and fixed pricing but with less flexibility. CSP offers agility to scale up or down without long-term penalties, ideal during the 12 to 24 month integration period when user counts and systems are in flux. Many companies use CSP during transition then re-enter an EA once the organisation stabilises. A hybrid approach, extending the EA short-term while using CSP for variable needs, often works best and preserves negotiation leverage for the post-integration EA renewal.
Set a Transition Services Agreement (TSA) period during which the spin-off can use the parent's IT and licences. During that time, help the new entity establish its own Microsoft tenant and contract. Transfer perpetual licences using Microsoft's transfer form. For cloud services, plan a user and data migration to a new tenant the spin-off controls. Both companies should know exactly when the new entity will "go live" on its own licences. CSP is the recommended initial contract type for the spun-off entity because it requires no multi-year commitment. See Licence Carve-Outs in Divestitures.
Risks include paying far more than necessary (maintaining duplicate licences and separate subscriptions for the same users), compliance exposure (licences assigned to the wrong entity or over-deployment under the wrong agreement), and operational complexity (two sets of security policies, two admin consoles, two sets of conditional access rules). Microsoft could audit the merged company and find inconsistencies that trigger expensive true-up demands. You also miss out on volume discounts that the combined user count would unlock. Every month of delay costs real money.
Microsoft's EA includes a good-faith adjustment provision when licence quantities change by more than 10% due to M&A. They can also offer bridge contracts, short-term extensions, or interim agreements. However, none of this is automatic. You must proactively engage your Microsoft account team and negotiate. Microsoft's willingness to accommodate depends on the commercial opportunity the combined entity represents and how well you present your requirements. Having an independent adviser strengthens your position significantly because you approach the conversation with market data and negotiation experience rather than relying on Microsoft's account team to propose fair terms.
Yes. Volume Licensing programmes like EA and Open allow perpetual licence transfers in divestitures without requiring Microsoft's consent, but you must notify Microsoft by submitting the Perpetual Licence Transfer form. Keep records of all transfers, as they will not automatically appear in the Volume Licensing Service Centre. The key documentation requirement is a schedule of all licences transferred (product, edition, quantity, licence keys if applicable) signed by both parties. This documentation is your primary audit defence for both the parent and the divested entity. See Transferring Volume Licences in M&A.
For mid-size organisations (1,000 to 5,000 users), expect 3 to 6 months for a phased tenant migration. Large enterprises with complex SharePoint estates, custom applications, Power Platform solutions, and multiple Azure subscriptions may take 6 to 12 months. The key variables are the volume of data to migrate (Exchange mailboxes, SharePoint sites, OneDrive content), the complexity of application integrations (Power Automate flows, custom connectors, third-party SSO configurations), and the number of Azure resources that must be moved. Starting the planning process immediately and migrating in waves minimises both business disruption and the duration of duplicate licensing costs.
Redress Compliance provides independent Microsoft licensing advisory for mergers, acquisitions, and divestitures. Pre-close due diligence, contract consolidation, tenant migration licensing support, and divestiture carve-outs. Fixed-fee, vendor-independent, and confidential.
EA Optimisation ServiceIndependent Microsoft licensing advisory for mergers, acquisitions, and divestitures. Tenant consolidation. Contract negotiation. Compliance assurance. 100% vendor-independent.