End Customer Track

The Effective License Position, Explained

How Microsoft builds the number that defines your exposure

The Effective License Position is the single document that decides what an audit costs you. Understand how it is built, where it goes wrong, and how to contest it before it becomes your bill.

Every Microsoft audit converges on one number. It is called the Effective License Position, the ELP, and it is the reconciliation of what you are deemed to be using against what you are licensed to use. The gap between those two figures is your unlicensed use, and that gap drives the entire cost of the audit. If you understand how the ELP is built, you can see where it is vulnerable. If you do not, you are accepting a figure assembled by people whose job is to maximize it.

What the Effective License Position is

The ELP is a product by product comparison. On one side sits your deployment, the count of what the auditor believes is installed, accessed, or running across your estate. On the other side sits your entitlement, the licenses you can prove you own. The auditor subtracts entitlement from deployment. Where deployment exceeds entitlement, the difference is reported as a shortfall. The sum of those shortfalls, priced out, is your exposure.

The number looks objective. It is presented as accounting. In practice it is a stack of assumptions, and each assumption is a place where the figure can be inflated or corrected.

How the auditor builds the number

A formal audit runs through a third party accounting firm appointed under the audit clause in your Microsoft Business and Services Agreement. The auditor follows a sequence, and knowing that sequence tells you where to apply pressure.

Step one: data collection

The auditor gathers deployment data. Some comes from scripts and inventory tools run across your environment. A great deal comes from Microsoft own telemetry, drawn from Azure, Microsoft 365, and your management tooling. This is the heart of the issue. Microsoft uses its own counting methodology and its own data, and that data is not always a fair picture of your actual licensable usage.

Step two: product mapping

Raw deployment data has to be mapped to licensable products and editions. Is that SQL Server instance Standard or Enterprise? Is that user a full Microsoft 365 E5 user or something lighter? Mapping decisions move large amounts of money, because editions differ in price by multiples. Auditors faced with ambiguity tend to map upward, to the more expensive assumption.

Step three: applying entitlements

The auditor then applies your entitlements. This step is only as good as the records used. Volume licensing history, prior agreements, transfers, and downgrade rights all reduce the shortfall, and all are easy to miss if you are not the one assembling them. Entitlements you cannot locate are entitlements the auditor will not credit.

Step four: the draft ELP

The auditor issues a draft ELP. This is the moment many teams misread. The draft is not a verdict. It is an opening position, and it is built on the assumptions above. The draft is where the defense begins, not where it ends.

Where the number goes wrong

The draft ELP overstates exposure in predictable ways. The most common are:

  • Edition inflation. Standard products counted as Enterprise, or light users counted as premium users, because the mapping defaulted to the costly assumption.
  • Double counting. The same workload counted twice because it appears in more than one data source.
  • Stale or decommissioned assets. Installations that no longer exist still showing in the inventory.
  • Virtualization assumptions. Counting every host where a workload could run rather than where it actually runs, which inflates core and processor based products dramatically.
  • Unapplied rights. Downgrade rights, license mobility, and prior entitlements that were never credited.

None of these are exotic. They appear in audit after audit, and each one is a line you can contest with evidence.

Why a SAM tool result is not the same thing

Teams sometimes run a Software Asset Management tool and assume the output is their ELP. It is not. A SAM tool produces a self generated view that Microsoft is under no obligation to accept. In an audit Microsoft uses its own methodology and its own data, and where the two disagree, Microsoft relies on its own. A SAM tool result is a useful internal hypothesis. It is not audit defense, and it is not a number you can take to the table as fact.

How to contest the ELP

The draft ELP is contestable in full. Effective defense follows a clear method.

  • Rebuild the deployment count from your own evidence rather than accepting the auditor figure.
  • Challenge every edition and role mapping that defaulted to the expensive assumption.
  • Locate and apply every entitlement, including downgrade rights, mobility, and historic agreements.
  • Strip out decommissioned, duplicated, and non productive instances.
  • Correct virtualization counts to reflect where workloads actually run.
  • Reduce the gap below the 5 percent threshold wherever the evidence allows, because at or above 5 percent you reimburse verification costs and acquire licenses at 125 percent of price.

The 5 percent threshold is the figure to keep in view throughout. Below it, the contractual penalty does not trigger. Every line you correct that pulls the gap downward changes the economics of the entire audit.

Why this is buyer side work

The auditor is independent of you, and its deliverable serves the enforcement clause. No one in the room is paid to find the corrections that reduce your bill unless you bring them. That is our role. We are the defense that sits between you and Microsoft and its appointed auditor, and we rebuild the ELP from your evidence to bring the number down to what is genuinely owed and no more.

We work on a Fixed Fee from $18,000 or on Gainshare, a share of verified savings or avoided penalty with zero retainer and no risk to you. Our guarantee is simple: we reduce your exposure or we reimburse our service fee. Across more than 300 Microsoft and SPLA audits we have defended more than $500M in Microsoft exposure, with clients held in the 95 to 100 percent range of penalty exposure defended and more than 20 years of combined experience behind every engagement.

Received a draft ELP?

Do not accept it as final. Send it to us and we will show you where the number is inflated and how far it can come down.