The strongest position in any Microsoft audit is the one where you already know your own Effective License Position. When you build it first, the auditor's draft stops being a verdict and becomes a document you can check against your own.
Why the order matters
Microsoft can verify an end customer three ways. A SAM engagement is voluntary and sales led, presented as a free optimization but used to find gaps. A self verification is a contractual demand you cannot decline. A formal audit runs through a third party accounting firm under the audit clause. All three converge on the same artifact, an Effective License Position, the reconciliation of what you deployed against what you were entitled to use. Whoever builds that reconciliation first sets the frame for everything that follows.
If Microsoft and its auditor build it first, you spend the engagement reacting to a number you did not produce, on a timeline you did not set, using data you cannot fully see. If you build it first, you arrive knowing where your real exposure sits, which findings to expect, and which figures to challenge. The work is the same reconciliation either way. The difference is who controls it.
What an internal ELP actually contains
A defensible internal Effective License Position is not a license count from a single tool. It is a reconciliation built from deployment data, entitlement records, and product use rights, assembled the way the auditor will assemble it. It answers, for every product in scope, how much is deployed, how much is genuinely in use, what you are entitled to, and where the gap sits.
- Deployment data across servers, endpoints, virtualized hosts, and cloud, with dormant and decommissioned instances identified
- Entitlement records mapped to the deployments they cover, including agreements, true ups, and prior purchases
- Product use rights applied correctly by edition, version, and licensing model
- Usage signals that distinguish what is installed from what is actually consumed
- A clear gap figure expressed as a percentage of total use, because that percentage drives the contract clause
Why a SAM tool report is not the same thing
It is tempting to treat the output of a software asset management tool as a finished ELP. It is not audit defense. Microsoft uses its own counting methodology and its own data drawn from Azure, Microsoft 365, and management tooling. A clean SAM tool report can still differ from Microsoft's calculation, and Microsoft's calculation governs. The value of an internal ELP is not that a tool produced a number. It is that you understand the methodology behind the number and can defend each input when the auditor's version disagrees.
The 5 percent line you are managing toward
The reason to know your position early is the contract clause. If unlicensed use reaches 5 percent or more of total use, you reimburse Microsoft's verification costs and acquire the missing licenses at 125 percent of price. Below that line, you simply true up at normal price. Knowing your position before Microsoft does means you can see whether you are near that threshold and, where there is time, close the gap or correct the assumptions that pushed you over it before any formal count happens.
| Corrected position | What you pay |
|---|---|
| Unlicensed use below 5 percent | True up the gap at normal price, no premium, no cost reimbursement |
| Unlicensed use at or above 5 percent | Acquire at 125 percent of price and reimburse verification costs |
The figures above are the contract mechanics, not an estimate of your case. The point is simple. The same estate can sit on either side of that line depending on whether dormant instances are counted, editions are applied correctly, and entitlements are fully mapped. Knowing this early is what gives you room to act.
The defensive move this enables
A recognized buyer side move is to decline the initial SAM review and run your own internal assessment with independent help first, then respond to any formal demand from a controlled position. You cannot make that move well if you do not already know your numbers. Building the ELP first is what converts a reactive audit into a managed one. It is the difference between learning your exposure from the auditor and presenting your position to them.
The next step
Knowing your Effective License Position is the foundation of audit readiness. Start from our pillar, the Effective License Position Guide, then read how governance roles in audit readiness keep that position current and how the audit readiness calendar turns it into a routine. The opening position is built to be high. Knowing your own first is how you are ready before the letter arrives.
If the timeline is already running, we model the exposure through our ELP exposure modeling work before the auditor publishes theirs.
Build your ELP before Microsoft does
Download the Effective License Position Guide, the buyer side playbook for building a position you can defend. Fixed Fee from $18,000 or Gainshare, no risk to you, both backed by our guarantee.
Download the Effective License Position guide