The Effective License Position is the reconciliation of what you deploy against what you are entitled to use. In a Microsoft audit it becomes the number everything else is built on. This guide explains how the ELP is produced, why the auditor's version is an opening position, and how to build one you can defend.
An Effective License Position, usually shortened to ELP, is a reconciliation. On one side sits your deployment, every install and every consuming user across servers, Microsoft 365, and Azure. On the other side sits your entitlement, the licenses and subscriptions you actually hold with their use rights. The ELP is the net of the two. A positive net means you hold more than you use. A negative net means unlicensed use, and that is where exposure lives.
In a formal Microsoft audit a third party accounting firm produces the ELP under the MBSA audit clause. In a self verification you produce it under a contractual demand you cannot decline. In a SAM engagement, which is voluntary and sales led, Microsoft will offer to produce it for you. In every case the ELP is the spine of the outcome, which is why who builds it and how matters so much.
The ELP that lands on your desk reads with the authority of a finding. It is not one. It is the start of a negotiation. The auditor counts with Microsoft's methodology and Microsoft's data, and that methodology tends to resolve ambiguity against the customer. Editions get read up rather than down. Benefits you are entitled to, such as downgrade rights, prior version use, and license mobility, are often omitted unless you assert them. Each of those omissions inflates the gap.
The contract clause gives the opening number real teeth. If unlicensed use is 5 percent or more of total use, you reimburse Microsoft's verification costs and acquire the missing licenses at 125 percent of the current price. That threshold is why a defensible ELP is worth building with care.
Many organizations run a SAM tool, get a clean ELP, and assume they are covered. They are not. Microsoft uses its own counting methodology and its own data drawn from Azure, Microsoft 365, and management tooling. A clean SAM tool result can still differ from Microsoft's calculation, and Microsoft's calculation governs. The tool is useful for inventory. It is not a defense. We explain this in detail in why a SAM tool ELP is not audit defense and in why SAM tool output needs expert review.
The table below shows how an opening position can shrink once entitlements are asserted correctly. The figures are indicative and used only to show the mechanics.
| Product | Auditor opening gap | After downgrade and mobility rights asserted | Defended gap |
|---|---|---|---|
| Windows Server (per core) | 240 cores | Server and CAL entitlements and mobility applied | 40 cores |
| SQL Server | 16 cores | Passive failover and version downgrade applied | 0 cores |
| Microsoft 365 E5 | 180 users | Disabled and unassigned accounts removed | 35 users |
The point is not the specific numbers. The point is that most of an opening gap is contestable, and the contest happens before any settlement is signed.
A practical walk through of how Microsoft builds an Effective License Position and how to build one you can defend.
Inside you will find the full reconciliation method, the entitlements auditors routinely omit, a worked exposure model against the 5 percent clause, and a checklist you can run before you respond to any demand. Written for CIOs, procurement, IT asset managers, and general counsel.
Enter your work email to receive the guide. We block free inboxes so we can keep the list to practitioners. You can subscribe to The Audit Brief on the same step.
We rebuild your Effective License Position and defend it line by line. Fixed fee or gainshare, both backed by our guarantee.
Get a QuoteWeekly intelligence on Microsoft and SPLA audit moves and the buyer side defenses that work.