Most organizations sign the Microsoft Business and Services Agreement, the MBSA, without reading the audit clause closely. It is short, it is standard, and it sits in the background until the day an audit notice arrives. On that day it becomes the most important paragraph in your contract, because it is the authority for everything the auditor does. This article walks through what the clause grants, what it does not, and where the defense lives.
One clause, two tracks
The MBSA is the master agreement beneath your Microsoft relationship, whether you are an end customer running volume licenses or a hoster operating under SPLA. The audit clause is the common root of both audit tracks. For an end customer it authorizes a formal audit run by a third party accounting firm that produces an Effective License Position. For a hoster it authorizes a SPLA audit run by a Big Four firm across a 36 month lookback. The mechanics differ but the source of authority is the same.
What the clause grants Microsoft
Read plainly, the clause gives Microsoft a defined set of rights. It grants the right to verify that your use of the software complies with your licensing. It provides for that verification to be carried out by an independent third party, typically an accounting firm. And it generally requires reasonable notice and conduct that does not unreasonably interfere with your operations.
The independence of the auditor cuts both ways. The auditor is not your advocate, but the auditor is also bound by the clause and by professional standards. That gives you a basis to hold the process to its proper bounds rather than submitting to whatever is asked on whatever schedule is demanded.
The financial terms inside the clause
For end customers the clause carries a specific consequence. If the auditor concludes that unlicensed use is 5 percent or more, you reimburse Microsoft for the cost of the verification and you acquire the licenses you are short on at 125 percent of price. The 5 percent figure is a trigger, not a tolerance band you are entitled to use, and the 125 percent is the contractual uplift on the catch up purchase.
| Item | Amount |
|---|---|
| Measured shortfall at list price | $1,000,000 |
| Acquisition at 125 percent | $1,250,000 |
| Verification cost reimbursement | $120,000 |
| Total exposure if the gap stands | $1,370,000 |
Figures are indicative. The point is that the uplift and the cost reimbursement turn a licensing gap into a much larger bill, which is why the defense focuses on keeping the measured gap below the trigger.
What the clause does not grant
The clause is a grant of specific rights, not an open license to assume the worst. It does not make the auditor figure final. A draft Effective License Position is a proposed conclusion built on assumptions you are entitled to test. It does not require you to accept Microsoft counting methodology without question, even though Microsoft relies on its own data from Azure, Microsoft 365, and management tooling. And it does not turn a voluntary SAM engagement into a contractual obligation.
How to read the clause as a defense
- Confirm the audit is being conducted under the clause and within its scope before you respond.
- Hold the process to its standards of reasonable notice and reasonable conduct.
- Treat every draft conclusion as contestable, because the clause does not make it final.
- Rebuild the position from your own evidence rather than accepting vendor data unchallenged.
- Work the measured gap toward and below the 5 percent threshold wherever the evidence allows.
Your next step
We are the defense that sits between you and Microsoft and its appointed auditor, and we operate inside the clause, not against it. The same authority that lets the auditor measure you also bounds how they may do it. To see the whole sequence from notice to settlement, read the stages of a Microsoft audit and our wider survival guide. 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, and our guarantee is plain: we reduce your exposure or we reimburse our service fee.
Before you send anything back to the auditor, our Microsoft audit defense team manages every exchange with the auditor on your behalf.