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.
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.
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.
Different EA terms, renewal dates, discount levels, and special pricing across two organisations create a contractual maze that Microsoft will exploit at renewal.
Acquired company's systems may not be properly licensed under your agreements. Microsoft is known to scrutinise companies post-merger — audit risk increases significantly.
Maintaining separate agreements means neither entity benefits from the combined volume. Consolidating unlocks better pricing tiers and negotiation leverage.
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. Read Microsoft Audit Defence Service.
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, and any special pricing or concessions. Read Microsoft EA Optimisation Service.
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.
Check the Microsoft Business and Services Agreement for "affiliate" definitions — usually entities with >50% ownership. If the acquired company qualifies as an affiliate, you may bring them under your existing umbrella agreements more easily.
Review any company-wide Office 365 or Windows licensing commitments. If you acquired a company with 300 new Windows Servers and your Server & Cloud Enrollment requires Software Assurance on all servers, that acquisition could trigger a massive true-up. Know obligations in advance.
One company might have negotiated discounted pricing or flexible terms. Strive to preserve those in the combined contract — don't assume Microsoft will automatically extend the same deals to the new larger entity. You'll need to negotiate. See 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.
Tenant consolidation is a major technical undertaking in mergers. Each company typically has its own M365 tenant — Azure AD, Exchange Online, Teams, SharePoint. CIOs should decide early whether to merge into a single tenant for unified collaboration, reduced admin overhead, and elimination of duplicate licences.
Microsoft doesn't provide a one-click "merge" button. Migration involves moving users, mailboxes, SharePoint sites, and data using third-party tools or Microsoft's cross-tenant migration capabilities. Migrate department by department to minimise disruption.
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.
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.
After migration, shut down the acquired company's tenant to stop ongoing licensing charges. Don't forget to migrate Azure services, Power Platform applications, and any other resources tied to the old tenant's Azure AD.
Need help consolidating Microsoft tenants after an acquisition?
Microsoft Optimisation →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.
| 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" — 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 |
| Office 365 E3 | Company A (1,000 users) | Company B (500 users) | Combined (1,500 users) |
|---|---|---|---|
| Approx. price per user/month | $20 (EA volume discount) | $22 (smaller contract) | $18 (higher volume tier) |
| Annual licensing cost | ~$240,000 | ~$132,000 | ~$324,000 |
| Annual savings | ~$48,000/year from consolidating into a single higher-volume agreement | ||
Beyond volume discounts, consolidation eliminates duplicate licences (both companies may have separate Power BI, Project, or Visio subscriptions), standardises licence editions, and creates opportunities for bundle optimisation. Read Consolidating M365 Tenants Without Double Licensing.
| 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 — locked user counts 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 |
| Recommendation | Renew/extend EA once integration stabilises | Use CSP during the 12–24 month integration period |
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, 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. Don't be afraid to ask. See 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 doesn't happen overnight.
Formalise a transition period (typically 6–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.
Identify which perpetual licences (Windows, Office, Server CALs) need to transfer to the new entity. Use Microsoft's transfer process — Volume Licensing programmes like EA and Open allow transfers in divestiture without Microsoft's consent, but you must submit the transfer form.
Cloud subscriptions can't 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.
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. Read Licence Carve-Outs in Divestitures.
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.
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.
Merge M365/Azure AD 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.
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.
Don't 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.
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.
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.
Independent Microsoft licensing advisers can benchmark your combined position, identify savings opportunities, and negotiate consolidation terms that internal procurement may not know are achievable. Microsoft Contract Negotiation Service →
Explore our vendor-specific guides:
Our independent Microsoft licensing experts help enterprises consolidate tenants, negotiate optimal contract structures, and avoid compliance risks during mergers, acquisitions, and divestitures.