Microsoft Licensing in M&A Transactions

Microsoft Licensing in M&A: What Changes Immediately

When two organisations with separate Microsoft tenants merge, the Microsoft licensing position of both entities does not automatically combine. Each tenant retains its own EA (if applicable), its own licence entitlements, and its own Azure subscriptions. The newly merged entity must actively notify Microsoft and work through a formal process to align tenants, consolidate agreements, and restructure licence counts. Failure to manage this process results in paying for duplicate licences, missing the renegotiation window, or — worse — inadvertently breaching the use rights of licences acquired from the target organisation.

Microsoft's standard position on M&A activity is governed by the Microsoft Product Terms and the EA amendment process. In an acquisition where a parent entity's EA enrolls the acquired subsidiary, the subsidiary's users must be counted against the parent's true-up from the date of legal close. If the acquisition closes mid-EA term, the parent must perform an immediate licence count assessment and report any uplift at the next annual true-up date — or request an out-of-cycle amendment if the uplift is material. Our EA vs MCA-E comparison guide explains the agreement-level implications of inheriting a target company's Microsoft contracts.

The most immediate risk is the grace period. Microsoft typically allows 90 days from legal close for the acquiring entity to bring the acquired organisation's users into compliance — covering any gap between acquired users and available licence entitlements. This 90-day window is not automatically extended and is not guaranteed for all M&A structures. Missing this window creates retroactive licence liability. Engage Microsoft's account team within 30 days of close to document the transition plan and confirm the grace period formally.

Tenant Consolidation: Options and Commercial Implications

Tenant consolidation — migrating users from the acquired entity's Azure AD tenant into the acquirer's tenant — is the cleanest long-term structure but carries significant short-term cost and complexity. The three primary options are:

• Full consolidation: Migrate all acquired users into the parent tenant. Decommission the acquired tenant. Simplest licensing structure but requires 3–6 months of migration effort and typically incurs one-off Professional Services costs of £50,000–£500,000 depending on complexity.
• Cross-tenant federation: Maintain both tenants but federate identity and collaboration (Teams, SharePoint). Users in both tenants appear in each other's directories. Avoids migration cost short-term but creates ongoing licence management complexity — especially for E5 security and compliance features that do not span tenants natively.
• Subsidiary enrolment: Bring the acquired entity under the parent's EA as a subsidiary enrolment without tenant consolidation. Users remain in the acquired tenant but are licensed under the parent's EA terms. This approach is administratively clean from a Microsoft commercial perspective but requires careful governance to prevent licence leakage between entities.

The choice between these options affects your Microsoft commercial position in ways that are not immediately obvious. Full tenant consolidation typically triggers a new EA true-up discussion — Microsoft's account team will use the opportunity to review your entire licence estate and push for upsells. Go into this conversation prepared: use our Microsoft true-up risk assessment to model your combined licence position before engaging Microsoft, and review your Azure Reserved Instance portfolio to understand which reservations transfer to the consolidated subscription and which do not.

Using M&A as Negotiation Leverage with Microsoft

Most organisations treat Microsoft licensing as a compliance obligation during M&A and miss a significant commercial opportunity. A merger or acquisition that increases the combined organisation's Microsoft spend above a new pricing tier — or that brings a renewal date forward — is a legitimate trigger for EA renegotiation. Microsoft's account teams have authority to re-price an EA mid-term when the licensee's profile changes materially through corporate action.

The tactics that work in practice: If the acquisition increases your total Microsoft seat count by 20% or more, request a full EA renegotiation rather than a simple amendment. Present the combined organisation's spend profile and forecast — including Azure consumption projections — as a single negotiation. Microsoft's discount tiers for M365 typically step up at 500, 2,000, 10,000, and 50,000 seat thresholds. If the combined count crosses a threshold, the discount improvement on the entire estate is substantial. A move from the 2,000-seat tier to the 10,000-seat tier can reduce per-seat M365 E3 pricing by 10–15% — on 8,000 additional seats this represents £250,000–£350,000 in annual savings at UK list prices.

For divestiture situations — selling a subsidiary — the commercial dynamic is reversed. The subsidiary may retain licences under the parent's EA for a transition period (typically 12–24 months under a Transition Services Agreement), but these must be separately accounted for and the parent must ensure they are not transferred beyond the permitted scope. The parent also loses the seat count that supported its EA pricing tier, which can trigger an uplift in per-seat cost if the count falls below a threshold. Model this impact before executing the divestiture structure and build renegotiation rights into the transition services agreement with the buyer. Download our Microsoft Vendor Management Toolkit for governance templates applicable to M&A scenarios. To book a confidential call before your next M&A milestone, our Microsoft team engages at the earliest stage of deal planning.

Azure Subscriptions, Dynamics 365, and Power Platform in M&A

Azure subscriptions are not automatically transferred in a corporate acquisition. An Azure subscription belongs to the billing account under which it was created — if the acquired organisation has Azure subscriptions under its own EA enrolment, these must be formally transferred to the acquirer's billing account through Microsoft's subscription transfer process. This requires a service request to Microsoft and can take 30–60 days. During the transfer window, costs continue to accrue under the original billing account and may not be visible to the acquiring entity's finance team.

Dynamics 365 licences present a specific portability challenge. D365 licences are per-user, per-module, and tenant-specific. In a full tenant consolidation, D365 users must be re-provisioned in the acquiring tenant and licences re-assigned. If the acquired entity ran D365 Finance, Supply Chain, or HR on a different release cycle or customisation level, the migration may require significant implementation work beyond the licensing adjustment. This is often underestimated in M&A due diligence. Our Dynamics 365 licensing guide covers the licence structure for each D365 module and the implications of tenant migration for existing D365 deployments.