Post-merger Microsoft licensing integration is a 12-month workstream from deal close through the first joint EA renewal of the combined entity. The integration runs across four cadences: 90 days to clean compliance triage and Microsoft notification (T+0 to T+90), 90 days to operational tenant and SKU rationalisation (T+90 to T+180), 90 days to contract harmonisation and commercial-position rebuild (T+180 to T+270), and 90 days to combined-entity renewal preparation (T+270 to T+365). Each cadence has distinct objectives and forcing functions. The mistakes that recur in post-merger integration are (a) treating Microsoft licensing as an operational IT-integration task instead of a commercial-position rebuild, (b) running the tenant consolidation before the contract harmonisation (which costs leverage), and (c) deferring the combined-entity Microsoft account-team engagement until the first renewal forces the conversation. The 2026 amplifier is the EA tier-collapse and Copilot programme commitments — both reward early combined-entity posture and punish fragmented post-merger integration. The companion M&A licensing pillar covers pre-close and close-window mechanics; this page covers the post-close 12 months.
The starting position on post-merger Microsoft licensing: deal close happens, the IT integration team is given a target operating model, and Microsoft licensing is enumerated as line-item 14 on the IT integration plan — alongside email migration, Active Directory consolidation, and SAP rationalisation. This framing makes Microsoft licensing a downstream consequence of operational integration. It costs the combined entity materially. Microsoft licensing should run as a parallel workstream — reporting to the CFO, not the CIO — because the commercial-position rebuild needs different leverage points and different timing than the operational IT integration. The disciplined post-merger Microsoft licensing programme treats the 12 months from close as a structured commercial-rebuild workstream, with operational IT integration as a downstream input rather than an upstream constraint.
Post-merger Microsoft licensing: the four 90-day cadences
The 12-month integration runs across four cadences. Each cadence has a distinct objective, forcing function, and leverage point.
| Cadence | Window | Primary objective | Forcing function |
|---|---|---|---|
| Cadence 1 · Compliance triage | T+0 to T+90 | Clean licence-position baseline, Microsoft notification, no-surprise discipline | Audit-risk window plus integration-period scrutiny |
| Cadence 2 · Operational rationalisation | T+90 to T+180 | Tenant consolidation, SKU rationalisation, shelfware elimination | Subscription anniversaries and tenant-licensing dependencies |
| Cadence 3 · Contract harmonisation | T+180 to T+270 | EA / MCA-E / CSP harmonisation, master agreement rebuild, Unified Support consolidation | Renewal anniversary alignment and amendment-window leverage |
| Cadence 4 · Combined renewal preparation | T+270 to T+365 | Combined-entity EA renewal posture, 2026 inflection-point capture, Copilot commitment scope | Combined renewal anniversary (typically T+12 to T+18) |
Post-merger Microsoft licensing cadence 1: compliance triage (T+0 to T+90)
The first 90 days are about establishing a clean licence-position baseline for the combined entity and notifying Microsoft of the close in a controlled manner.
Reconcile deployed vs purchased licences across the combined estate
The compliance triage starts with reconciling deployed counts against purchased entitlements across both legacy estates. Differences identified here become the integration baseline. The audit covers M365 SKU mix, Windows Server, SQL Server, Visual Studio, Power Platform, Dynamics 365, and any specialty workloads (Defender, Purview, Intune Suite). See the licence-position audit article for the methodology. The audit must complete before any tenant-consolidation work begins, because consolidation can mask deployed-vs-purchased delta and remove leverage for true-up negotiation.
Notify Microsoft of the close and align both legacy account teams to a combined-entity sponsor
Microsoft account teams are not auto-informed of merger close; both legacy teams often continue running their pre-close cadences for months until someone formally notifies. The combined-entity CFO or CIO should send a written notification within 30 days of close, identifying the combined entity legal name, the surviving Microsoft account team, the agreement instruments in effect, and a designated single point of contact. The notification triggers Microsoft to assign a unified account team. See the license transfer mechanics article for the assignment-and-consent posture.
Update both legacy EAs' affiliate-inclusion schedules to reflect the post-close entity
Both legacy EAs likely have affiliate-inclusion schedules that no longer reflect the post-close legal entity. The schedules must be updated explicitly: the surviving entity's EA should add the acquired entity's affiliates; the acquired entity's EA should add the surviving entity's affiliates (or be terminated and consolidated). See the EA affiliates and subsidiaries article for the mechanic. Schedule updates that are not done create ambiguity about whether users at one entity were authorised under the other entity's EA at any post-close point.
Compute true-up exposure for both legacy EAs against the deployed-position audit
Both legacy EAs continue to run their true-up cycles post-close. The true-up exposure should be computed for each EA against the deployed-position audit. Where true-up exposure is material, the combined entity should evaluate whether to (a) true-up at the legacy EA prices, (b) defer until the EA harmonisation, or (c) negotiate the true-up as part of the harmonisation. See the true-up leverage article.
Treat the first 12 months post-close as elevated audit risk and monitor accordingly
Microsoft compliance functions historically increase audit attention on companies in the first 12-18 months post-merger, on the theory that combined entities have unclear licence positions. The combined entity should monitor for SAM-engagement invitations and contractual audit notifications. See the true-up defense service and the audit help page for the response posture.
Post-merger Microsoft licensing cadence 2: operational rationalisation (T+90 to T+180)
The middle 90 days are about consolidating the operational Microsoft estate — tenants, SKUs, and consumption — while the commercial position is being prepared for harmonisation in cadence 3.
- Tenant strategy decision. The combined entity must decide between single-tenant consolidation, multi-tenant federation, or multi-tenant with Multi-Geo. The decision shapes the next decade of operational Microsoft consumption and constrains certain SKU choices (Multi-Tenant Organisation features, External ID licensing, cross-tenant collaboration). Tenant strategy should be set in cadence 2 but executed in cadence 3-4 to align with contract harmonisation.
- SKU rationalisation across estates. Legacy entities often run different M365 SKU mixes (one on E3 with selective E5, the other on E5 throughout). The combined entity should rationalise to a unified SKU mix. The M365 licence audit tool supports the analysis. Often the unified position is E3 + selective E5 add-ons (Defender for Office, Purview, Intune Suite) where E5 is needed by role rather than across-the-board.
- Shelfware elimination. Both legacy entities likely carry shelfware that is invisible at the entity level but becomes visible in the combined audit. See the license overages article for the cost-recovery mechanic.
- Azure consumption alignment. Both legacy entities may have MACC commitments that overlap or duplicate. The Azure consumption should be aligned to a single tenant or federation, MACC commitments evaluated for consolidation. See the MACC negotiation pillar.
- Unified Support tier review. Both legacy entities run Unified Support at distinct tiers; the combined entity may need only one tier (typically the higher tier from the larger legacy entity) at a recalculated contracted-spend basis. Reference the Unified Support 2026 pillar.
Post-merger integration in flight? The cadence-discipline window closes fast — engage independent advisory in the first 60 days.
30-minute scoping call. Post-merger Microsoft licensing is standard advisory work.
Post-merger Microsoft licensing cadence 3: contract harmonisation (T+180 to T+270)
The third 90 days are the commercial-position rebuild. This is where the largest savings are captured and where most post-merger integrations fall short.
The combined entity must decide whether to run on a single EA, a single MCA-E, or a hybrid. The decision is shaped by combined seat count, Azure-vs-M365 mix, geographic spread, and growth profile. A single EA is appropriate for stable, large combined entities; a single MCA-E is the modern flexible alternative; hybrid (M365 on EA, Azure on MCA-E) is increasingly common. The EA negotiation pillar covers the instrument-choice analysis.
Both legacy EAs have different anniversaries. The combined entity should align to a single anniversary. The mechanic is either (a) co-terminate one EA into the other, with a credit / amendment to align dates, or (b) let the earlier EA expire and roll into the surviving EA at expiry. Co-termination is typically more expensive in the short term but produces a single negotiation window thereafter; rollover is cheaper but creates an asymmetric negotiation window. The choice depends on the relative size of the two legacy positions and the calendar pressure of cadence 4 renewal preparation.
Both legacy MACC commitments should be consolidated into a single MACC at the combined entity's recalibrated Azure consumption forecast. The recalibration typically captures tier discount that neither legacy entity could access alone. The growth model should reflect combined-entity growth assumptions, not legacy-entity assumptions. See the MACC negotiation pillar for the consolidation mechanic.
Unified Support is calculated on contracted Microsoft spend; combined-entity spend is the sum of legacy spend after consolidation. The Unified Support tier should be reset to the appropriate tier for combined spend, not the highest legacy tier carried forward. Often the combined entity can step down a tier (Performance to Advanced, or Advanced to Core) reflecting consolidated spend rather than additive legacy tiers.
Both legacy entities may have Copilot commitments from pre-merger periods. Aggressive Copilot adoption assumptions inherited from pre-merger times rarely survive the integration. The combined-entity Copilot scope should be rebuilt on integrated-adoption assumptions — typically a small-pilot-first approach with deferred ramp commitment. See the Copilot Studio 2026 pillar for the 4-mechanism framework.
Post-merger Microsoft licensing cadence 4: combined renewal preparation (T+270 to T+365)
The final 90 days prepare the combined entity for its first joint EA renewal — the moment when the post-merger integration is locked in as a commercial position.
- Renewal posture rebuild. The combined entity enters the renewal as a new combined position, not as either legacy entity. The posture must be rebuilt from first principles. See the EA Q4 checklist.
- 2026 inflection-point alignment. The combined renewal sits in the post-2026 commercial environment with EA tier-collapse, July 2026 price increase, Copilot programme commitments, and CSP grace-period elimination. Each must be addressed in the renewal posture. Reference the 2026 changes rollup.
- Tier-collapse modelling. The combined volume should be modelled against the post-2026 tier grid. Combined volume often crosses thresholds neither legacy entity reached. See the tier-collapse pillar.
- July 2026 lock-in window. Where the combined renewal sits before July 2026, the pre-July pricing should be locked in. See the July 2026 pricing pillar.
- Agent 365 and E7 evaluation. The combined entity should evaluate Agent 365 and M365 E7 on combined-entity adoption assumptions, not legacy-entity ones.
The single highest-leverage move in post-merger Microsoft licensing is to run the four cadences as a parallel CFO-sponsored workstream rather than as a downstream IT-integration task. The CFO sponsorship provides the commercial-rebuild discipline that the IT-integration cadence cannot. The CFO sponsorship also keeps the combined-entity Microsoft account-team conversation at the executive level, where commercial latitude is materially greater. The second-highest leverage move is to align cadence 2 (operational rationalisation) to support cadence 3 (contract harmonisation) rather than running tenant consolidation before commercial harmonisation. Tenant consolidation should happen after the commercial position is locked, because consolidation removes leverage points that the commercial negotiation can use. Independent advisory engages on post-merger licensing as a standard 12-month engagement; the engagement structure typically pairs a CFO-reporting advisory line with operational-IT integration support.
The Microsoft Negotiations briefing
Monthly. M&A post-merger Microsoft licensing intelligence, integration cadence discipline, 2026 inflection-point updates, harmonisation playbooks. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the post-merger Microsoft licensing discipline next
Post-merger integration pairs with the broader M&A framework. The M&A playbook covers pre-close mechanics; the license transfer playbook covers assignment and consent; the diligence playbook covers pre-close discovery; the EA consolidation playbook covers the consolidation mechanics; the PE portfolio playbook covers cross-portfolio discipline; the EA affiliates article covers schedule mechanics; the EA negotiation pillar covers the renewal-cycle context; the EA strategy service is the productised renewal-rebuild engagement; the contract advisory service is the harmonisation and amendment engagement; the EA renewal checklist is the T-12 to T-3 cadence guide adapted for post-merger combined-entity renewals. For organisations in flight on post-merger integration, the scoping call is the direct engagement channel.