Microsoft Licensing in M&A:
Tenant Consolidation, Licence Migration & Contract Renegotiation

Why M&A Is Microsoft's Favourite Upsell Opportunity

Microsoft account teams are alerted internally when their customers announce acquisitions or mergers — it is a trigger event in their CRM that generates an account team meeting, an updated commercial opportunity model, and a set of talking points framed around "helping you integrate seamlessly." The reality behind the framing: M&A events create genuine licensing complexity that Microsoft is uniquely positioned to resolve — at a premium. Organisations that allow Microsoft to drive the post-M&A licensing conversation consistently end up purchasing more licences at worse prices than organisations that arrive at the conversation with their own analysis.

This guide covers the mechanics of Microsoft licensing in M&A — Azure AD / Entra ID tenant decisions, EA rebalancing rights, CSP subscription handling, Teams migration timelines — and the negotiation window that M&A creates for renegotiating enterprise agreement terms before the next scheduled renewal. For broader Microsoft advisory context, our Microsoft Knowledge Hub and advisory services page cover the full licensing landscape. For the existing guide to this topic, see our detailed Microsoft M&A tenant consolidation guide.

The Tenant Decision: Merge, Maintain, or Federate?

The first and most consequential Microsoft decision in any M&A is tenant architecture: whether to merge the acquired company's Microsoft 365 / Azure AD (Entra ID) tenant into the acquirer's, maintain separate tenants with federation, or adopt a hybrid approach with some workloads consolidated and others kept separate. Each path has distinct licensing, operational, and commercial implications:

Full tenant merge: All users, data, and workloads from the acquired company are migrated into the acquiring company's tenant. This is the highest-integration option and ultimately the most commercially efficient — a single tenant enables licence pool consolidation, eliminates duplicate admin overhead, and removes the complexity of cross-tenant collaboration. The challenge is migration cost and timeline: full tenant merges for organisations of 1,000+ users typically take 6 to 18 months and require specialist Microsoft migration tooling (Microsoft's own migration tooling, or third-party tools like BitTitan MigrationWiz or Quest On Demand Migration). During the migration period, both tenants must be licensed — creating temporary licence duplication costs.

Separate tenants with federation: Identity federation (via Entra ID B2B) enables users in separate tenants to collaborate across Teams, SharePoint, and email without full migration. This is lower initial cost but higher long-term operational overhead — two separate tenant admin functions, duplicate security and compliance configurations, and ongoing identity management complexity. Commercially, separate tenants mean separate EAs (or separate CSP agreements), which eliminates cross-tenant volume discount leverage and makes multi-year commit negotiations harder.

Hybrid approach: Some workloads consolidated (typically email and Teams for communication efficiency) while others remain separate (often driven by regulatory requirements, particularly in cross-border acquisitions where data residency mandates separate tenants). The licensing complexity of hybrid approaches is the highest — each boundary between the tenants creates potential licence compliance questions.

EA Licence Rebalancing: Your Rights and How to Exercise Them

Enterprise Agreements contain provisions that govern how licence counts change when headcount changes through M&A — but these provisions are written to Microsoft's advantage if not proactively managed. The key mechanisms:

True-up obligations on acquisition: When you acquire a company, the employees of the acquired entity become subject to your EA terms. If your EA includes a true-up obligation, you are required to report and pay for the additional users at the next annual true-up. However, the timing of when these users become "in scope" for your EA versus the acquired company's existing agreements is not automatic — it depends on tenant architecture, assignment of Microsoft licences, and the terms of your specific EA. This creates a window in which duplicate licence payment can be avoided through careful transition planning.

Right to reduce on divestiture: When you divest a business unit, the employees leaving your organisation remove the obligation to licence them under your EA. This creates a licence reduction right at the next true-up — which Microsoft's account team will not proactively highlight. Document the headcount change, the effective date, and the specific licence SKUs affected, and submit a formal true-up credit request.

Contract renegotiation window: M&A events — particularly acquisitions that materially increase your total employee count covered by Microsoft licences — create genuine leverage for renegotiating your EA terms before the scheduled renewal. A 20% increase in Microsoft-licensed headcount represents a meaningful new revenue opportunity for Microsoft that their account team is motivated to secure. Using this as a prompt for a full commercial renegotiation — new discount levels, new commit structure, improved Azure rates — is one of the most commonly overlooked M&A commercial opportunities.

CSP Subscription Consolidation

Many acquisitions involve companies operating on Cloud Solution Provider (CSP) subscriptions rather than Enterprise Agreements. CSP-to-EA migration is a common post-M&A task with several commercial considerations:

• Timing: CSP subscriptions renew monthly or annually. Migrating mid-term typically involves paying out the remaining CSP term or accepting early termination. Plan the migration to coincide with CSP renewal to avoid duplication costs.
• Licence mapping: CSP plans and EA plans are not always identical in included features. Microsoft 365 Business Premium (common in CSP for sub-300-seat organisations) does not map directly to M365 E3 or E5. A licence equivalency analysis is required before migration to avoid capability gaps or inadvertent licence inflation.
• Reseller relationships: CSP subscriptions are sold through resellers. Consolidating into your EA removes the CSP reseller from the relationship — which the reseller will resist. Microsoft may offer additional incentives to facilitate the migration, particularly if the consolidated ACV is material.

Teams Migration Timelines and Communication Continuity

Microsoft Teams migration between tenants is one of the most operationally sensitive elements of any Microsoft M&A integration. Teams chats, channels, and meeting recordings are tenant-specific — they cannot be directly migrated via Microsoft's native tooling and require third-party migration solutions or a "cut and keep" approach where historical data remains accessible in the old tenant for a period while new collaboration moves to the consolidated tenant.

The commercial implication: maintaining the acquired company's tenant as an archive environment for 12 to 24 months post-acquisition requires continued licensing (at minimum, an E1 or Exchange Online Plan 1 licence per archived user). Budget for this continuation cost in your M&A integration financial model. Microsoft's account team will often propose extending the full licence footprint rather than a targeted archive licence — the difference in cost can be substantial for large acquisitions.

Using M&A as a Renegotiation Trigger

The most commercially valuable aspect of any M&A event is the renegotiation window it creates. Microsoft needs to update your EA to reflect the new entity structure — and this administrative necessity is a commercial conversation that should encompass your entire Microsoft relationship, not just the structural change. Organisations that use this window to renegotiate discount levels, adjust commit structures, and reset Azure pricing consistently achieve outcomes 12% to 20% better than waiting for the next scheduled EA renewal. The leverage is time-limited: once the tenant integration is complete and the new EA is signed, the leverage evaporates. For the broader negotiation tactics that maximise this window, see our Microsoft deal leverage guide and our CIO negotiation guide. To discuss your specific M&A scenario, book a confidential advisory call with our Microsoft team.