Microsoft contract terms. Decoded.

The Microsoft Enterprise Agreement reads as a single document. The commercial leverage sits inside seven clauses. The Product Terms reference. The Price Sheet. The BPO clause. The price protection. The audit clause. The True Up math. The Customer Affiliate definition.

Each clause carries a default Microsoft position and a buyer side counter. The default holds unless the counter is filed in writing before signing. The settlement runs at list price if the buyer side counter is missing.

Read this article alongside the Microsoft knowledge hub, the Microsoft advisory practice, the Microsoft EA Renewal Playbook, the Microsoft audit survival checklist, and the Vendor Shield subscription.

Product Terms reference

The Microsoft Product Terms document defines every product, every use right, every license metric, and every restriction. The document publishes monthly. Each version supersedes the previous.

Product Terms versions and the contractual reference

The buyer side fix on the Product Terms reference

File a one line amendment that locks the Product Terms version to the signing date. Capture the document version and store the PDF as an audit defense artifact. Refresh only at the customer's election, not Microsoft's.

Price protection clause

The Microsoft EA carries a price protection clause on the Online Services line. The clause holds the per user per month price for the term. The clause does not apply to on premise SKUs by default. The clause does not apply to True Up purchases by default.

Five price protection traps on the Microsoft EA

• On premise SKU reset. Windows Server, SQL Server, and System Center reset at each renewal absent an amendment.
• True Up purchase reset. A True Up at a higher price overrides the original price protection.
• New SKU exclusion. Copilot, Power Platform, and new GenAI SKUs are excluded from price protection at launch.
• FX clause. Multi currency EAs carry an FX adjustment clause that breaks the price protection.
• Affiliate divestiture. A divested affiliate loses price protection at the closing date.

The buyer side fix on price protection

Extend price protection to on premise SKUs through an amendment. Hold the True Up price to the original signing price. Apply price protection across all current and future SKUs in the EA.

BPO suspension clause

The Business Process Outsourcing clause permits a divested entity to continue using the EA for up to sixty days after the closing. The clause is rarely invoked because the customer does not know it exists. The clause has to be invoked in writing within thirty days of the closing.

Six BPO clause discipline points

• Invoke in writing. A written notice to the Microsoft account team within thirty days of the closing.
• Document the scope. List every product, every license count, and every affiliate covered by the suspension.
• Track the sixty day window. The window runs from the closing date, not the notice date.
• Plan the cut over. The divested entity needs a new EA or a CSP agreement before day sixty one.
• Document the True Up impact. The True Up that follows the divestiture has to net out the suspended licenses.
• Capture the audit defense artifact. The BPO notice and the cut over plan are the audit defense artifacts.

Audit clause discipline

The audit clause sits inside the Microsoft Business and Services Agreement. The clause permits Microsoft to audit at any time with thirty days notice. The customer has ninety days to deliver the data. Microsoft auditors are usually Big Four firms paid by Microsoft.

Audit clause checkpoints and the buyer side counter

True Up math

The Microsoft EA True Up is an annual reconciliation. The customer reports the user count and the deployed product count. Microsoft invoices the delta against the baseline. The True Up runs at the signing price, not the renewal price, if the price protection clause holds.

The buyer side fix on True Up math

Run the internal count every quarter, not annually. Reconcile against the baseline. Forecast the True Up exposure twelve months out. Negotiate a True Down option at the next renewal cycle. Document every True Up against the original signing price.

Customer Affiliate definition

The Customer Affiliate definition controls which legal entities can use the EA. A narrow definition forces a separate EA at every acquisition. A broad definition lets the customer absorb acquisitions under the existing EA for the term.

What to do next

The seven step checklist below is the buyer side starting position to control the Microsoft EA contract terms.

1. File the Product Terms lock amendment. One line, signed before the order.
2. Extend price protection across on premise SKUs. Tie the protection to True Up purchases.
3. Document the BPO clause. Train the procurement team to invoke within thirty days.
4. Negotiate the audit clause checkpoints. Notice, delivery, auditor identity, threshold, settlement currency.
5. Run the True Up internal count quarterly. Forecast the True Up exposure twelve months out.
6. Broaden the Customer Affiliate definition. Pre approve acquisitions inside the term.
7. Engage independent advisory. Buyer side benchmark on the EA and audit defense on every SAM Engagement.

Frequently asked questions

How Redress engages on Microsoft

Redress runs Microsoft engagements inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The Microsoft commercial leadership sits with Ethan Mullins.

Read the related benchmarking, about us, locations, and contact pages.