Home · The Audit Brief · Article
Penalty Mitigation · Top of funnel

Licenses at 125 Percent of Price and How to Avoid It

The 5 percent clause is what makes a Microsoft audit expensive. Cross the line and you buy the missing licenses at 125 percent of price and pay the verification cost too. Here is exactly how the penalty works and how to stay under it.

Published April 9, 2026Updated May 28, 2026Independent buyer side analysis · About a 10 minute read

Most people meet the 125 percent figure for the first time in an audit settlement, when it is too late to change the position it applies to. It is written into the Microsoft Business and Services Agreement, it is mechanical, and it turns a compliance gap into a premium purchase. The good news is that it only bites past a clear threshold, and that threshold is something you can manage before an audit ever begins. This article explains the clause in plain terms and shows where the defense actually sits.

What the clause actually says

The audit clause in the MBSA sets a single trigger. When a formal audit finds that your unlicensed use is 5 percent or more of your total use, two things follow. You reimburse Microsoft for the cost of the verification, and you acquire the licenses you were short on at 125 percent of the current price rather than the normal rate. Below 5 percent, you simply true up the shortfall at standard pricing and the verification cost stays with Microsoft. The 5 percent line is the whole game.

The penalty is not a fine in the ordinary sense. It is a contractual uplift that switches on at 5 percent of total use. Keep unlicensed use below that line and the expensive part of the clause never applies.

Why the threshold is a percentage, not a count

The trap in the clause is that 5 percent is measured against total use, not against a fixed number of licenses. A large estate can absorb more raw shortfall before crossing the line, and a small estate can be tipped over by a handful of servers. This is why the same forgotten deployment is harmless in one company and a penalty in another. It also means the denominator matters. If the auditor undercounts your legitimately licensed deployment, your unlicensed percentage looks higher than it is, and a position that should sit under 5 percent gets pushed over. Defending the denominator is as important as defending the numerator.

A worked example of the math

The figures below are indicative and built to show the mechanics, not real client data. They illustrate how the same shortfall produces very different outcomes on either side of the line.

ScenarioTotal useUnlicensed useResult
Under the line1,000 units40 units (4 percent)True up 40 units at standard price, no verification cost
Over the line1,000 units60 units (6 percent)Acquire 60 units at 125 percent of price, plus verification cost

The difference between the two rows is twenty units of deployment, yet one is a routine purchase and the other is a penalty purchase with the verification bill attached. That gap is exactly where buyer side defense earns its place.

Where the position is really decided

The percentage that the clause acts on is the output of the Effective License Position, the reconciliation of what you deployed against what you are entitled to. The auditor builds that position, and the auditor builds it from Microsoft's own counting methodology and Microsoft's own data drawn from Azure, Microsoft 365, and management tooling. A clean internal report can still differ from the number the auditor produces, and the auditor's number governs unless you challenge it. So the question of whether you cross 5 percent is decided in how the ELP is built, which entitlements are credited, and how deployment is counted.

  • Entitlements that exist but were not surfaced to the auditor pull your percentage down once they are credited
  • Rights you hold but had not documented, including non production and downgrade rights, change the count
  • Deployment counted twice across hosts or migrations inflates the numerator unfairly
  • Edition and core assumptions that the auditor applied without checking can be contested

How to stay under the line

Avoiding the 125 percent uplift is a matter of controlling the position before and during the audit, not arguing about it afterward.

  1. Know your real position firstBuild your own Effective License Position before any review, so you know whether you sit above or below 5 percent and by how much.
  2. Close the gap on your own termsIf you are above the line, remediate and acquire at standard pricing before an audit fixes the position, rather than at the penalty rate after.
  3. Defend the denominatorMake sure every legitimate entitlement and right is credited, because a fuller count of licensed use lowers the unlicensed percentage.
  4. Challenge the count, not just the totalTest how the auditor counted cores, editions, and migrated workloads, since a single counting error can be the difference between 4 and 6 percent.

The next step

The 125 percent clause is fixed, but the position it applies to is not. The Microsoft Audit Survival Guide sets out the full sequence from letter to settlement, and the related articles below cover who pays the verification cost and how to document the remediation that keeps you under the line. Download the guide to see where the threshold is decided and how to keep your position on the safe side of it.

Related reading

When the exposure is real, we work the penalty math through our penalty mitigation engagement.

Know your position before the line is drawn.

Download the Microsoft Audit Survival Guide and see exactly how the 5 percent clause is decided. Fixed Fee from $18,000 or Gainshare, both backed by our guarantee.

Download the Microsoft Audit Survival Guide

The Audit Brief

Weekly intelligence on Microsoft and SPLA audit moves and the buyer side defenses that work.

Get a Quote · Book a Strategy Call · The Audit Brief · About · Pricing · Blog · Contact · Privacy · Terms · New York · London Not affiliated with Microsoft Corporation. Independent buyer side advisory only.