Microsoft licensing exposure is one of the least diligenced items in technology acquisitions and one of the most reliably consequential after close. Audit exposure travels with the asset. Renewal cliffs travel with the asset. Latent shelfware and bundle commitments travel with the asset. The briefing below names the diligence questions that surface these items, the disclosures the seller will resist providing, and the remedies that belong in the purchase agreement.
Most diligence streams capture the target's Microsoft annual spend and stop there. The number is unhelpful in isolation. What matters is the gap between entitlement and consumption, the contractual position relative to peer pricing, the open audit posture, and the renewal cliff that will land in the acquirer's lap inside the deal model. The practice has seen acquirers absorb seven to nine figure post close licensing liabilities that were visible in diligence to anyone who knew where to look.
The active master agreement, the enrollment structure, the price level, the term remaining, the next anniversary date, and the renewal cliff. Without this baseline the rest of diligence is conjecture.
The complete SKU level entitlement position. Quantities paid for. SKUs included by virtue of bundle structures. Reservations and savings plans on Azure. Hybrid benefit entitlements. The position the target is paying for, not the position it thinks it has.
Active user counts in Entra. Active SQL Server cores in production. Active Azure consumption against MACC. The gap between paid entitlement and actual consumption is the single most informative number in the diligence pass.
Any open or recently closed Microsoft audit. The findings, the settlement, the residual obligations. The probability of a new audit given the target's profile. The audit posture inherited at close is rarely surfaced without explicit diligence.
What the target is paying versus peer companies on similar contract size. The benchmark gap is recoverable at renewal in most cases. The acquirer needs to know whether the value exists before the deal model bakes in the current cost structure as if it were market.
Whether Microsoft has assignment consent rights, what the consent process looks like, and what concessions the target's contract might lose under change of control. Microsoft's response to change of control is administrative if the contract is sound and disruptive if it is not.
Sellers resist the disclosures that would surface the exposures above. The acquirer's diligence team needs to ask for the right artifacts, in the right order, and to know when to escalate the disclosure refusal into a deal protection rather than walking away from the data. The list below names the four asks that reliably attract pushback and how to handle them.
The full SKU level entitlement export from the Microsoft 365 admin center and the EA portal. Sellers resist because the export surfaces gaps. The acquirer should treat refusal as a material item warranting an indemnity rather than a representation.
All correspondence with Microsoft compliance, with KPMG, Deloitte, or BDO acting as Microsoft's auditor, and with any third party reseller acting on Microsoft's behalf. Even closed audits carry residual exposure that the diligence pass needs to surface.
Twelve months of Azure consumption data exported from cost management. Sellers often disclose summarized data only. Subscription level data is what allows the acquirer to model the actual reservation and MACC position rather than the seller's representation of it.
Written confirmation from the Microsoft account team on how change of control will be administered. Whether pricing concessions survive close. Whether the contract bifurcates. Without the written position, the acquirer is assuming a friendly Microsoft posture that is not contractually guaranteed.
The practice has supported acquirers on Microsoft licensing diligence across financial services, technology, and manufacturing transactions. We run the diligence pass on the timeline the deal needs.