Microsoft licensing due diligence in M&A produces five artefact categories that determine integration cost, integration timeline, and post-close negotiation leverage: contract artefacts (EA / MCA-E / CSP contracts and amendments), entitlement artefacts (licence-position records, SA-coverage detail, MACC and Copilot commitments), deployment artefacts (actual deployed user/device count, SKU mix, third-party tools), compliance artefacts (open audits, SAM engagements, true-up exposure), and commercial artefacts (discount tier, anniversary date, account-team relationships). The buyer-side discipline is to require all five categories in the diligence data room and to interpret them against the contemplated transaction structure. Diligence findings inform deal valuation (integration cost is a deal-economic variable), warranty / indemnity scoping (compliance exposure is an indemnifiable risk), and integration planning (timing the affiliate amendment to the acquirer's renewal-cycle is a leverage variable). The 2026 amplifiers add Copilot commitment exposure, MACC reset risk, and tier-collapse repricing. The companion M&A integration playbook covers the broader programme context.
The starting position on Microsoft licensing due diligence: licensing is one of the most reliably-overlooked diligence threads in mid-market and even large-cap M&A. Deal teams cover legal, financial, tax, operations, IT systems, and cybersecurity diligence as a matter of course; software licensing slots into IT systems or operations as a sub-bullet, and the diligence depth rarely matches the financial exposure. The exposure is meaningful: an undiagnosed Microsoft licensing position can add 3 to 9 percent of post-close integration cost relative to the deal value, the bulk of it driven by audit findings, true-up exposure, and Copilot / MACC commitment positions that surface in post-close integration but were invisible in the original diligence. A dedicated licensing-diligence workstream changes that exposure profile.
Microsoft licensing due diligence: contract artefacts
The contract artefact set is the foundation of the licensing diligence. Without the contracts in hand, no other diligence interpretation is reliable.
- Enterprise Agreement (EA) and all amendments. The current EA contract document and every amendment, side letter, and order form executed against it. Includes the EA enrollment number, the affiliate-inclusion schedule, the assignment / change-of-control clauses, and any custom-negotiated provisions.
- Microsoft Customer Agreement for Enterprise (MCA-E) or MCA-X. For organisations that have transitioned from EA to MCA, the current MCA-E contract document, the MCA-X or MCA-E terms, and any active commitment-aligned addenda.
- CSP indirect contracts. For organisations consuming Microsoft via CSP (typically smaller subsidiaries or specific business units), the CSP indirect reseller agreement(s), the subscription terms, and the actual subscription order records.
- Server & Cloud Enrollment (SCE). If present, the SCE document and order history.
- Direct EAS / EAP for Azure / Server licences. Any direct Azure commitment instrument (MACC) and the underlying terms.
- Side letters and non-published terms. Any account-team-issued letters or negotiated terms outside the published Product Terms. These often contain the most leverage-relevant provisions and are also the most likely to be missed in a deal-room collection.
Microsoft licensing due diligence: entitlement artefacts
The entitlement artefact set documents what the target is actually licensed for under the contracts.
- Current Microsoft licensing position. Pulled from VLSC, the M365 admin centre, or the equivalent licence-management portal. Includes every SKU, the seat / device / core count, the SA-coverage flag, and the active vs expired status. VLSC Report 3 is the canonical artefact.
- Anniversary and renewal dates. The EA anniversary date, the next true-up window, and the EA renewal date.
- Software Assurance coverage detail. Per-SKU SA coverage detail, including SA expiration dates and SA-benefit-redemption history (e-learning, Training Vouchers, Planning Services Days, HUP). The redemption history is leverage at SA renewal.
- MACC (Microsoft Azure Consumption Commitment). Current MACC commitment value, commitment period, consumed-to-date, remaining-balance, and the growth-discount activation status.
- Copilot commitments. Copilot for M365 seat commitment, Copilot Studio (CCCU/ACU) capacity reservation, GitHub Copilot Business / Enterprise seat counts, and any AI-product-specific commitment instruments.
- Reserved Instances and Savings Plans. Azure RI and Savings Plan commitments, term, scope, and remaining-balance.
- Unified Support tier and value. The current Unified Support tier (Core / Advanced / Performance / Mission Critical), the annual fee, and the contract anniversary.
Microsoft licensing due diligence: deployment artefacts
The deployment artefact set documents what the target is actually consuming, versus what they are licensed for. The gap between entitlement and deployment is where compliance exposure typically lives.
| Deployment artefact | Source | Diligence relevance |
|---|---|---|
| Active M365 user count by SKU | M365 admin centre / Azure AD | Confirms entitled vs active user ratio; over-licensed = rightsizing opportunity, under-licensed = true-up exposure |
| Active Copilot deployment | M365 admin centre Copilot section | Documents the actual Copilot rollout against the commitment |
| Active Azure subscriptions and consumption | Azure portal / Cost Management | Tracks MACC commitment burn rate vs commitment value |
| Active Azure Reserved Instances and Savings Plans | Azure Reservations dashboard | Confirms RI utilisation and exposure to under-utilised commitments |
| Active Windows Server / SQL Server estate | SCCM / Configuration Manager / Intune / Defender for Cloud | Reveals the on-prem server licensing position and the AHB-eligibility on Azure |
| Third-party tools that consume Microsoft licences | IT inventory / procurement | Power Automate, Power BI, Power Apps, Dynamics — license inheritance complexity |
| Active Unified Support consumption | Premier dashboard | Confirms support engagement value vs the contracted tier |
Microsoft licensing due diligence: compliance artefacts
The compliance artefact set documents any open or recent risk exposure. This category is the most likely to produce material indemnity claims post-close.
- Open Microsoft Verification engagements. Any active Microsoft Verification (formerly known as SAM engagement) or audit-type review. Includes the engagement scope, the verification team, the findings to-date, and the current remediation posture.
- Recent SAM engagement findings. Findings from any SAM engagement closed within the last 36 months, including remediation actions taken and any residual exposure.
- Open true-up disputes. Any disputed true-up calculations, contested seat counts, or unresolved over-deployment items.
- SPLA audit exposure. For organisations holding SPLA contracts (typically service providers or hosting providers), the open SPLA audit position and the monthly usage reporting accuracy. See the SPLA audit pillar for detail.
- Indirect-channel compliance. Any compliance exposure on CSP or LSP-channel licences, including seat-allocation accuracy and contract-term compliance.
- Software piracy or unlicensed-deployment risk. Documented incidents or known exposure for unlicensed Microsoft software deployment (e.g., Office on personally-procured machines used for work, server software running without licence assignment).
- Acquired-business prior compliance history. If the target itself has acquired companies in the past 5 years, the licensing-compliance posture of those prior acquisitions and any residual exposure.
Microsoft licensing due diligence: commercial artefacts
The commercial artefact set documents the negotiation posture and the relationship history. These artefacts inform the post-close re-negotiation leverage.
- Current discount tier and price-list position. The negotiated discount level (A/B/C/D in legacy terms, or the equivalent volume-tier in the post-2026 structure), and the negotiated discount percentage off MSRP for each SKU.
- Pricing-history record. The pricing trajectory across the last 2-3 EA renewals. Identifies any historical concessions, price-protection mechanisms, or volume-rebate arrangements.
- Account-team relationships. The named Microsoft account executive, the technical specialist team, and the LSP / partner relationships. Relationship continuity affects post-close negotiation leverage.
- Renewal-cycle history. Any concessions made by either party in past renewal cycles. Microsoft account teams track this history; the buyer should also have it.
- Disputed account-team issues. Any escalations or disputes with the Microsoft account team, especially around audit handling, pricing, or product-positioning concerns.
The buyer-side licensing-diligence discipline
Five operating practices recur in mature M&A licensing-diligence programmes.
Make licensing a named workstream in the diligence plan, not a sub-item of IT
Licensing should be a named workstream with a named workstream lead, a dedicated data-room sub-folder, and a defined deliverable set. Where licensing is a sub-bullet under IT, the depth and rigour of the diligence is structurally insufficient. The dedicated workstream produces an artefact pack at three milestones: pre-LOI scoping (high-level exposure flag), pre-binding offer (full artefact set with exposure quantification), and pre-close (final exposure assessment and integration plan input).
Require all five artefact categories in the data room and follow up on gaps
Targets frequently provide contracts (relatively easy to assemble) but not entitlements (require admin-portal exports), deployment (require IT-asset-management data pulls), or compliance (sometimes deliberately omitted). The buyer-side diligence team should require all five categories and flag any gap as a diligence finding, not an acceptable absence. Targets that cannot produce deployment artefacts within 2 weeks of request often have unmanaged licensing positions — itself a diligence finding.
Interpret diligence findings against the planned deal structure (stock, asset, merger, divestiture)
The same diligence finding produces different post-close exposure depending on the deal structure. An open Microsoft Verification engagement in a stock acquisition transfers automatically with the entity; in an asset acquisition, it may not transfer if assignment is properly structured. A MACC commitment shortfall in a divestiture remains with the parent; in a stock acquisition, it transfers to the acquirer. The interpretation pass converts diligence findings into deal-structure-specific exposure quantification.
Convert diligence findings into deal-economic inputs
Diligence findings are not just integration-planning inputs; they are deal-economic variables. Integration cost (the post-close licensing run-rate after roll-up to acquirer EA) affects deal valuation. Compliance exposure (open Microsoft Verification engagements, audit findings, true-up disputes) affects warranty / indemnity scope. The buyer-side discipline is to feed the diligence findings explicitly into the deal-pricing and indemnification negotiations rather than treat them as post-close operational items.
Build the post-close affiliate-amendment plan as a diligence deliverable
The final diligence deliverable is the post-close integration plan: when the affiliate amendment will be sought, what re-negotiation positions will be taken, what audit-remediation actions will be triggered, and what the targeted post-close licensing run-rate will be. The plan is treated as a deal-document attachment rather than a post-close operational item. Mature M&A licensing-diligence teams produce this plan as part of the final diligence pack so the deal team can present an integrated view to the deal-close investment committee.
M&A diligence with licensing bundled into IT systems? The exposure is structurally invisible until post-close.
30-minute scoping call. M&A licensing diligence is standard advisory work.
2026 amplifiers shaping Microsoft licensing due diligence
Three 2026 dynamics reshape the diligence priority list this cycle.
- Copilot commitment exposure. Copilot for M365 seat commitments and Copilot Studio (CCCU/ACU) capacity reservations are now meaningful diligence items. Targets with aggressive Copilot commitments and slow actual rollout carry a documented unused-commitment exposure that is rarely surfaced in standard IT diligence. The dedicated licensing diligence should map every AI-product commitment to actual adoption.
- MACC reset risk on entity-level changes. Asset acquisitions and dissolution-style mergers create MACC reset risk. The diligence pack should document MACC commitment posture, current consumption against commitment, and exposure to a Microsoft-driven MACC reset at transaction close. See the MACC negotiation pillar for the broader mechanics.
- EA tier-collapse repricing exposure. Targets approaching EA renewal in the post-2026 tier-collapse pricing structure carry repricing exposure that the acquirer should model pre-close. The combined post-deal volume may also produce different tier-collapse outcomes than the target standalone position; the diligence should model both. See the EA tier collapse pillar.
The single most-overlooked diligence artefact is the Copilot adoption metric. Microsoft account teams routinely sell Copilot commitments larger than the target's realistic adoption ramp; the commitment lands on the licensing position but the adoption never materialises. Targets in this position have a "shadow Copilot exposure" — they are paying for commitment they are not consuming, the commitment will renew automatically, and the acquirer inherits the renewal. The dedicated licensing diligence should pull the Copilot active-user metric from the M365 admin centre and compare against the contracted seat count. The gap is the exposure; it is sometimes substantial. The Agent 365 framework adds another axis to this conversation for 2026 acquisitions.
The Microsoft Negotiations briefing
Monthly. M&A licensing diligence, EA negotiation, Copilot adoption, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the diligence discipline next
The licensing-diligence discipline pairs with the broader M&A and EA-negotiation framework. The M&A integration playbook covers the broader programme context; the license transfer guide covers the post-close assignment mechanics; the affiliates and subsidiaries guide covers the post-close affiliate-amendment mechanic; the EA negotiation pillar covers the broader renewal-cycle context; the EA strategy service is the productised renewal-cycle engagement; the licensing audit service is the productised diligence-style engagement; the M365 licence audit tool is a starting self-check. For organisations approaching an M&A transaction, the scoping call is the direct engagement channel; for broader scoping, the free EA assessment is the broader channel.
Transaction-specific guidance: the post-close EA consolidation playbook covers acquirer-side integration once diligence findings are quantified; the divestiture / EA-splitting playbook covers carve-out mechanics; the pre-IPO licensing playbook adapts the diligence artefact set to S-1 scrutiny; the cross-border M&A playbook covers international diligence layers; the spin-off licensing playbook covers parent-and-SpinCo separation.
Owner-specific guidance: the private-equity Microsoft licensing playbook covers cross-portfolio diligence-template build for PE operating partners; the post-merger integration playbook covers how diligence findings translate into the 12-month integration cadence; the entity-to-entity transfer playbook covers the consent-and-assignment mechanic that diligence outputs feed; the merging IT environments playbook covers how diligence findings flow through to operational workload reconciliation.