How Microsoft audits follow mergers is a question of arithmetic as much as intent. A merger takes two Microsoft estates, each with its own agreement, its own editions, and its own assumptions, and forces them together. Editions overlap, client access licenses fall short, and server entitlements stop matching the hardware once workloads are consolidated. Microsoft, frequently working through an appointed third party, reviews the combined picture in the year after a deal and prices whatever does not reconcile. This page explains the mechanics, as a child of the cluster on M&A software audit risk.
How Microsoft audits follow mergers through colliding agreements
The first thing a merger does to a Microsoft estate is collide two agreements that were never meant to coexist. Each company arrives with its own Enterprise Agreement or its own mix of licensing programmes, negotiated at different times against different headcounts and different product sets. When the entities combine, those agreements do not simply add together. One may need to be assigned, one may be co terminated, and during the transition there is often a period where it is unclear which agreement covers which deployment. Microsoft and its appointed reviewers look precisely at these seams, because a product that is deployed but not clearly covered by either agreement is a shortfall they can price. The cleaner the buyer can make the agreement structure early, the smaller that seam becomes.
Editions, CALs, and the gaps that hide in plain sight
Microsoft licensing carries two recurring traps that a merger widens. The first is editions. Windows Server, for example, is licensed in Standard and Datacenter editions with very different virtualization rights, and SQL Server is licensed per core with edition tiers that matter on consolidated hosts. When a target's servers are folded into the buyer's virtual environment, the edition that was adequate standalone may be wrong for the shared cluster. The second trap is client access licenses, the per user or per device rights required for many server products. CALs are easy to undercount, easy to lose track of across two organisations, and a frequent source of shortfall when two user populations merge. Neither gap is exotic, which is exactly why a reviewer expects to find them.
How the review actually happens
Microsoft often does not run the review itself. Much post deal compliance work reaches the customer as a Software Asset Management engagement or as a formal audit conducted by an appointed third party, frequently a large accountancy or specialist firm. The reviewer collects deployment data, reconciles it against the entitlement records, and presents any shortfall for purchase. The process can feel neutral, but the method and the assumptions favour the publisher, and a buyer that has not built its own position tends to accept the reviewer's numbers by default. Understanding the sequence in advance lets a buyer prepare evidence and challenge assumptions rather than react. The general shape of that sequence is set out in the audit defense timeline after a transaction.
| Area | Typical gap | Why a merger causes it |
|---|---|---|
| Windows Server | Standard deployed where Datacenter is needed | Consolidation onto dense virtual hosts |
| SQL Server | Undercounted cores on shared clusters | Workloads moved across combined infrastructure |
| Client access licenses | Missing user or device CALs | Two user populations merged without reconciliation |
| Microsoft 365 | Mismatched plans and orphaned licenses | Two tenants merged or left running in parallel |
| Agreement coverage | Products covered by neither EA in transition | Agreements assigned or co terminated unevenly |
Key takeaways
- A merger collides two Microsoft agreements and two estates that were never designed to combine.
- Edition mismatches and missing client access licenses are the most common and most expected shortfalls.
- Microsoft often reviews through a Software Asset Management engagement or an appointed third party, not directly.
- Virtualization and consolidation change core counts and required editions even when workloads are unchanged.
- A single reconciled position across both estates is the buyer's best defence and best negotiating asset.
Virtualization, the multiplier on a Microsoft merger
Virtualization sits underneath most of these gaps. Windows Server Datacenter exists because dense virtualization needs unlimited virtual rights on a host, and SQL Server core licensing tracks the cores available to the workload. When a buyer consolidates a target onto shared virtual infrastructure, the host configuration, not the application, determines the licensing. A few well intentioned consolidation decisions can change which edition is required and how many cores must be licensed, producing exposure that has nothing to do with new functionality. Buyers planning consolidation should model the licensing impact of the target host design before they move workloads, a discipline shared with audit risk from virtualization and cloud migration.
How a buyer gets ahead of Microsoft
The defence is reconciliation, done early and once. A buyer should build a single inventory of what is deployed across both estates, a single record of what is entitled under both agreements, and a clear plan for the editions, CALs, and core counts the consolidated environment will need. With that baseline in hand, a review becomes a comparison the buyer can lead rather than a finding the buyer must accept. The same baseline lets the buyer rationalise overlapping agreements, retire duplicated spend, and time any true up on its own terms. Doing this before a notice arrives is the whole game, because evidence assembled in calm always beats evidence scrambled under an audit clock. The broader method is set out in building an audit defensible license position after close.
Recommendations for buyers
- Build one reconciled position. Combine both estates into a single inventory and a single entitlement record before any review.
- Clarify agreement coverage. Confirm which Enterprise Agreement governs which entity so no product falls into a transition gap.
- Model editions and cores before consolidating. Check Windows Server and SQL Server licensing against the target host design.
- Reconcile client access licenses. Count user and device CALs across the merged population, not each company alone.
- Lead the review with evidence. Prepare deployment data and assumptions so you challenge the method rather than accept it.
Microsoft 365 and the two tenant problem
Cloud does not simplify the Microsoft picture in a merger, it adds a new seam. Each company usually runs its own Microsoft 365 tenant, with its own plan mix, its own licenses, and its own identity directory. Combining the organisations forces a choice: migrate one tenant into the other, run both in parallel, or build a new one. Each path has licensing consequences. Parallel tenants tend to accumulate orphaned and duplicate licenses as people move between them, and plan mismatches mean some users hold more than they need while others lack a required add on. A migration can strand licenses that do not transfer cleanly, and reassigning licenses across tenants is governed by rules that are easy to break. Microsoft 365 also interacts with the on premise estate through hybrid identity and shared services, so a tenant decision can ripple into server licensing. A buyer should plan the tenant strategy early and reconcile the plan mix across the combined population, because the subscription waste and the compliance gaps both compound the longer two tenants drift in parallel.
How Microsoft audits follow mergers, in one line
How Microsoft audits follow mergers comes down to a collision: two agreements, two sets of editions, and two estates forced together faster than anyone reconciles them. Edition gaps, missing client access licenses, and consolidation driven core changes are the predictable result, and an appointed reviewer prices them in the year after the deal. A buyer that builds one reconciled position, clarifies agreement coverage, and models consolidation in advance turns that review into a negotiation it can win. We do that work on the buyer side only, paid solely by the acquirer.