The compliance review claimed the company had deployed its own Microsoft licenses on Azure without the mobility rights to support it, and the opening exposure ran into the millions. The claim rested on assumptions about the estate that did not hold. This is how entitlement reconstruction collapsed the number.
A fast scaling software company running its platform on Azure with a substantial deployment of its own Microsoft server licenses brought into the cloud under license mobility. A compliance review asserted that large portions of the estate lacked the mobility rights and Software Assurance coverage required to run those licenses on Azure, producing a multimillion dollar exposure. The practice was engaged to reconstruct the entitlement position and respond.
Bring your own software on Azure is one of the most misunderstood areas of Microsoft licensing, and one of the most frequently challenged in compliance reviews. The rules around license mobility, Software Assurance coverage, and which workloads qualify to run customer owned licenses in the cloud are genuinely intricate, and the burden of proving the entitlement position sits with the customer. For a fast growing company that had scaled its Azure footprint quickly, the documentation trail had not kept pace with the deployment, which is exactly the gap a review is designed to find.
The review arrived with a confident assertion. It took a point in time picture of what was running on Azure, mapped it against what the reviewer could see in the company's purchasing records, and treated every license it could not immediately reconcile as unlicensed. The resulting exposure ran to $4.6M. The methodology was familiar: when the entitlement history is incomplete, the reviewer fills the gap with the assumption least favorable to the customer, and the burden falls on the company to prove otherwise.
The company's instinct was to negotiate the number down from the top, which is the most common and most expensive mistake in audit response. A claim built on assumptions is not defeated by haggling. It is defeated by reconstructing the facts the assumptions replaced.
The practice rebuilt the entitlement position from the underlying records rather than the reviewer's snapshot. Every customer owned license deployed on Azure was traced to its acquisition, its Software Assurance coverage, and its eligibility for license mobility, establishing which workloads genuinely qualified to run in the cloud. The deployment was then mapped accurately to that entitlement base, separating the licenses that were fully covered from the smaller set where a real gap existed.
That reconstruction dismantled the claim in stages. A large share of the asserted exposure rested on licenses that did carry mobility rights and Software Assurance, which the company had simply never documented in a form the reviewer would accept. Another portion reflected double counting in the reviewer's snapshot, where the same deployment had been counted against multiple entitlements. What remained after the reconstruction was a modest, genuine gap, a fraction of the original claim, that the company could resolve on fair terms.
The response was framed on the entitlement record, not on goodwill. By presenting a license by license reconstruction that the reviewer could verify, the practice moved the conversation from an assertion the company had to disprove to a documented position the reviewer had to accept. The reviewer's leverage is the gap in your records. Close the gap and the leverage closes with it.
The review settled at $0.74M against the $4.6M opening claim, an eighty four percent reduction in exposure delivered inside eleven weeks. The settlement reflected only the genuine gap that survived the reconstruction, with the bulk of the original claim removed because the licenses were properly covered and the company could now prove it. No part of the reduction depended on a discretionary concession. It rested entirely on the documented entitlement position.
The durable value was the baseline. The company emerged from the review with a complete, defensible record of its Azure bring your own software estate, mapped license by license to mobility rights and Software Assurance coverage. That record turned a recurring exposure into a managed position and gave the company a foundation it could maintain as it continued to scale, so the next review would meet documentation rather than assumptions.
The engagement reflects the firm's broader record across Microsoft contracts: more than $420M in cumulative client savings, over 340 engagements delivered, and an average 79 percent reduction in audit financial exposure, built on 20+ years of combined practice depth across the Microsoft estate. The figures above are verifiable on a reference call arranged through the practice.
The practice supports software and cloud companies on defending Azure bring your own software and license mobility disputes through entitlement reconstruction. Two analyst calls, no pitch, and an honest read on what the exposure actually is.