The document Microsoft once called the Product Use Rights, and now publishes as the Product Terms, is the single most cited reference in any compliance review and the least read document in most enterprises. It governs how every product you license may actually be used. This is a plain reading of what it is, why the version date matters more than the content, and how a buyer turns it from a liability into a defense. The rules are written by the seller. Reading them is the buyer's job.
The Product Terms are the master rulebook that sits underneath every Microsoft agreement you sign. Your Enterprise Agreement or Microsoft Customer Agreement for Enterprise sets the commercial frame, the price, and the term. The Product Terms govern the detail of what each license entitles you to do: how a product may be installed, who or what must be licensed to access it, what virtualization rights apply, and which benefits travel with Software Assurance.
For most of the last two decades this document was published as the Product Use Rights, almost always abbreviated to PUR. Microsoft has since consolidated it, along with several other reference documents, into a single online publication called the Product Terms. The name on the cover changed. The function did not. When a third party auditor builds a compliance position against your estate, the Product Terms are the authority they cite line by line.
The most important thing a buyer can understand about this document is that it is not static. Microsoft revises it regularly, sometimes monthly, and the rights that applied when you acquired and deployed a product are the rights that govern that deployment. A change published in a later edition does not retroactively rewrite what you bought.
This single fact is where most audit disputes are won or lost. An auditor working from the current edition will frequently apply a definition or a restriction that did not exist when your environment was built. A buyer who can produce the edition that was in force at the point of acquisition is holding the only version that matters, and the gap between the two is very often the difference between a real shortfall and a manufactured one.
You are governed by the Product Terms as they read on the day you acquired the license, not as they read on the day you are audited.
A handful of provisions account for the large majority of exposure that surfaces in reviews. None of them are hidden. All of them are easy to assume your way past.
The Product Terms generally require that every user or device benefiting from a product be licensed, even when access is routed through intermediate software. This is the principle behind multiplexing rules, and it is the most common surprise in Dynamics and server reviews. The middle layer does not absorb the licensing obligation.
Rules for licensing software in virtual environments, including how cores are counted and how mobility applies, are some of the most frequently misread provisions in the entire document. See virtualization counting and VM density for how this plays out on Windows Server.
Many rights buyers assume they hold, including hybrid benefit and license mobility, depend on active Software Assurance. The Product Terms define those dependencies precisely. Letting Software Assurance lapse can quietly remove a right you are still exercising.
In a formal review the Product Terms become the auditor's primary instrument. Findings are framed as deviations from defined use rights, and the financial exposure that results is calculated against list pricing in the current edition. This is presented as a settled liability. It is not. It is an opening position built on one party's reading of a document that has multiple historical versions.
A disciplined defense reconstructs the entitlement picture against the editions that actually governed each deployment, challenges definitions that were applied out of period, and reframes the exposure as a negotiation rather than an invoice. This is the core of audit defense, and across the practice it is the reason average audit exposure is reduced by 79 percent on the engagements we run.
The same document that creates exposure also creates rights, and most enterprises underclaim them. Hybrid benefit goes unused. Downgrade and down edition rights are forgotten. Mobility entitlements that would lower Azure cost sit unexercised. A buyer side reading of the Product Terms is as much about recovering value you have already paid for as it is about defending against a shortfall.
The practical discipline is simple to state and rarely done. Maintain a record of which edition governed each material acquisition. Reconcile your deployment against your entitlements before anyone else does, which is the work of an effective license position. And treat every renewal as the moment to lock the use rights you depend on into the agreement itself, rather than relying on a document the other party controls and revises.
A short companion to this explainer. The first moves to make when a compliance review lands, including how to establish which edition of the Product Terms governs your estate before you respond.
When the Product Terms are being used to set your exposure or your price, the version that governs and the rights you have already bought are both negotiable ground. Two analyst calls, no pitch.